Understand the project
Practical overview
When it fits
Use Crabtalk when an application needs a self-hosted long-running agent runtime with explicit capability declarations, MCP connectivity or a separate application layer.
Who it is for
- Developers building long-running autonomous agents.
- Teams creating self-hosted agent services with declared capabilities.
- Builders developing standalone applications on top of an agent daemon.
- Rust developers working with MCP-connected agent runtimes.
Documented uses
- Run agents through a persistent daemon.
- Dispatch tools declared through agent harnesses.
- Connect agents to MCP servers as a capability.
- Limit access to declared shell, file, skills and session-search harnesses.
- Connect independent agent-powered applications to the daemon through auto-discovery.
Before you choose
Requirements & limits
The project is presented as a public Apache-2.0 Rust repository. Its README documents installation through cargo and crabup, followed by the crabtalkd daemon command. The README also warns that the CLI and internal APIs are under heavy refactor.
- Crabtalk separates the daemon from applications that connect through auto-discovery.
- Shell, file access, skills and session search are declared harnesses rather than tools owned directly by the daemon.
- MCP is modeled as a capability for calling another program, not as a harness.
- The repository documents an RV64 ELF format for harnesses and says access is limited by each declaration.
- The current refactor may affect CLI usage, crate layout and APIs.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 3 October 2026
- Original website title
- crabtalk/crabtalk · Official homepage title · retained in its source language