Octomate 🐙

Your agents. Your channels. Wherever you need them.

Octomate is a self-hosted relay that brings your agents, conversations and tools within reach across channels. Give an agent a task, let it work in the background, and return to the conversation wherever you're connected. Keep using your existing apps, editor and terminal, with the agents and logins you already have.

Documentation · Quickstart · Tentacles

Early development. APIs and integrations are evolving. Capabilities vary by agent and channel; the guides describe their current limits.

See it in action

Start at your desk, continue elsewhere

Use your agent as usual. Octomate collects the session, so you can revisit it or ask your agent to hand the task to a connected channel with a brief. Native sessions

Think it through together, then put an agent to work

Discuss an idea in a channel, then ask: “Hand this to Codex in the website project. Include our decisions and show me the changes before committing.” Handoffs

Take the conversation with you

“Continue this in my private conversation on the other channel.” Teleport carries the same agent and its history between supported destinations; a group discussion can move into DMs with a brief instead. Moving conversations

Connect once, ask from anywhere

“Find the open issues in my repository and compare them with what we discussed.” Your agent can combine recorded history with your connected GitHub tools. MCP connectors

Features

• Native and driven sessions. Collect sessions from supported agents, or start background work through a channel.
• Threads and chat rooms. Keep tasks independent across group conversations, private messages and the web console.
• Shared history. Record conversations centrally; let agents search message text in threads you participated in.
• Gateway. Discover destinations, hand off to another agent, teleport supported conversations, move a brief into DMs, or send a result without moving the task.
• Delegation. Inkling can commission another agent, follow up and bring its report back to your conversation.
• Native channel presentation. Stream replies, tool activity, todo lists, files and interactive cards as each channel supports.
• Approvals and questions. Answer individual requests in batches, from the conversation or Trunkline, with recorded decisions.
• Permission modes. Choose the runtime's supported level of oversight for a conversation.
• Projects and workspaces. Give project threads separate Git working copies, save changes after each turn and review diffs.
• Octomate MCP. Bring history, messaging and gateway tools into your existing agent.
• MCP proxy. Discover and use installed services through one connection, with personal OAuth grants or operator-provided credentials. Connect through Trunkline or a conversation.
• Accounts and identity. Sign in, issue API tokens and link channel profiles to the same account.
• Trunkline. Start conversations, browse collected sessions, answer pending requests, inspect workspace changes and manage MCP connections in the web console.
• Inkling's model and tool support. Use Pydantic AI models, project file and shell tools, and previews or summaries of oversized tool results.
• Deployment and operations. CLI setup, YAML templates, hooks and MCP configuration, private networking, upgrades, backups, logs and optional Logfire tracing.
• Extensible integrations. Add agent, channel or MCP tentacles; configure multiple named instances and agent/model routes.

Supported tentacles

Agents

Channels

MCP connectors

Get started

Give your agent the setup brief, or choose a deployment guide. macOS is tested end to end with live agents; Linux and Docker guides are also available, with Docker recommended for Windows. Then connect your native agents.

Contribute

Start with the development setup, design concepts and API reference. The contribution guides include examples for adding each kind of tentacle.

License

Copyright © 2026 Lu Hui. GNU Affero General Public License v3.0.