waggle
Attributed, resolvable artifact references for agent handoffs — a ~30-byte token instead of pasted context. MCP-native; the reference layer for the agent-harness world.
What is it?
What it is
Locations are dumb — no per-agent shaping, no receipts, no way to fix them once sent. waggle's 30-byte <strong>token</strong> resolves into each
Why it exists
Attributed, resolvable artifact references for agent handoffs — a ~30-byte token instead of pasted context. MCP-native; the reference layer for the agent-harness world.
Who should use it
Teams building with Rust who want an open-source, self-hosted option.
Who should avoid it
Teams that need a fully managed SaaS with enterprise SLAs out of the box.
How it works
A quick walkthrough in plain English
How waggle works
Step 1 of 3
You interact with it
Open waggle, send a request, or connect it to your stack.
Features
Advantages
- Open source (Apache-2.0)
- Active Rust ecosystem
- Self-hosted deployment options
Disadvantages
- Requires operational ownership for self-hosted setups
- Community support varies by project maturity
Installation
native
cargo install waggle-cli # from crates.io # ...or a prebuilt binary, no Rust toolchain needed: curl --proto '=https' --tlsv1.2 -LsSf \ https://github.com/modiqo/waggle/releases/latest/download/waggle-cli-installer.sh | sh # ...or Homebrew: brew install modiqo/homebrew-tap/waggle-cli
FAQ
What is waggle?
waggle is an open-source project licensed under Apache-2.0.
What language is waggle built with?
Primary language: Rust.
Is it free to use?
Yes. Licensed under Apache-2.0. Check the license for commercial use.
Featured in Videos
YouTube tutorials and walkthroughs for waggle
Alternatives
Similar projects ranked by category, topics, and text overlap.
