Agents

An agent uses a model and a configured set of tools to handle work. Comis can run one agent or several, each with its own instructions, tools, state, and limits.

​

What is an agent?

You give an agent instructions, a model, and access to selected tools. It can answer questions, search the web, work on a schedule, send messages, and store information when those features are configured. Each agent has a logical identity and normally uses agent-scoped session keys, memory and context queries, workspace paths, instructions, budgets, and tool policy. You can have one agent handling your Discord server and another managing your Telegram chats, each behaving differently based on its configuration. This scoping is not process isolation. Agents share the same trusted daemon and host, and explicitly authorized cross-agent operations can cross those logical boundaries. Use separate deployments when agents belong to mutually hostile security domains.

​

What agents can do

​

How it all fits together

When someone sends a message to your agent, here is what happens at a high level:

1. The message arrives from any connected platform (Discord, Telegram, Slack, WhatsApp, or the web dashboard)
2. Comis routes it to the right agent based on your routing rules
3. The agent recalls relevant memories from past conversations
4. The agent thinks and optionally uses tools (web search, scheduling, file management, and more)
5. A reply is sent back to the same chat

Run time depends on the model, tools, provider, and workflow. For the full walkthrough with a diagram, see the Agent Lifecycle page.

​

Slash commands

While chatting, you can control your agent with slash commands — short instructions that start with /. For example:

• /think high — Tell your agent to think harder about the next response
• /status — See session info, token usage, and model details
• /model openai/gpt-4o — Switch to a different AI model for the session
• /new — Start a fresh conversation

The supported surface includes session, model, budget, export, configuration, and conditional approval commands. Direct /skill:name dispatch is not wired in the current daemon. See Slash Commands.

​

Running multiple agents

You do not need routing rules if you only run one agent — the default agent handles everything automatically. But if you want different agents for different situations, Comis supports that out of the box. For example, you might run:

• A support agent on Slack that answers team questions
• A research agent on Telegram that finds and summarizes information
• A scheduler agent on Discord that manages reminders and recurring tasks

Routing rules decide which agent receives each ordinary inbound message, and agent/tenant identifiers scope normal storage queries. Misconfiguration or an explicitly authorized cross-agent operation can still cross those logical scopes, so routing should not be treated as a process or host security boundary. See Routing for details.

​

Explore agents