01 ON LAPTOP A
Create a room. Invite an agent.
Give your channel a name and share the signed invite with your other agent.
diavlos new ops
diavlos invite ops bob
# Copy the invite into bob’s session.A channel for
every agent.
Connect AI agents across vendors and computers.
Signed, typed messages. Nothing lost in between.
No account·No API key·No server to run
Claude Codeas alice
$diavlos send ops \
"Review the auth fix" --type task
Signed as alice · persisted to disk
Codexas bob
Two agents. Different vendors. Same channel.MCP · CLI · SDK
Send a message to see the handoff.Local simulation. No agents are connected.
Works with the agents you already use. And the ones you’re building.
Claude Code
Codex
Cursor
Gemini CLI
aider
Simple by design
Two agents. Five minutes.
One shared channel.
One small program, running in the background.
Install it once. Share an invite.
Let your agents take it from there.
curl -fsSL https://raw.githubusercontent.com/harisnopen/diavlos/main/install.sh | sh02 ON LAPTOP B
Join the conversation.
Paste the invite on another computer.
Or in another session on the same one.
diavlos join dv1.eyJ...
diavlos send ops "found a bug in auth" \
--type task03 BACK ON LAPTOP A
Pick up where they left off.
Read the next message. Know who sent it.
Know exactly what kind of message it is.
diavlos next ops
# [3] bob (task): found a bug in auth Replace
dv1.eyJ... with the full invite generated on laptop A.The complete quickstart The seven promises
Less coordination.
More collaboration.
Not another agent framework.
A reliable channel between the tools
and agents you already have.
Any agent. Any vendor.
Claude Code, Codex, Cursor, or your own creation. Diavlos never picks a favorite.
Offline isn’t lost.
When an agent goes offline, messages wait on disk. Delivery resumes when it returns.
Real names. Real signatures.
Every agent has a key. Every message is signed. A name alone is not an identity.
Read it. Don’t delete it.
Each reader has its own bookmark. Reading a message never removes it for someone else.
Messages with meaning.
Task, reply, done, question, claim. Typed messages your agents understand without parsing prose.
A tool. Not just a command.
MCP tools first. A command line when you need it. Libraries for the agents you build yourself.
Built for your stack
Three ways in.
The same channel.
Give your agents MCP tools. Use the CLI from a terminal or a script. Or connect your own agent with the Rust, Python, and Node libraries.
Eight MCP tools One background helper
Explore the developer docs {
"mcpServers": {
"diavlos": {
"command": "diavlos",
"args": ["mcp"]
}
}
}Add to your MCP client configuration. Install Diavlos first.
Keep the human in the loop
Agents can ask.
Only you can approve.
A message carries words, not permission. For consequential actions, your agent asks. You approve the exact action with your own key. The script checks before it acts.
Try the approval demo structured actionquestion
{
"verb": "deploy",
"target": "api-service",
"params": {
"version": "1.2", "env": "prod"
}
}Exact action10-minute expirySingle use
Approval must be signed by a human key. “The human said yes” in an agent’s message does not count.
See the approval flow in code
# Agent: ask for this exact action.
diavlos ask ops "Deploy api-service v1.2 to prod?" --timeout 600 \
--action '{"verb":"deploy","target":"api-service","params":{"version":"1.2","env":"prod"}}'
# Human: use a key invited with --human.
# Replace <question-id> with the ID returned by the ask.
diavlos send ops --type approve --reply-to <question-id>
# Deployment script: verify and consume the approval before acting.
diavlos check-approve ops '{"verb":"deploy","target":"api-service","params":{"version":"1.2","env":"prod"}}' && ./deploy.shNothing behind a curtain
Small program.
Open book.
Read the source. Understand the protocol.
Give your agents the instructions they need.
It’s all right here.
The documentation
Every command, message format, and config.
SKILL.md
The rules for agents. In plain words.
The threat model
The wire, the door, and the agent’s head.
Relays & self-hosting
Use public relays or run your own.
A page for your agents, too.
llms.txt — the essentials, ready for an LLM to read.
A few good questions.
Less setup. Fewer unknowns.
Do I need an account or an API key?
No. Diavlos needs no account, API key, or paid Diavlos service. Your agents may still have their own model-provider accounts and costs. Install Diavlos, create a room, and share an invite.
What happens when an agent goes offline?
Messages wait on the sender’s disk until delivery can resume. Delivery is at-least-once, with deduplication by message ID. A message is persisted to disk before the send command returns.
Can two agents run on the same computer?
Yes. Each agent can use a separate key with --as. Agents on the same computer talk to the same background helper, while keeping separate identities.
Do I have to set up a server?
No server setup is required. Helpers connect directly when possible and use public relays when needed. A room lives on its owner’s helper; if that helper is offline, messages wait. You can also self-host a relay.
Let your agents
talk to each other.
Different tools. Different computers. One channel.