Skip to main content
Comis ships with 73 built-in agent tools spanning file operations, web access, messaging, scheduling, media processing, browser automation, context management, interactive terminal sessions, and administration. This page is the master reference — every tool listed with its category, description, and link to detailed documentation. When an agent receives a message, it decides which tools to use based on what you asked it to do. Need a daily briefing? The agent uses the cron tool. Want to send a message to another channel? It uses message. Need to analyze an image someone sent? It reaches for image_analyze. The tools listed below are everything your agents have at their disposal. Each tool is linked to its detailed guide page where you will find parameters, examples, and tips for effective use.

Understanding Tool Categories

Tools fall into three tiers: Tool access is controlled by tool policy. By default, agents have access to all tools, but you can restrict access per agent using profiles (like coding or messaging) or fine-grained allow/deny lists.
All tool names use snake_case — for example, web_search, sessions_spawn, and memory_store. When referencing tools in configuration files (such as tool policy allow/deny lists), use these exact names.

Master Reference Table

Every tool your agents can use, organized by category. Click the guide link in any row to jump to the full documentation for that tool.

Files & Code (8 tools)

File and code tools are always available unless explicitly denied by tool policy. They can be individually toggled in config.yaml under the builtinTools section.

Process & Execution (2 tools)

Terminal (Interactive Shell)

Interactive terminal sessions for driving allowlisted binaries. Requires an operator-configured allowEntries allowlist — without a matching entry the tool rejects. Requires bubblewrap sandbox on Linux. See exec sandbox. Full reference: the Terminal Driver guide; for driving Claude Code & Codex as first-class coding agents (config + how it works), see Coding CLIs; to hand the agent a design doc and have it build the whole thing via the GSD spec-driven workflow, see Autonomous Builds.

Web & Browser (3 tools)

Scheduling

Scheduling tools let agents create automated tasks that run on a timer. Agents can set up recurring cron jobs, one-time reminders, and manage their own heartbeat — a periodic wake-up that triggers routine maintenance or check-in tasks.

Messaging

The message tool works across all connected channels — Discord, Telegram, Slack, WhatsApp, and every other supported platform. Agents can send new messages, reply to specific messages, add emoji reactions, edit or delete messages, fetch message history, and send file attachments. Agents can also send messages to channels they are not currently conversing in, making the message tool ideal for notifications, alerts, and cross-channel coordination.

Sessions & Sub-Agents

Session tools let agents manage their conversations, communicate with other agents, and spawn sub-agents for specialized tasks. For example, a lead agent can spawn a researcher sub-agent and a writer sub-agent to work in parallel.

Pipelines (Execution Graphs)

The pipeline tool defines and runs multi-agent execution graphs (DAGs). Nodes run in parallel when independent, or wait for upstream nodes via depends_on. Comis ships 7 built-in node type driversagent, debate, vote, refine, collaborate, approval-gate, and map-reduce.

Media

Media tools process images, audio, video, and documents. Agents can analyze images with vision AI, convert text to speech, transcribe voice messages, describe video content, and extract text from documents like PDFs. These tools require appropriate AI providers to be configured (for example, vision capabilities for image analysis, and STT providers for transcription).

Memory

Memory tools give agents access to their long-term memory. Agents automatically build up memory over time, but these tools let them explicitly search, read, and store information. Memory uses hybrid text and vector search for semantic matching, so agents can find relevant memories even with different wording.

Context (3 tools)

In-session recovery tools over the DAG (LCD) context engine’s lossless store. Available when the agent runs in DAG mode (contextEngine.version: "dag"). They recover detail the summary hierarchy compressed away within this conversation — they are distinct from cross-session recall (memory_search / session_search), which they share no code with, and they never reach other sessions or tenants. All three are never-export (never reachable via the MCP server) and read-only. See Context Management.

Infrastructure

These platform-management tools let agents inspect or modify the running Comis daemon. The gateway tool drives configuration and the secret store; background_tasks inspects the long-running task queue; mcp_manage reaches into the MCP client manager. See also: browser (listed under the Web and Browser section).

Supervisor

Supervisor tools require admin-level trust. They manage the entire platform, not just the current agent’s session. Only agents with the supervisor profile or explicit allow entries can use these tools.
Supervisor tools can modify agents, delete sessions, flush memory, and manage gateway tokens. Grant these tools only to trusted agents that need fleet-wide control. See tool policy for how to restrict access.
See also: heartbeat_manage (listed under the Scheduling section).

Platform Actions

Platform action tools perform moderation and administration tasks specific to each messaging platform. Each tool wraps the native API of its platform, letting agents kick users, manage roles, pin messages, create channels, and more — all from within a conversation. The available actions vary by platform. See the Platform Actions guide for the full list of actions per platform.

Channel Messaging Capability Matrix

The message tool works across all 10 connected channels, but not every action is supported everywhere. The matrix below summarizes per-channel capabilities — consult the Channels Overview for full per-channel detail. “Streaming” indicates how live agent output is delivered: Edit means the agent edits a placeholder message as content streams in; Block means the agent buffers and emits complete chunks; None means no streaming support (the agent waits for the full reply).

Quick Access by Use Case

Not sure which tool you need? Start here. The table below maps common tasks to the specific tool and action that handles them. Each row links to the detailed guide page where you can find parameters, examples, and tips.

Tool Guides

Explore each tool category in detail:

Scheduling

Cron jobs, heartbeat timing, and automated tasks

Messaging

Send, reply, react, edit, and delete messages

Sessions

Sessions, sub-agents, and long-term memory

Pipelines

Multi-agent execution graphs (DAGs) with 7 node types

Media

Image analysis, text-to-speech, transcription, and documents

Infrastructure

Configuration, gateway control, and fleet management

Browser

Headless browser automation and web interaction

Web Tools

Web search across 8 providers and content fetching

Platform Actions

Discord, Telegram, Slack, and WhatsApp moderation