Comis v2 · In developmentSelf-hosted. Owner-controlled.MIT licensed
Comis Get started

Self-hosted AI personal assistant

It does the work. You keep the keys.

Comis is built around one chief of staff on the chat apps you already use. It hands your requests to a team of workers and keeps you informed while they run. Every credential and every action that matters stays under your control.

Explore Comis Getting started

In development. Meet the design behind Comis. The first release is still ahead.

Chief of staffTelegram · private chat
09:14

The Android login bug is back. Open an issue with last night’s crash log.

On it. A worker is pulling the log now.

worker · crash log found · 48 s

Approval neededGitHub
Create issue in example-org/android
title
Login crashes after token refresh
body
3 crashes on Android 15 last night. Log attached.
asked by
worker, task “login bug”
Fig. 1Interactive example. Try approving or denying the request. This demo sends nothing.

01 What it does

A chief of staff that gets real work done.

You ask in plain words. Workers take on the tasks, so your chief of staff stays available to answer you. Here is what Comis is designed to do.

Telegram Slack Discord Terminal One chief of staff
A

One assistant on every channel

Telegram is the default. Slack, Discord and the terminal sit beside it. Your private channels share one chief of staff, one memory and one team.

  • doneCompare three accountants nearby
  • runningSummarize the Q3 spreadsheet
  • waitingDraft a reply to the landlord
  • queuedTranscribe this morning’s voice note
B

Real work through real tools

Workers research the web, work with code on GitHub, write documents and analyze spreadsheets. They read your email and calendar and draft replies. Reminders, schedules and follow-ups are built in.

C

Sites without an API

Comis can read your accounts on sites such as banks and utilities. You sign in through a hand-off browser that only you use. The agent never sees the password or the session. Codes, CAPTCHAs and payments come back to you.

D

Memory you can read

Facts you tell it are stored in your own words, as Markdown files in a git repository. Open them in any editor. Ask what it knows about you, and have it forget something with one tap.

02 How it works

Follow one request.

Workers have no direct route to the internet. Every request they make passes the Gate, and the Gate answers to you.

How a request travels through Comis The owner talks to the Hub. The Hub coordinates isolated workbenches. Every workbench request passes the Gate before it reaches the internet. The Gate sends approval cards back to the Hub. The owner uses the hand-off browser for sign-ins, codes and payments, also through the Gate. The Gate sends approval cards to the Hub approval cards Owner and Hub talk both ways Hub and workbenches talk both ways Every workbench request goes to the Gate everyrequest The Gate forwards what your policy allows The owner opens the hand-off browser The hand-off browser also goes through the Gate Owner Owner chat apps · terminal Hub Hub channels · tasksschedules · memory Workbenches Workbenches Pi · CLIs · skillsisolated containers Gate Gate policy · credentialsapprovals · spend Internet Internet services · models · web Hand-off browser Hand-off browser sign-ins · codes · payments From you to the internet, through the Gate You talk to the Hub. The Hub coordinates workers in isolated workbenches. Their requests pass through the Gate to the internet. Approval requests return from the Gate to the Hub. The primary task route The Gate returns approval cards to the Hub approval cards You, the owner You your chat app The Hub coordinates the work Hub coordinates work Workers run in isolated workbenches Workbenches isolated workers The Gate enforces your policy Gate your rules, enforced The internet is reached only through the Gate Internet models · apps · web
  1. YouMessage your chief of staff on Telegram, Slack, Discord or the terminal.
  2. HubRuns the channels, conversations, tasks, schedules and the memory index. It hands the work to workers.
  3. WorkbenchesContainers where Pi, an open-source coding agent, works with four tools: read, write, edit and bash.
  4. GateThe only route out. It applies your policy, injects credentials, holds writes for approval, meters spend and keeps a ledger of receipts.
  5. InternetServices, models and the web. Nothing a worker sends gets here without passing the Gate.
Fig. 2Blue is the way out. Coral is the way approval cards come back to you.
  • Hand-off browserWhere you do the steps only a person should: sign-ins, codes and payments.
  • VaultEach agent’s memory, persona and skills, kept as Markdown in git. Backup is a snapshot, and history is git log.

03 Owner control

Authority lives on the wire.

Security decisions are made outside the agent, at the network boundary. Credentials, approvals and budgets are enforced by the Gate, not by the model.

  1. 01Isolation

    Agents run in containers with no direct route to the internet. Their only way out is the Gate.

  2. 02Credential custody

    The Gate holds every API key, token and website session. The agent sees only placeholders.

  3. 03Exact approvals

    An external write waits until you approve the exact request, unless your policy allows it. It is sent once and gets a receipt.

  4. 04Budgets

    The Gate reserves the cost of every model call against daily and monthly caps before the call leaves.

  5. 05Owner-only actions

    On recognized services, account-security changes and payments ask on a card of their own. This protection cannot cover every way to move money.

  6. 06Fewer taps

    When a task holds several writes, one card shows them all, and you approve the ones you choose.

  7. 07Fail closed

    If the Gate or its ledger is unhealthy, writes are denied.

Read the security model and its limits
Fig. 3An example page of the Gate’s ledger.

04 Skills

Four tools. Many skills.

A skill teaches the agent how to use the commands on its path. These are a few examples. Some become available when you connect an account. The set of available skills will follow the release.

Core 8

  • comis
  • memory
  • delegate
  • plan
  • verify
  • research
  • terminal
  • coding-agents

Work 8

  • browser
  • documents
  • read
  • reflect
  • sites
  • speech
  • media
  • podcast

Everyday 8

  • exchange-rates
  • feeds
  • holidays
  • papers
  • places
  • wayback
  • weather
  • wiki

Connected accounts 3

  • gmail
  • calendar
  • sweep

Read-only, through the Gate.

Chat controls

  • /new
  • /stop
  • /status
  • /decisions
  • /approve
  • /deny
  • /away
  • /back
  • /model
  • /remember
  • /help

Or ask in plain words. The chief of staff can steer or pause a worker and list your schedules.

05 Questions

Before you make room.

A few things to know about running your own assistant.

Can I install Comis today?

Comis v2 is still in development. There is no published release or supported public installer yet. Read the current status and target requirements.

Where does it run?

On a machine you control. The target is Docker on Linux, macOS, or Windows through WSL 2. Linux uses gVisor for additional sandbox isolation. The target baseline is 4 CPUs, 8 GB of memory and 20 GB of disk.

Does self-hosted mean everything stays local?

Your files and services live on your host. If you choose a hosted model provider or connect an outside service, requests still go to that provider through the Gate. A local model is also part of the design. Read the security model and its limits.

Is this a subscription service?

Comis is software you run yourself, under the MIT license. You provide the machine and model access. Hosting, model calls and services you connect can have their own costs. The Gate is designed to enforce your model-spend limits.

Which chat apps can I use?

Telegram is the default channel. Slack, Discord and the terminal are in scope. Signal, WhatsApp and iMessage are optional later channels. Availability will follow the verified release, and features can differ by channel.

Can I inspect or export its memory?

Memory is designed around Markdown files in a git vault that you control. You can read it in an editor, see changes and ask Comis what it remembers. You can also ask it to forget.

06 / Make it yours

Your assistant.
Your machine.
Your say.

One conversation, with a team behind it.
Start with the design. Come back for the release.

See what you’ll need