Documentation

Learn how to use Octomind to build powerful AI agents without writing code.

Use-cases

Use Case: Automated Code Review in CI/CD

Run Octomind as part of your CI/CD pipeline to automatically review pull requests, check for security issues, or enforce coding standards.

Read more

Use Case: Event-Driven Agent with Webhooks

Run Octomind as a persistent daemon that reacts to external events -- GitHub pushes, Slack messages, monitoring alerts.

Read more

Use Case: Custom Development Workflow

Build a multi-stage AI pipeline that refines, researches, and validates a task before another agent executes the fix.

Read more

Use Case: Web Dashboard with AI Assistant

Embed Octomind into a web application as a real-time AI coding assistant using the WebSocket server.

Read more

Use Case: Multi-Agent Task Delegation

Split complex tasks across specialized AI agents that work independently and report back to a coordinator.

Read more

Use Case: AI Self-Configuring MCP Servers at Runtime

Let the AI discover what tools it needs and connect new MCP servers on the fly -- no config changes, no restarts.

Read more

Use Case: Scheduled Tasks and Timed Automation

Use the built-in schedule tool to have the AI perform actions at specific times during a session -- reminders, periodic checks, timed workflows.

Read more

Use Case: Long-Running Development with Session Resume

Use named sessions and resume to work on complex tasks across multiple sittings without losing context.

Read more

Use Case: Custom Hooks -- Build Any Integration in Any Language

Hooks are HTTP listeners backed by scripts you write in any language. You have full control: parse any payload, filter events, transform data, and…

Read more

Usage

Installation

Read more

Quickstart

Get from zero to a productive AI session in 5 minutes.

Read more

Configuration

Octomind uses TOML configuration files stored in a platform-specific data directory.

Read more

AI Providers

Octomind talks to language models through a unified interface implemented in octolib. octolib wires 20 network providers plus a special cli…

Read more

Sessions

All interaction with Octomind happens through sessions. A session is a conversation with context, tool access, and cost tracking.

Read more

Roles and Permissions

Roles control what the AI can do in a session: which tools are available, what system prompt is used, and how the AI behaves.

Read more

MCP Tools Reference

Octomind uses the Model Context Protocol (MCP) to provide AI models with external tools. This is the single reference for all built-in tools.

Read more

Context Compression

Octomind automatically manages conversation context size through intelligent compression. This is the single reference for the compression system.

Read more

Workflows

octomind workflow <file.toml> is an external orchestrator that chains multiple octomind run invocations into a multi-step process. Each step is an…

Read more

Commands, Layers, Agents, and Prompts

Octomind provides four mechanisms for extending AI capabilities beyond the base session:

Read more

Structured Output

Octomind can emit its session activity as machine-readable JSON instead of human-formatted terminal text. This is what you use for automation, CI/CD…

Read more

Editor Integration

Octomind integrates with code editors via the ACP (Agent Client Protocol), providing AI assistance directly in your IDE.

Read more

Cross-Session Learning

Octomind can extract and reuse lessons across sessions — mistakes corrected, patterns that worked, user preferences — so the same issues aren't…

Read more

Supervisor

The supervisor is an out-of-band control plane that runs beside the agent loop — never in your transcript. It watches each turn, keeps the agent on…

Read more

Skills

Skills are reusable instruction packs that inject domain knowledge into AI sessions on demand. They follow the AgentSkills specification and are…

Read more

Token Efficiency: Capabilities, Auto-Activation, and LRU Eviction

Octomind keeps the model's tool surface small on purpose. Every exposed tool eats prompt tokens on every turn, and a wide tool zoo encourages the LLM…

Read more

Local Tools

Drop a shebang script into <workdir>/.agents/tools/<name> and it becomes an MCP tool — auto-discovered, role-agnostic, no config required. The…

Read more

Guardrails

Per-project policy for tool use and input preprocessing, defined in .agents/guardrails.toml. Four section types cover four phases of the session…

Read more