podium

takopi

50 of 51 criteria have a sourced finding; 49 were also cross-checked by a second agent. Every comparison that includes takopi links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-16
Agent cross-checked
49 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

No client of its own: the interface is Telegram (any Telegram app or web client, including phones) talking to a takopi process on the user machine, plus a takopi CLI for setup and running. No desktop app, web UI or editor extension. The bridge runs where Python 3.14 and uv run (OS independent).

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process, takopi CLI (onboarding, init, config, doctor, plugins) and the process that bridges Telegram to local agent CLIs · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • desktop os: No desktop client; the takopi package is a Python process (classifier OS Independent).
  • mobile apps: No takopi mobile app; users use the Telegram app.
  • browser: No takopi browser client; Telegram Web is Telegram own.
  • mobile browser: No takopi mobile web client.
  • editor extensions: No editor extension found in the repository.
  • notifications: Telegram delivers the progress and final messages; --final-notify sends the result as a new message; no other channels.
9 atomic answers
  • Desktop os [unsupported] No desktop client; the takopi package is a Python process (classifier OS Independent). Sources: takopi:pyproject.
  • Mobile apps [unsupported] No takopi mobile app; users use the Telegram app. Sources: takopi:readme.
  • Browser [unsupported] No takopi browser client; Telegram Web is Telegram own. Sources: takopi:readme.
  • Mobile browser [unsupported] No takopi mobile web client. Sources: takopi:readme.
  • Cli [supported] takopi, takopi init, config get/set/list, chat-id, doctor and plugins commands. Sources: takopi:commands.
  • Editor extensions [unsupported] No editor extension found in the repository. Sources: takopi:readme.
  • Task actions [supported] Through Telegram: send a task (with /engine, /project and @branch directives), reply to continue, /cancel, steer or cancel queued Codex continuations with buttons, /new, /file put and get. Sources: takopi:commands, takopi:changelog.
  • Notifications [partial] Telegram delivers the progress and final messages; --final-notify sends the result as a new message; no other channels. Sources: takopi:commands.
  • Cross device continuity [supported] Resume lines let a Telegram run continue in the terminal and chat sessions continue from any Telegram client. Sources: takopi:readme, takopi:telegram.

Sources: takopi:readme, takopi:pyproject, takopi:commands, takopi:changelog, takopi:telegram

Agent cross-checked partial

Bridges four agent CLIs as engines: Codex (app-server by default, exec mode optional), Claude Code (claude -p), OpenCode and Pi; entry-point plugins can add engines. Engine chosen per message with /engine, per chat or topic with /agent, and per project.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • model providers: Model choice is each CLI own; /model and /reasoning set overrides (Claude and Pi reasoning levels).
5 atomic answers
  • Harnesses [supported] codex, claude, opencode and pi runners in src/takopi/runners. Sources: takopi:readme, takopi:codexrun.
  • Model providers [partial] Model choice is each CLI own; /model and /reasoning set overrides (Claude and Pi reasoning levels). Sources: takopi:changelog, takopi:commands.
  • Custom adapters [supported] Plugin API for engine backends via entry points. Sources: takopi:plugin.
  • Session integration [supported] Controls each CLI through its machine protocol (Codex app-server JSON-RPC, claude stream-json, opencode and pi event streams) with normalized events. Sources: takopi:codexrun, takopi:spec.
  • Mixed harness operation [supported] Different engines run in different threads, topics or messages; one resume token per engine per chat. Sources: takopi:telegram, takopi:commands.

Sources: takopi:readme, takopi:plugin, takopi:config, takopi:codexrun, takopi:changelog, takopi:commands, takopi:spec, takopi:telegram

Agent cross-checked partial

Uses the engines own logins and subscriptions; Claude billing option use_api_billing; voice notes can use an OpenAI key. No takopi credits.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • vendor credits: No takopi credits.
  • local models: Any local model the engine CLI supports; none first-party.
  • account switching: No account switching found in config reference.
  • provider restrictions: No statement about provider terms for non-interactive use of subscription CLIs.
7 atomic answers
  • Agent subscriptions [supported] README: works with existing Anthropic and OpenAI subscriptions. Sources: takopi:readme.
  • Api accounts [supported] Engines read their own API keys; claude use_api_billing option. Sources: takopi:clauderun.
  • Vendor credits [unsupported] No takopi credits. Sources: takopi:readme.
  • Local models [partial] Any local model the engine CLI supports; none first-party. Sources: takopi:readme.
  • Account switching [unsupported] No account switching found in config reference. Sources: takopi:config.
  • Vendor account requirement [supported] Needs a Telegram bot token and chat id; no takopi account. Sources: takopi:config.
  • Provider restrictions [unknown] No statement about provider terms for non-interactive use of subscription CLIs. Sources: takopi:clauderun.

Sources: takopi:readme, takopi:clauderun, takopi:config

Agent cross-checked partial

Install with uv, run takopi and follow the onboarding wizard (bot token via BotFather, workflow, chat, engine); projects registered with takopi init. A git repo is needed for worktrees; GitHub is not used.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • no git: A project path without git can run; @branch worktrees need git.
  • hosted git: No GitHub integration; engines may use gh themselves.
  • managed cloud setup: No managed cloud; it runs on the user machine.
  • byo vps onboarding: No VPS onboarding feature; a user can run it on any machine.
7 atomic answers
  • First task setup [supported] Install uv and Python 3.14, uv tool install takopi, run takopi and follow onboarding, then message the bot. Sources: takopi:readme.
  • No git [partial] A project path without git can run; @branch worktrees need git. Sources: takopi:worktrees.
  • Local git without remote [supported] Worktrees are local git. Sources: takopi:wtpy.
  • Hosted git [unsupported] No GitHub integration; engines may use gh themselves. Sources: takopi:readme.
  • Prerequisite guidance [supported] README requirements and takopi doctor validate Telegram connectivity. Sources: takopi:readme, takopi:commands.
  • Managed cloud setup [unsupported] No managed cloud; it runs on the user machine. Sources: takopi:readme.
  • Byo vps onboarding [unsupported] No VPS onboarding feature; a user can run it on any machine. Sources: takopi:readme.

Sources: takopi:readme, takopi:commands, takopi:worktrees, takopi:wtpy

Agent cross-checked partial

CLI for configuration only plus a plugin API for engines, transports and commands. No public API, SDK, MCP server or webhooks for driving tasks from outside Telegram.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • cli: CLI configures and starts the bridge; it does not create or steer tasks.
  • api: No HTTP or RPC API; the Telegram bot is the interface.
  • sdk: Importable takopi.api for plugins.
  • mcp server: No MCP server.
  • webhooks: Telegram long polling (getUpdates), no webhooks.
  • operations: Plugins can add commands; task control is through chat messages.
  • authentication: Telegram bot token and allowed_user_ids sender allowlist.
  • stability: No API stability statement beyond the specification MUSTs.
8 atomic answers
  • Cli [partial] CLI configures and starts the bridge; it does not create or steer tasks. Sources: takopi:commands.
  • Api [unsupported] No HTTP or RPC API; the Telegram bot is the interface. Sources: takopi:plugin.
  • Sdk [partial] Importable takopi.api for plugins. Sources: takopi:plugin.
  • Mcp server [unsupported] No MCP server. Sources: takopi:plugin.
  • Webhooks [unsupported] Telegram long polling (getUpdates), no webhooks. Sources: takopi:telegram.
  • Operations [partial] Plugins can add commands; task control is through chat messages. Sources: takopi:plugin.
  • Authentication [partial] Telegram bot token and allowed_user_ids sender allowlist. Sources: takopi:config.
  • Stability [unknown] No API stability statement beyond the specification MUSTs. Sources: takopi:spec.

Sources: takopi:commands, takopi:plugin, takopi:config, takopi:telegram, takopi:spec

Agent cross-checked partial

Extension through Python entry-point plugins (engines, transports, commands); MCP, skills and instruction files belong to the engines; takopi itself exposes no MCP client.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • mcp client: No MCP client; MCP elicitation requests from Codex are declined.
  • custom tools: No custom tool registry.
  • instructions import: Instruction files are read by the engines only.
  • authentication: Plugin config under plugins.<id>.
  • permission scope: Engine permissions are configured in each CLI.
7 atomic answers
  • Mcp client [unsupported] No MCP client; MCP elicitation requests from Codex are declined. Sources: takopi:codexrun.
  • Plugins [supported] Entry-point plugins for engines, transports and commands. Sources: takopi:plugin.
  • Custom tools [unsupported] No custom tool registry. Sources: takopi:plugin.
  • Instructions import [unsupported] Instruction files are read by the engines only. Sources: takopi:readme.
  • Authentication [partial] Plugin config under plugins.<id>. Sources: takopi:config.
  • Permission scope [partial] Engine permissions are configured in each CLI. Sources: takopi:clauderun.
  • Integration owner [supported] Plugins are separate packages. Sources: takopi:plugin.

Sources: takopi:plugin, takopi:clauderun, takopi:codexrun, takopi:readme, takopi:config

Agent cross-checked partial

Python application (anyio, httpx, msgspec) with a Telegram transport; no native or webview client.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • desktop implementation: No desktop client; Python process.
  • mobile implementation: No mobile client.
  • hybrids: None.
4 atomic answers
  • Desktop implementation [unsupported] No desktop client; Python process. Sources: takopi:pyproject.
  • Mobile implementation [unsupported] No mobile client. Sources: takopi:readme.
  • Hybrids [unsupported] None. Sources: takopi:readme.
  • Implementation evidence [supported] pyproject.toml dependencies and src/takopi layout at the pinned commit. Sources: takopi:pyproject.

Sources: takopi:pyproject, takopi:readme

Planning and context

Agent cross-checked partial

No task intake beyond chat messages: each Telegram message or reply starts or continues an agent run; projects are registered locally. No issue import or tracker link.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • external import: No issue import.
  • chat git triggers: Telegram chat is the trigger; no git event triggers.
  • authoritative tracker: No tracker.
  • stable ids: Resume tokens identify engine sessions.
  • sync: None.
  • supported edits: None.
  • external roundtrips: Not applicable: no tracker integration.
9 atomic answers
  • Local creation [supported] A message starts a run. Sources: takopi:readme.
  • Prompt intake [supported] Text, voice notes (transcribed) and forwarded messages coalesced into a prompt. Sources: takopi:telegram.
  • External import [unsupported] No issue import. Sources: takopi:readme.
  • Chat git triggers [partial] Telegram chat is the trigger; no git event triggers. Sources: takopi:telegram.
  • Authoritative tracker [unsupported] No tracker. Sources: takopi:readme.
  • Stable ids [partial] Resume tokens identify engine sessions. Sources: takopi:spec.
  • Sync [unsupported] None. Sources: takopi:readme.
  • Supported edits [unsupported] None. Sources: takopi:readme.
  • External roundtrips [unsupported] Not applicable: no tracker integration. Sources: takopi:readme.

Sources: takopi:readme, takopi:commands, takopi:telegram, takopi:spec

Agent cross-checked partial

No task plans: the engine own plan mode applies; takopi stores context (project and branch) and resume tokens only.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • plans: No plan objects in specification or source.
  • acceptance criteria: None.
  • editors: None.
  • revisions: None.
  • implementation links: ctx footer links a message to a project and branch.
  • amendment: Reply or steer a running Codex turn.
7 atomic answers
  • Plans [unsupported] No plan objects in specification or source. Sources: takopi:spec.
  • Acceptance criteria [unsupported] None. Sources: takopi:spec.
  • Editors [unsupported] None. Sources: takopi:spec.
  • Revisions [unsupported] None. Sources: takopi:spec.
  • Amendment [partial] Reply or steer a running Codex turn. Sources: takopi:changelog.
  • Restart persistence [supported] Chat sessions persist in telegram_chat_sessions_state.json; resume tokens survive restart. Sources: takopi:telegram.

Sources: takopi:spec, takopi:telegram, takopi:worktrees, takopi:changelog

Agent cross-checked partial

No hierarchy or dependencies; each thread (chat, topic or session) is independent with a serialized queue.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • epics: None.
  • hierarchy: Projects contain branches (worktrees) and topics.
  • blockers: None.
  • readiness: None.
  • enforcement: None.
  • state propagation: None.
  • task to epic: None.
  • identity retention: A topic keeps its session.
9 atomic answers
  • Epics [unsupported] None. Sources: takopi:spec.
  • Hierarchy [partial] Projects contain branches (worktrees) and topics. Sources: takopi:topics.
  • Blockers [unsupported] None. Sources: takopi:spec.
  • Readiness [unsupported] None. Sources: takopi:spec.
  • Enforcement [unsupported] None. Sources: takopi:spec.
  • State propagation [unsupported] None. Sources: takopi:spec.
  • Task to epic [unsupported] None. Sources: takopi:spec.
  • Identity retention [partial] A topic keeps its session. Sources: takopi:topics.
  • Workflow constraints [supported] Three onboarding workflows only configure defaults; none is mandatory. Sources: takopi:readme.

Sources: takopi:spec, takopi:topics, takopi:readme

Agent cross-checked partial

Context is each engine own (instruction files, memory); takopi persists the project and branch context binding and the per-engine resume token.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • instructions: Read by engines only.
  • skills: None.
  • project docs: None.
  • memory: Resume tokens give continuity inside the engine session.
  • provenance: None.
  • correction: /ctx set and clear; /new clears sessions.
  • freshness: None.
10 atomic answers
  • Instructions [unsupported] Read by engines only. Sources: takopi:readme.
  • Skills [unsupported] None. Sources: takopi:readme.
  • Project docs [unsupported] None. Sources: takopi:readme.
  • Memory [partial] Resume tokens give continuity inside the engine session. Sources: takopi:telegram.
  • Scope [supported] Per chat, topic and sender. Sources: takopi:telegram.
  • Provenance [unsupported] None. Sources: takopi:readme.
  • Correction [partial] /ctx set and clear; /new clears sessions. Sources: takopi:commands.
  • Deletion [supported] /new clears stored sessions. Sources: takopi:commands.
  • Freshness [unsupported] None. Sources: takopi:readme.
  • Takeover continuity [supported] Reply resume lines continue a session in chat or terminal. Sources: takopi:readme.

Sources: takopi:telegram, takopi:worktrees, takopi:commands, takopi:readme

Agent cross-checked partial

No retrieval or indexing; files can be sent to and fetched from the repo through Telegram; voice notes are transcribed.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • code search: None.
  • indexing: None.
  • external knowledge: None.
  • multimodal inputs: Voice notes and uploaded files; images depend on the engine.
  • freshness: None.
  • api retrieval: None.
  • citations: None.
  • conflict detection: None.
  • review enforcement: None.
10 atomic answers
  • Indexing [unsupported] None. Sources: takopi:files.
  • External knowledge [unsupported] None. Sources: takopi:files.
  • Multimodal inputs [partial] Voice notes and uploaded files; images depend on the engine. Sources: takopi:voice, takopi:files.
  • Freshness [unsupported] None. Sources: takopi:files.
  • Access scope [supported] Uploads go to a repo-relative dir with a deny glob list. Sources: takopi:files.
  • Api retrieval [unsupported] None. Sources: takopi:files.
  • Citations [unsupported] None. Sources: takopi:files.
  • Conflict detection [unsupported] None. Sources: takopi:files.
  • Review enforcement [unsupported] None. Sources: takopi:files.

Sources: takopi:files, takopi:voice

Agent cross-checked partial

No native issue management or idea backlog: only chat threads and sessions.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • create: None.
  • edit: None.
  • discuss: None.
  • prioritize: None.
  • label: None.
  • assign: None.
  • search: None.
  • filter: None.
  • archive: None.
  • reopen: Reply to a message to continue a session.
  • project epic views: None.
  • idea parking: Telegram scheduled messages hold prompts to send later.
  • explicit dispatch: None.
  • task session separation: A thread is the session.
  • metadata: Project, branch and engine in the ctx footer.
  • durable states: None.
17 atomic answers
  • Create [unsupported] None. Sources: takopi:spec.
  • Edit [unsupported] None. Sources: takopi:spec.
  • Discuss [unsupported] None. Sources: takopi:spec.
  • Prioritize [unsupported] None. Sources: takopi:spec.
  • Label [unsupported] None. Sources: takopi:spec.
  • Assign [unsupported] None. Sources: takopi:spec.
  • Filter [unsupported] None. Sources: takopi:spec.
  • Archive [unsupported] None. Sources: takopi:spec.
  • Reopen [partial] Reply to a message to continue a session. Sources: takopi:readme.
  • Project epic views [unsupported] None. Sources: takopi:spec.
  • Idea parking [partial] Telegram scheduled messages hold prompts to send later. Sources: takopi:schedule.
  • Explicit dispatch [unsupported] None. Sources: takopi:spec.
  • Task session separation [unsupported] A thread is the session. Sources: takopi:spec.
  • Metadata [partial] Project, branch and engine in the ctx footer. Sources: takopi:worktrees.
  • Durable states [unsupported] None. Sources: takopi:spec.
  • External tracker requirement [supported] No tracker is required or supported. Sources: takopi:readme.

Sources: takopi:spec, takopi:readme, takopi:schedule, takopi:worktrees

Agent cross-checked partial

No agent-operable issue records.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • shared ids: None.
  • read: None.
  • create: None.
  • update: None.
  • claim: None.
  • assign: None.
  • state changes: None.
  • dependencies: None.
  • children: None.
  • results: Final message returns the agent answer to Telegram.
  • human visibility: None.
  • attribution: None.
  • permissions: allowed_user_ids.
  • conflicts: Per-thread serialization.
14 atomic answers
  • Shared ids [unsupported] None. Sources: takopi:spec.
  • Read [unsupported] None. Sources: takopi:spec.
  • Create [unsupported] None. Sources: takopi:spec.
  • Update [unsupported] None. Sources: takopi:spec.
  • Claim [unsupported] None. Sources: takopi:spec.
  • Assign [unsupported] None. Sources: takopi:spec.
  • State changes [unsupported] None. Sources: takopi:spec.
  • Dependencies [unsupported] None. Sources: takopi:spec.
  • Children [unsupported] None. Sources: takopi:spec.
  • Results [partial] Final message returns the agent answer to Telegram. Sources: takopi:spec.
  • Human visibility [unsupported] None. Sources: takopi:spec.
  • Attribution [unsupported] None. Sources: takopi:spec.
  • Permissions [partial] allowed_user_ids. Sources: takopi:config.
  • Conflicts [partial] Per-thread serialization. Sources: takopi:spec.

Sources: takopi:spec, takopi:plugin, takopi:config

Agent cross-checked unsupported

No living specifications.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • persistent requirements: None.
  • human edits: None.
  • agent edits: None.
  • revisions: None.
  • approvals: None.
  • implementation links: None.
  • later retrieval: None.
  • drift detection: None.
  • review integration: None.
9 atomic answers
  • Persistent requirements [unsupported] None. Sources: takopi:spec.
  • Human edits [unsupported] None. Sources: takopi:spec.
  • Agent edits [unsupported] None. Sources: takopi:spec.
  • Revisions [unsupported] None. Sources: takopi:spec.
  • Approvals [unsupported] None. Sources: takopi:spec.
  • Later retrieval [unsupported] None. Sources: takopi:spec.
  • Drift detection [unsupported] None. Sources: takopi:spec.
  • Review integration [unsupported] None. Sources: takopi:spec.

Sources: takopi:spec

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

Parallel runs across different threads (chats, topics, branches); runs for the same session are serialized with a per-thread queue and Codex steer or cancel buttons. No documented concurrency quota.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • quotas: No limit or quota in config reference or specification.
  • observed concurrency: The catalog measures no concurrency.
  • status visibility: Each run posts a progress message (engine, elapsed time, steps) edited in place; no cross-run dashboard.
5 atomic answers
  • Concurrent sessions [supported] README: parallel runs across agent sessions. Sources: takopi:readme.
  • Concurrent tasks [supported] Different threads and worktrees run concurrently; same thread serialized (specification 5.3). Sources: takopi:spec.
  • Quotas [unsupported] No limit or quota in config reference or specification. Sources: takopi:config.
  • Observed concurrency [unknown] The catalog measures no concurrency. Sources: takopi:spec.
  • Status visibility [partial] Each run posts a progress message (engine, elapsed time, steps) edited in place; no cross-run dashboard. Sources: takopi:telegram, takopi:readme.

Sources: takopi:readme, takopi:spec, takopi:changelog, takopi:config, takopi:telegram

Agent cross-checked partial

Work is routed by chat, topic, project and engine directives; per-thread queue; no assignees, claims or duplicate prevention beyond serialization.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • human assignment: None.
  • claims: None.
  • ownership enforcement: allowed_user_ids sender filter; lockfile allows one takopi instance.
7 atomic answers
  • Human assignment [unsupported] None. Sources: takopi:spec.
  • Agent assignment [supported] Engine selected per message, topic or project. Sources: takopi:commands.
  • Claims [unsupported] None. Sources: takopi:spec.
  • Queues [supported] Per-thread queue with queued jobs addressable for steer or cancel. Sources: takopi:spec, takopi:changelog.
  • Routing [supported] /project, @branch and /ctx route to repos and branches; topics bind contexts. Sources: takopi:commands, takopi:topics.
  • Duplicate prevention [supported] Steered prompts are not also run later; per-session lock. Sources: takopi:changelog, takopi:spec.
  • Ownership enforcement [partial] allowed_user_ids sender filter; lockfile allows one takopi instance. Sources: takopi:config, takopi:spec.

Sources: takopi:commands, takopi:spec, takopi:topics, takopi:changelog, takopi:config

Agent cross-checked partial

No delegation: takopi has no coordinator, subagent tools or agent-to-agent messaging; engines own any subagent features.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • roles: None.
  • model harness effort: Users choose engine, model and reasoning per scope.
  • messages: None.
  • results return: None between agents.
  • cross harness: No cross-harness teams.
  • orchestration owner: Not applicable.
  • activation: Not applicable.
  • authentication: Not applicable.
  • live progress: Progress shows engine actions only.
  • retained results: None.
  • followup: Reply continues the same session.
  • invocation: None.
12 atomic answers
  • Roles [unsupported] None. Sources: takopi:spec.
  • Model harness effort [partial] Users choose engine, model and reasoning per scope. Sources: takopi:commands.
  • Messages [unsupported] None. Sources: takopi:spec.
  • Results return [unsupported] None between agents. Sources: takopi:spec.
  • Cross harness [unsupported] No cross-harness teams. Sources: takopi:spec.
  • Orchestration owner [unsupported] Not applicable. Sources: takopi:spec.
  • Activation [unsupported] Not applicable. Sources: takopi:spec.
  • Authentication [unsupported] Not applicable. Sources: takopi:spec.
  • Live progress [partial] Progress shows engine actions only. Sources: takopi:telegram.
  • Retained results [unsupported] None. Sources: takopi:spec.
  • Followup [partial] Reply continues the same session. Sources: takopi:readme.
  • Invocation [unsupported] None. Sources: takopi:spec.

Sources: takopi:spec, takopi:plugin, takopi:commands, takopi:telegram, takopi:readme

Agent cross-checked partial

No scheduler or triggers of its own: docs rely on Telegram native scheduled and recurring messages; the internal scheduler only queues thread jobs. Runs only while the takopi process is up.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • schedules: Telegram scheduled messages (including daily and weekly) deliver prompts at a time; takopi has no scheduler.
  • events: None.
  • recurring tasks: Telegram recurring scheduled messages.
  • completion conditions: None.
  • scheduler location: Telegram servers hold scheduled messages; takopi receives them as ordinary messages.
  • retries: Telegram network errors are retried; runs are not retried.
  • client independence: Needs the takopi process running to act; Telegram client can be closed.
8 atomic answers
  • Schedules [partial] Telegram scheduled messages (including daily and weekly) deliver prompts at a time; takopi has no scheduler. Sources: takopi:schedule.
  • Events [unsupported] None. Sources: takopi:spec.
  • Recurring tasks [partial] Telegram recurring scheduled messages. Sources: takopi:schedule.
  • Completion conditions [unsupported] None. Sources: takopi:spec.
  • Scheduler location [partial] Telegram servers hold scheduled messages; takopi receives them as ordinary messages. Sources: takopi:schedule.
  • Overlaps [supported] Overlapping messages for one session queue serially. Sources: takopi:spec.
  • Retries [partial] Telegram network errors are retried; runs are not retried. Sources: takopi:changelog.
  • Client independence [partial] Needs the takopi process running to act; Telegram client can be closed. Sources: takopi:schedule.

Sources: takopi:schedule, takopi:spec, takopi:changelog

Agent cross-checked partial

Cancel with /cancel (reply to the progress message), steer or cancel queued Codex continuations with buttons, reply to continue, errors shown in the final message. No pause, approvals or escalation; Claude cannot ask questions mid-run.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • pause: None.
  • steer: Codex app-server steering through buttons; other engines queue.
  • notifications: Telegram messages and push from Telegram app.
  • pending decisions: Engine prompts are not surfaced: Claude -p cannot answer interactive questions and Codex approvals are auto-accepted.
  • escalation: None.
  • chat terminal parity: Resume lines continue the session in the terminal.
  • retained history: Telegram history; takopi stores resume tokens only.
10 atomic answers
  • Pause [unsupported] None. Sources: takopi:spec.
  • Stop [supported] /cancel stops the current run. Sources: takopi:commands.
  • Resume [supported] Reply with a resume line or auto-resume. Sources: takopi:readme.
  • Steer [partial] Codex app-server steering through buttons; other engines queue. Sources: takopi:changelog.
  • Notifications [partial] Telegram messages and push from Telegram app. Sources: takopi:telegram.
  • Pending decisions [unsupported] Engine prompts are not surfaced: Claude -p cannot answer interactive questions and Codex approvals are auto-accepted. Sources: takopi:clauderun, takopi:codexrun.
  • Escalation [unsupported] None. Sources: takopi:spec.
  • Visible errors [supported] Runner errors are rendered in the final message; crash handling in spec 6.7. Sources: takopi:spec, takopi:changelog.
  • Chat terminal parity [partial] Resume lines continue the session in the terminal. Sources: takopi:readme.
  • Retained history [partial] Telegram history; takopi stores resume tokens only. Sources: takopi:telegram.

Sources: takopi:commands, takopi:changelog, takopi:clauderun, takopi:spec, takopi:readme, takopi:telegram, takopi:codexrun

Agent cross-checked partial

No fleet or epic UI: Telegram forum topics list contexts per repo and branch; topic status icons are only a feature request.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • fleet fixture: No fixture; the catalog runs no products.
  • parent child: Topics per project and branch.
  • dependencies: None.
  • attention: None.
  • history: Telegram topic history.
  • workload: None.
  • navigation errors: None.
  • fixture mode: No fixture mode applies.
8 atomic answers
  • Fleet fixture [unknown] No fixture; the catalog runs no products. Sources: takopi:topics.
  • Parent child [partial] Topics per project and branch. Sources: takopi:topics.
  • Dependencies [unsupported] None. Sources: takopi:spec.
  • Attention [unsupported] None. Sources: takopi:spec.
  • History [partial] Telegram topic history. Sources: takopi:topics.
  • Workload [unsupported] None. Sources: takopi:spec.
  • Navigation errors [unsupported] None. Sources: takopi:spec.
  • Fixture mode [unknown] No fixture mode applies. Sources: takopi:topics.

Sources: takopi:topics, takopi:spec

Agent cross-checked partial

No mandatory workflow beyond three onboarding presets (assistant, workspace, handoff) that set defaults; engine and context chosen per message; changes mid-run are limited to steering.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • growing epic: None.
  • natural language: Directives are a small syntax, not natural-language configuration.
  • agent configuration: /agent, /model and /reasoning per scope.
  • in run changes: Steer a Codex turn; cancel.
  • live roles: None.
  • retained relationships: None.
  • auth friction: Needs each engine logged in and a Telegram bot.
10 atomic answers
  • Quick task [supported] Send a message. Sources: takopi:readme.
  • Growing epic [unsupported] None. Sources: takopi:spec.
  • Presets [supported] Assistant, workspace and handoff workflows. Sources: takopi:readme.
  • Natural language [unsupported] Directives are a small syntax, not natural-language configuration. Sources: takopi:commands.
  • Agent configuration [partial] /agent, /model and /reasoning per scope. Sources: takopi:commands.
  • In run changes [partial] Steer a Codex turn; cancel. Sources: takopi:changelog.
  • Live roles [unsupported] None. Sources: takopi:spec.
  • Retained relationships [unsupported] None. Sources: takopi:spec.
  • Discoverability [supported] Telegram command menu and docs. Sources: takopi:spec.
  • Auth friction [partial] Needs each engine logged in and a Telegram bot. Sources: takopi:readme.

Sources: takopi:readme, takopi:commands, takopi:config, takopi:spec, takopi:changelog

Execution and reliability

Agent cross-checked partial

Agents run on the machine where takopi runs (local, or any server the user chooses to run it on); no managed cloud; the bridge process must stay up.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • byo remote: Nothing prevents running takopi on a server, but no remote execution feature or guide exists.
  • self hosted: Self-run Python process; no hosted control plane.
  • managed cloud: None.
  • hybrid: Phone chat controls a host process.
  • provisioning: None.
  • resources: None.
  • region: None.
  • expiry: None.
12 atomic answers
  • Local [supported] Runs coding agents on your computer. Sources: takopi:readme.
  • Byo remote [partial] Nothing prevents running takopi on a server, but no remote execution feature or guide exists. Sources: takopi:readme.
  • Self hosted [partial] Self-run Python process; no hosted control plane. Sources: takopi:readme.
  • Managed cloud [unsupported] None. Sources: takopi:spec.
  • Hybrid [partial] Phone chat controls a host process. Sources: takopi:readme.
  • Provisioning [unsupported] None. Sources: takopi:spec.
  • Payer [supported] User pays for engines. Sources: takopi:readme.
  • Resources [unsupported] None. Sources: takopi:spec.
  • Region [unsupported] None. Sources: takopi:spec.
  • Expiry [unsupported] None. Sources: takopi:spec.
  • Client disconnect [supported] Closing Telegram leaves runs going. Sources: takopi:readme.
  • Other device continuation [supported] Any Telegram client continues the chat. Sources: takopi:telegram.

Sources: takopi:readme, takopi:spec, takopi:telegram

Agent cross-checked partial

Optional git worktree per branch via @branch under .worktrees; otherwise runs in the project directory; no container, VM or sandbox of its own.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • container: None.
  • vm: None.
  • os sandbox: Engine sandboxes only; Codex approvals are auto-accepted.
  • filesystem: Project or worktree path; engines can reach elsewhere.
  • process: Separate engine processes only.
  • network: None.
  • secrets: Bot token in takopi.toml; engines use their own credentials.
  • security boundary: None claimed; dangerously_skip_permissions is documented as high risk.
12 atomic answers
  • Checkout [supported] Default runs in the project path. Sources: takopi:worktrees.
  • Branch [supported] @branch creates or uses the branch. Sources: takopi:wtpy.
  • Worktree [supported] git worktree add under worktrees_dir. Sources: takopi:wtpy.
  • Container [unsupported] None. Sources: takopi:readme.
  • Vm [unsupported] None. Sources: takopi:readme.
  • Os sandbox [partial] Engine sandboxes only; Codex approvals are auto-accepted. Sources: takopi:codexrun.
  • Filesystem [partial] Project or worktree path; engines can reach elsewhere. Sources: takopi:worktrees.
  • Process [unsupported] Separate engine processes only. Sources: takopi:spec.
  • Network [unsupported] None. Sources: takopi:readme.
  • Secrets [partial] Bot token in takopi.toml; engines use their own credentials. Sources: takopi:config.
  • Code separation [supported] Worktrees. Sources: takopi:worktrees.
  • Security boundary [unsupported] None claimed; dangerously_skip_permissions is documented as high risk. Sources: takopi:clauderun.

Sources: takopi:worktrees, takopi:wtpy, takopi:codexrun, takopi:readme, takopi:spec, takopi:config, takopi:clauderun

Agent cross-checked partial

Resume tokens and chat sessions persist; stateless resume lines continue sessions anywhere; Telegram network errors are retried; a lockfile enforces a single instance; crashed or hung runs surface as errors. Processes do not survive a takopi restart.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • service restart: Sessions resume by token after restart; running turns are lost.
  • expiry: None.
  • transcript reload: Telegram history; engine session files.
  • process reconnect: No reattachment to engine processes.
  • state reconstruction: State JSON per chat and topic.
  • context loss: Depends on engine session.
  • manual repair: /new resets sessions; takopi doctor.
  • multi day continuity: Sessions persist in state file and engine stores.
12 atomic answers
  • Client disconnect [supported] Run continues if Telegram client closes. Sources: takopi:readme.
  • Worker crash [supported] Runner failures are rendered as errors (spec 6.7; Codex app-server shutdown surfaced). Sources: takopi:spec, takopi:changelog.
  • Service restart [partial] Sessions resume by token after restart; running turns are lost. Sources: takopi:telegram.
  • Expiry [unsupported] None. Sources: takopi:spec.
  • Transcript reload [partial] Telegram history; engine session files. Sources: takopi:telegram.
  • Process reconnect [unsupported] No reattachment to engine processes. Sources: takopi:spec.
  • Task resume [supported] Resume lines and chat auto-resume. Sources: takopi:telegram.
  • State reconstruction [partial] State JSON per chat and topic. Sources: takopi:telegram.
  • Context loss [partial] Depends on engine session. Sources: takopi:spec.
  • Duplicate actions [supported] Steered prompts do not also run later. Sources: takopi:changelog.
  • Manual repair [partial] /new resets sessions; takopi doctor. Sources: takopi:commands.
  • Multi day continuity [partial] Sessions persist in state file and engine stores. Sources: takopi:telegram.

Sources: takopi:spec, takopi:telegram, takopi:changelog, takopi:readme, takopi:commands

Agent cross-checked unsupported

No environment management: no dependency caches, services, ports or secret injection beyond the engine process environment.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • dependencies: None.
  • caches: None.
  • snapshots: None.
  • services: None.
  • ports: None.
  • secrets: None.
  • duplicate installs: Worktrees do not link dependencies.
  • collisions: None.
  • remote setup: None.
  • automatic repair: None.
10 atomic answers

Sources: takopi:worktrees, takopi:config

Agent cross-checked partial

Few limits: Telegram message size handling (trim or split), voice and file size caps, outbox rate limiting with backoff; no time, turn, token or spend limits for agent runs.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • time limits: None for runs.
  • turn limits: None.
  • token limits: None.
  • spend limits: None.
  • timeouts: Telegram requests have timeouts and retries.
  • retries: Network errors retried (v0.23.1).
  • enforcement: Only transport limits are enforced.
8 atomic answers
  • Time limits [unsupported] None for runs. Sources: takopi:config.
  • Turn limits [unsupported] None. Sources: takopi:config.
  • Token limits [unsupported] None. Sources: takopi:config.
  • Spend limits [unsupported] None. Sources: takopi:config.
  • Timeouts [partial] Telegram requests have timeouts and retries. Sources: takopi:telegram.
  • Retries [partial] Network errors retried (v0.23.1). Sources: takopi:changelog.
  • Provider failures [supported] Provider errors such as 429 render as the final message. Sources: takopi:spec.
  • Enforcement [partial] Only transport limits are enforced. Sources: takopi:telegram.

Sources: takopi:telegram, takopi:config, takopi:changelog, takopi:spec

Agent cross-checked partial

Progress messages show engine, elapsed time, step count and actions (commands, tools, file changes); structured logs with TAKOPI_LOG_* settings; no statistics or exports; an error final message states the failure.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • traces: TAKOPI_TRACE_PIPELINE logs pipeline events.
  • usage export: None.
  • task stats: None.
  • agent stats: None.
  • project stats: None.
  • time stats: Elapsed time per run in the message.
  • approval status: No approval status exists.
  • reconnect consistency: Progress messages are edited in place; ordering via the outbox.
  • performance method: No performance claims in the repository.
  • responsiveness: Not measured.
13 atomic answers
  • Logs [supported] TAKOPI_LOG_LEVEL, FORMAT and FILE. Sources: takopi:env.
  • Traces [partial] TAKOPI_TRACE_PIPELINE logs pipeline events. Sources: takopi:env.
  • Failure reasons [supported] Final message includes the runner error. Sources: takopi:spec.
  • Usage export [unsupported] None. Sources: takopi:env.
  • Task stats [unsupported] None. Sources: takopi:env.
  • Agent stats [unsupported] None. Sources: takopi:env.
  • Project stats [unsupported] None. Sources: takopi:env.
  • Time stats [partial] Elapsed time per run in the message. Sources: takopi:readme.
  • Failure status [supported] Final status error or done. Sources: takopi:spec.
  • Approval status [unsupported] No approval status exists. Sources: takopi:codexrun.
  • Reconnect consistency [partial] Progress messages are edited in place; ordering via the outbox. Sources: takopi:telegram.
  • Performance method [unknown] No performance claims in the repository. Sources: takopi:spec.
  • Responsiveness [unknown] Not measured. Sources: takopi:spec.

Sources: takopi:readme, takopi:env, takopi:spec, takopi:codexrun, takopi:telegram

Sourced unsupported

No user-visible cost tracking: the Claude runner copies total_cost_usd and usage, and the Pi runner its last message usage, into the completed-event payload, but a bounded search of src/takopi (rendering, telegram, state files) found nothing that shows, stores or exports them. An open pull request proposes Pi token usage display.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • task cost: Claude total_cost_usd is captured internally and never shown.
  • session cost: None.
  • child cost: None.
  • epic cost: None.
  • harness aggregation: None.
  • billed vs estimated: None.
  • tokens: usage dicts captured internally, not displayed or exported.
  • subscription allowance: None.
  • provider reconciliation: None.
  • compute cost: None.
  • refresh delay: None.
  • alerts: None.
  • export: None.
  • drilldown: None.
14 atomic answers
  • Task cost [unsupported] Claude cost (total_cost_usd) is captured internally in the completed event but never shown to the user or stored. Sources: takopi:env, takopi:usage-payload.
  • Session cost [unsupported] None. Sources: takopi:env.
  • Child cost [unsupported] None. Sources: takopi:env.
  • Epic cost [unsupported] None. Sources: takopi:env.
  • Harness aggregation [unsupported] None. Sources: takopi:env.
  • Billed vs estimated [unsupported] None. Sources: takopi:env.
  • Tokens [unsupported] Claude and Pi usage dicts are captured in the completed-event payload and not displayed, stored or exported at the pinned release. Sources: takopi:changelog, takopi:usage-payload.
  • Subscription allowance [unsupported] None. Sources: takopi:env.
  • Provider reconciliation [unsupported] None. Sources: takopi:env.
  • Compute cost [unsupported] None. Sources: takopi:env.
  • Refresh delay [unsupported] None. Sources: takopi:env.
  • Alerts [unsupported] None. Sources: takopi:env.
  • Export [unsupported] None. Sources: takopi:env.
  • Drilldown [unsupported] None. Sources: takopi:env.

Sources: takopi:env, takopi:changelog, takopi:usage-payload

Agent cross-checked partial

No compute-aware scheduling: per-thread serialization and an outbox rate limiter only.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • concurrency: Per-thread serialization; unlimited across threads.
  • cpu ram: None.
  • backpressure: Outbox backoff for Telegram limits.
  • host awareness: None.
  • check reuse: None.
  • check deduplication: None.
  • bounded tests: Takopi runs no checks.
  • fairness: None.
  • recovery: None.
  • shared limits: None.
12 atomic answers
  • Concurrency [partial] Per-thread serialization; unlimited across threads. Sources: takopi:spec.
  • Queues [supported] Per-thread queue. Sources: takopi:spec.
  • Cpu ram [unsupported] None. Sources: takopi:spec.
  • Backpressure [partial] Outbox backoff for Telegram limits. Sources: takopi:telegram.
  • Host awareness [unsupported] None. Sources: takopi:spec.
  • Check reuse [unsupported] None. Sources: takopi:spec.
  • Check deduplication [unsupported] None. Sources: takopi:spec.
  • Bounded tests [unsupported] Takopi runs no checks. Sources: takopi:spec.
  • Cancellation [supported] /cancel. Sources: takopi:commands.
  • Fairness [unsupported] None. Sources: takopi:spec.
  • Recovery [unsupported] None. Sources: takopi:spec.
  • Shared limits [unsupported] None. Sources: takopi:spec.

Sources: takopi:spec, takopi:telegram, takopi:commands

Human collaboration and control

Agent cross-checked partial

Group chats and forum topics let several Telegram users message the same bot and topic; allowed_user_ids restricts senders; sessions are per sender in group chats, mentions-only trigger mode reduces noise. No presence or attribution beyond Telegram own.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • comments: Telegram replies.
  • presence: Telegram own presence only.
  • coprompting: Several allowed users can prompt; chat sessions store one token per sender.
  • conflicts: Serialization only.
  • attribution: Telegram shows the sender; takopi quotes the prompt.
  • permissions: allowed_user_ids sender allowlist; admin rights for topics.
11 atomic answers
  • Visibility [supported] Group members see progress and results in the topic. Sources: takopi:topics.
  • Discussion [supported] Telegram chat discussion. Sources: takopi:topics.
  • Comments [partial] Telegram replies. Sources: takopi:telegram.
  • Presence [partial] Telegram own presence only. Sources: takopi:telegram.
  • Coprompting [partial] Several allowed users can prompt; chat sessions store one token per sender. Sources: takopi:telegram.
  • Ordering [supported] Per-thread serialization queues overlapping prompts. Sources: takopi:spec.
  • Conflicts [partial] Serialization only. Sources: takopi:spec.
  • Attribution [partial] Telegram shows the sender; takopi quotes the prompt. Sources: takopi:telegram.
  • Permissions [partial] allowed_user_ids sender allowlist; admin rights for topics. Sources: takopi:config, takopi:topics.
  • Plan restrictions [supported] No plans. Sources: takopi:readme.
  • Owner online [supported] The host running takopi must stay online. Sources: takopi:readme.

Sources: takopi:telegram, takopi:topics, takopi:config, takopi:spec, takopi:readme

Agent cross-checked partial

No roles, organisations or SSO: a sender allowlist (allowed_user_ids) and Telegram group admin rights only.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • organization roles: None.
  • project roles: None.
  • task roles: None.
  • membership: Telegram group membership and allowlist.
  • sso: None.
  • provisioning: None.
  • unauthorized access: Updates from senders outside allowed_user_ids are ignored when set; empty allows everyone.
  • revocation: Edit the allowlist (hot reload with watch_config).
9 atomic answers
  • Organization roles [unsupported] None. Sources: takopi:config.
  • Project roles [unsupported] None. Sources: takopi:config.
  • Task roles [unsupported] None. Sources: takopi:config.
  • Membership [partial] Telegram group membership and allowlist. Sources: takopi:config.
  • Sso [unsupported] None. Sources: takopi:config.
  • Provisioning [unsupported] None. Sources: takopi:config.
  • Unauthorized access [partial] Updates from senders outside allowed_user_ids are ignored when set; empty allows everyone. Sources: takopi:config.
  • Revocation [partial] Edit the allowlist (hot reload with watch_config). Sources: takopi:config.
  • Plan scope [supported] No plans. Sources: takopi:readme.

Sources: takopi:config, takopi:topics, takopi:readme

Agent cross-checked partial

No approval workflow: Codex approval requests are auto-accepted and permission requests granted for the turn, Claude runs non-interactively with preconfigured permissions or the dangerous skip flag, MCP elicitation is declined.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • command: Approvals are auto-accepted for Codex and not surfaced for Claude.
  • tool: No tool approval UI.
  • network: None.
  • secret: None.
  • delivery: None.
  • approver identity: None.
  • lifetime: Permission grants are scoped to the turn.
  • allow: Automatic accept in the runner.
  • deny: Claude allowed_tools lists restrict tools.
  • revoke: None.
  • tunnels: None.
  • safer modes: Claude allowed_tools; engine sandboxes.
  • enforcement: Enforced by the engine CLI, not takopi.
14 atomic answers

Sources: takopi:codexrun, takopi:clauderun, takopi:readme

Agent cross-checked partial

No history features of its own: Telegram holds the conversation; takopi writes optional debug logs and a chat sessions state file.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • actions: Logs when enabled.
  • approvals: None.
  • edits: None.
  • discussion: Telegram history.
  • decisions: None.
  • cross user persistence: Topic sessions persist.
  • export: None.
  • mutability: Telegram messages and local files are editable.
  • retention: No retention policy.
  • integrity: None.
11 atomic answers
  • Actions [partial] Logs when enabled. Sources: takopi:env.
  • Approvals [unsupported] None. Sources: takopi:env.
  • Edits [unsupported] None. Sources: takopi:env.
  • Discussion [partial] Telegram history. Sources: takopi:telegram.
  • Decisions [unsupported] None. Sources: takopi:env.
  • Cross user persistence [partial] Topic sessions persist. Sources: takopi:telegram.
  • Cross session persistence [supported] State file. Sources: takopi:telegram.
  • Export [unsupported] None. Sources: takopi:env.
  • Mutability [partial] Telegram messages and local files are editable. Sources: takopi:telegram.
  • Retention [unknown] No retention policy. Sources: takopi:env.
  • Integrity [unsupported] None. Sources: takopi:env.

Sources: takopi:telegram, takopi:env

Agent cross-checked partial

No review experience: progress shows file change actions but no diff view, comments or review queue.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • pending reviews: None.
  • change understanding: Progress lists commands, tools and file changes.
  • evidence navigation: None.
  • comments: None.
  • request changes: Reply with a new instruction.
  • shipping guidance: None.
  • effort: No measurement.
  • missed evidence: None.
  • keyboard: Not applicable.
  • context switching: Topics per repo.
  • roles: None.
  • retained context: Telegram history.
13 atomic answers
  • Pending reviews [unsupported] None. Sources: takopi:readme.
  • Change understanding [partial] Progress lists commands, tools and file changes. Sources: takopi:readme.
  • Evidence navigation [unsupported] None. Sources: takopi:readme.
  • Comments [unsupported] None. Sources: takopi:readme.
  • Request changes [partial] Reply with a new instruction. Sources: takopi:readme.
  • Shipping guidance [unsupported] None. Sources: takopi:readme.
  • Effort [unknown] No measurement. Sources: takopi:spec.
  • Missed evidence [unsupported] None. Sources: takopi:readme.
  • Keyboard [unsupported] Not applicable. Sources: takopi:readme.
  • Narrow screen [supported] Telegram on phones. Sources: takopi:readme.
  • Context switching [partial] Topics per repo. Sources: takopi:topics.
  • Roles [unsupported] None. Sources: takopi:readme.
  • Retained context [partial] Telegram history. Sources: takopi:telegram.

Sources: takopi:readme, takopi:spec, takopi:topics, takopi:telegram

Agent cross-checked partial

Not designed for takeover: a different user would reply to a resume line; resume lines move a session to the terminal; sessions are per sender in group chats.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • ongoing takeover: Reply with a resume line in the topic or terminal.
  • session history: Engine session files and Telegram history.
  • decisions: None.
  • artifacts: /file get fetches files.
  • permissions: allowed_user_ids.
  • runtime context: Context footer ctx: project and branch.
  • ownership: None.
  • attribution: None.
  • context loss: Chat sessions are stored per sender, so another sender starts fresh unless they reply.
  • harness transfer: Resume tokens are per engine; switching engines starts a new session.
12 atomic answers
  • Ongoing takeover [partial] Reply with a resume line in the topic or terminal. Sources: takopi:readme.
  • Same task [supported] Resume token addresses the same engine session. Sources: takopi:telegram.
  • Session history [partial] Engine session files and Telegram history. Sources: takopi:telegram.
  • Decisions [unsupported] None. Sources: takopi:readme.
  • Artifacts [partial] /file get fetches files. Sources: takopi:files.
  • Permissions [partial] allowed_user_ids. Sources: takopi:config.
  • Runtime context [partial] Context footer ctx: project and branch. Sources: takopi:worktrees.
  • Owner disconnect [supported] Host keeps running. Sources: takopi:readme.
  • Ownership [unsupported] None. Sources: takopi:readme.
  • Attribution [unsupported] None. Sources: takopi:readme.
  • Context loss [partial] Chat sessions are stored per sender, so another sender starts fresh unless they reply. Sources: takopi:telegram.
  • Harness transfer [unsupported] Resume tokens are per engine; switching engines starts a new session. Sources: takopi:telegram.

Sources: takopi:readme, takopi:telegram, takopi:files, takopi:config, takopi:worktrees

Verification and delivery

Agent cross-checked partial

Files can be fetched back to Telegram with /file get; no diffs, screenshots, recordings or gallery.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • diffs: None.
  • documents: /file get sends files and directories (50 MiB cap).
  • screenshots: None.
  • recordings: None.
  • previews: None.
  • test outputs: None.
  • reviewer outputs: None.
  • gallery: None.
  • task links: None.
  • revision links: None.
  • persistence: Telegram stores messages.
  • child findings: None.
  • prompt leakage: Not addressed.
13 atomic answers

Sources: takopi:files, takopi:readme, takopi:telegram

Agent cross-checked unsupported

No verification gates: takopi runs no tests or checks; CI exists only for the project itself.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • tests: None.
  • lint: None.
  • types: None.
  • ci: None.
  • independent review: None.
  • spec checks: None.
  • required checks: None.
  • failure blocking: None.
  • requirement conflicts: None.
  • configured policy: None.
  • enforced policy: None.
11 atomic answers

Sources: takopi:spec, takopi:ci

Agent cross-checked partial

Git support is limited to creating branch worktrees; commits, pull requests and merges are left to the engine.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • commits: None.
  • pull requests: None.
  • comments: None.
  • ci response: None.
  • rebase: None.
  • conflicts: None.
  • product state: None.
9 atomic answers

Sources: takopi:worktrees, takopi:wtpy

Agent cross-checked unsupported

No merge or deployment authority: nothing in takopi merges, releases or deploys.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • approve: None.
  • merge: None.
  • release: None.
  • deploy: None.
  • exact revision: None.
  • authority enforcement: None.
6 atomic answers

Sources: takopi:spec

Agent cross-checked partial

No completion evidence: only the final Telegram message.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • commit links: None.
  • pr links: None.
  • build links: None.
  • deployment links: None.
  • delivery status: Final message says done or error.
  • retained evidence: Telegram history.
  • rollback: None.
  • revert: None.
  • stale approval invalidation: None.
9 atomic answers
  • Delivery status [partial] Final message says done or error. Sources: takopi:spec.
  • Retained evidence [partial] Telegram history. Sources: takopi:telegram.
  • Rollback [unsupported] None. Sources: takopi:spec.
  • Revert [unsupported] None. Sources: takopi:spec.
  • Stale approval invalidation [unsupported] None. Sources: takopi:spec.

Sources: takopi:spec, takopi:telegram

Agent cross-checked partial

No batch review or shipping features.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • review queue: None.
  • summaries: Final message summarises the agent answer.
  • grouping: Topics group by repo and branch.
  • risk size filters: None.
  • findings: None.
  • artifacts: None.
  • request changes: Reply.
  • exact revision approval: None.
  • dependency queues: None.
  • next actions: None.
  • stale approval invalidation: None.
  • check deduplication: None.
12 atomic answers
  • Review queue [unsupported] None. Sources: takopi:spec.
  • Summaries [partial] Final message summarises the agent answer. Sources: takopi:spec.
  • Grouping [partial] Topics group by repo and branch. Sources: takopi:topics.
  • Risk size filters [unsupported] None. Sources: takopi:spec.
  • Findings [unsupported] None. Sources: takopi:spec.
  • Artifacts [unsupported] None. Sources: takopi:spec.
  • Request changes [partial] Reply. Sources: takopi:readme.
  • Exact revision approval [unsupported] None. Sources: takopi:spec.
  • Dependency queues [unsupported] None. Sources: takopi:spec.
  • Next actions [unsupported] None. Sources: takopi:spec.
  • Stale approval invalidation [unsupported] None. Sources: takopi:spec.
  • Check deduplication [unsupported] None. Sources: takopi:spec.

Sources: takopi:spec, takopi:topics, takopi:readme

Ownership, privacy and economics

Agent cross-checked partial

MIT license, single public repository, also on PyPI.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • hosted extensions: No hosted component.
  • hosted parity: No hosted offering.
6 atomic answers
  • Client license [supported] MIT. Sources: takopi:license, takopi:repo.
  • Server license [supported] No separate server; the bridge is the one package under MIT. Sources: takopi:license.
  • Hosted extensions [unsupported] No hosted component. Sources: takopi:readme.
  • Source visibility [supported] Public. Sources: takopi:repo.
  • Source revision [supported] Pinned to v0.23.4 (e0123d4). Sources: takopi:rel.
  • Hosted parity [unsupported] No hosted offering. Sources: takopi:readme.

Sources: takopi:license, takopi:repo, takopi:rel, takopi:pypi, takopi:readme

Agent cross-checked partial

Runs on user infrastructure; state is JSON and TOML beside the config; no export or import; no account.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • vendor dependencies: Telegram bot API is required; engines call their providers; voice transcription uses an OpenAI-compatible endpoint when enabled.
  • export: None.
  • import: None.
  • formats: TOML config and JSON state.
  • account independence: Needs a Telegram account and bot, not a takopi account.
  • history portability: Sessions stay in engine stores; no export.
8 atomic answers
  • Self hosting [supported] Self-run process. Sources: takopi:readme.
  • Vendor dependencies [partial] Telegram bot API is required; engines call their providers; voice transcription uses an OpenAI-compatible endpoint when enabled. Sources: takopi:telegram, takopi:voice.
  • Export [unsupported] None. Sources: takopi:config.
  • Import [unsupported] None. Sources: takopi:config.
  • Formats [partial] TOML config and JSON state. Sources: takopi:config, takopi:telegram.
  • Cancellation [supported] Nothing to cancel. Sources: takopi:readme.
  • Account independence [partial] Needs a Telegram account and bot, not a takopi account. Sources: takopi:config.
  • History portability [unsupported] Sessions stay in engine stores; no export. Sources: takopi:telegram.

Sources: takopi:config, takopi:telegram, takopi:readme, takopi:voice

Agent cross-checked partial

No telemetry or analytics in the package; messages flow through Telegram servers (not end-to-end encrypted bot chats), prompts go to the engines providers, and voice notes optionally to an OpenAI-compatible endpoint; files transfer through Telegram.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • code data: Code stays local except content the user sends or fetches through Telegram.
  • prompts: Prompts travel through Telegram to the bridge and then to the engine provider.
  • credentials: Bot token and optional voice key in takopi.toml; engines hold their own.
  • logs: Local logs when enabled.
  • artifacts: Files through Telegram.
  • retention: No retention statement.
  • deletion: /new clears sessions; Telegram deletes messages.
  • training: Provider and Telegram terms govern.
  • residency: Not stated.
  • subprocessors: Telegram and the user chosen engines and transcription endpoint.
  • telemetry disclosure: Environment variable reference lists no telemetry; no privacy document.
  • telemetry controls: None needed.
  • consent prompt: None.
15 atomic answers
  • Code data [partial] Code stays local except content the user sends or fetches through Telegram. Sources: takopi:files.
  • Prompts [partial] Prompts travel through Telegram to the bridge and then to the engine provider. Sources: takopi:telegram.
  • Credentials [partial] Bot token and optional voice key in takopi.toml; engines hold their own. Sources: takopi:config.
  • Logs [partial] Local logs when enabled. Sources: takopi:env.
  • Artifacts [partial] Files through Telegram. Sources: takopi:files.
  • Retention [unknown] No retention statement. Sources: takopi:telegram.
  • Deletion [partial] /new clears sessions; Telegram deletes messages. Sources: takopi:commands.
  • Training [unknown] Provider and Telegram terms govern. Sources: takopi:telegram.
  • Residency [unknown] Not stated. Sources: takopi:telegram.
  • Subprocessors [partial] Telegram and the user chosen engines and transcription endpoint. Sources: takopi:telegram, takopi:voice.
  • Telemetry disclosure [partial] Environment variable reference lists no telemetry; no privacy document. Sources: takopi:env.
  • Telemetry defaults [supported] No telemetry found in src/takopi (bounded search for telemetry, analytics and sentry). Sources: takopi:env.
  • Telemetry controls [unsupported] None needed. Sources: takopi:env.
  • Provider separation [supported] Voice transcription has its own base URL and key. Sources: takopi:config.

Sources: takopi:telegram, takopi:voice, takopi:env, takopi:readme, takopi:files, takopi:config, takopi:commands

Agent cross-checked supported

Free MIT software; no paid plan.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
12 atomic answers

Sources: takopi:readme, takopi:license

Agent cross-checked partial

No takopi cost at any team size; engine usage applies.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • task assumptions: None published.
  • tokens: Not tracked.
  • variable cost: Engine usage varies.
  • unknown cost: Engine costs are not shown.
11 atomic answers

Sources: takopi:readme

Agent cross-checked partial

Open-source Python package at version 0.23.4; releases were frequent until 2026-05-25 and no commit has been pushed since; support through GitHub issues (52 open); no SLA.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • release stage: Version 0.x.
  • support: GitHub issues.
  • response commitments: None.
  • release activity: Releases on 2026-05-15 and 2026-05-25; nothing newer at 2026-11-16.
  • status history: None.
  • deprecation: No statement.
  • export options: None.
8 atomic answers
  • Release stage [partial] Version 0.x. Sources: takopi:rel.
  • Access restrictions [supported] Public on PyPI and GitHub. Sources: takopi:pypi.
  • Support [partial] GitHub issues. Sources: takopi:repo.
  • Response commitments [unsupported] None. Sources: takopi:repo.
  • Release activity [partial] Releases on 2026-05-15 and 2026-05-25; nothing newer at 2026-11-16. Sources: takopi:rel, takopi:changelog.
  • Status history [unsupported] None. Sources: takopi:repo.
  • Deprecation [unknown] No statement. Sources: takopi:repo.
  • Export options [unsupported] None. Sources: takopi:config.

Sources: takopi:rel, takopi:repo, takopi:changelog, takopi:pypi, takopi:config

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

Everything is free.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • credits trial: None.
  • paid only: None.
  • early access: Version 0.x.
10 atomic answers

Sources: takopi:readme, takopi:license, takopi:rel

Agent cross-checked supported

Transparent: nothing is sold.

Scope
Surfaces: Telegram bot interface (messages, replies, topics, inline buttons) served by the takopi process · Version: takopi release v0.23.4 (tag v0.23.4, commit e0123d4, 2026-05-25); the banteg account has one public takopi repository; third-party engine and transport plugins are separate packages and out of scope · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
9 atomic answers

Sources: takopi:readme

Sources

takopi:readme

takopi readme

Telegram bridge for codex, claude code, opencode and pi with projects, git worktrees, stateless resume, progress streaming, parallel runs with per-session queue, voice notes, file transfer, topics and existing subscriptions; requires uv, Python 3.14 and an engine on PATH.

Kind
source-inspected
Locator
features, requirements, install, setup, usage, plugins
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
readme.md
takopi:pyproject

pyproject.toml

Python package with anyio, httpx, openai, pydantic, typer, watchfiles; MIT classifier; OS Independent; Python 3.14.

Kind
source-inspected
Locator
dependencies, classifiers
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
pyproject.toml
takopi:changelog

changelog

Releases through v0.23.4 (2026-05-25): Codex app-server default, steer and cancel buttons, reasoning overrides, retry of Telegram network errors.

Kind
source-inspected
Locator
v0.22 to v0.23.4
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
changelog.md
takopi:commands

Commands and directives

Directives /engine, /project and @branch, in-chat commands /cancel /agent /model /reasoning /trigger /file /topic /ctx /new, and CLI commands init, chat-id, doctor, plugins.

Kind
source-inspected
Locator
Message directives, Telegram in-chat commands, CLI
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/commands-and-directives.md
takopi:telegram

Telegram transport

Voice transcription, mentions-only trigger mode, chat sessions stored in telegram_chat_sessions_state.json, forum topics, outbox with rate limiting and backoff.

Kind
source-inspected
Locator
Incoming messages, Trigger mode, Chat sessions, Forum topics, Outbox, Rate limiting
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/transports/telegram.md
takopi:config

Configuration reference

Config at ~/.takopi/takopi.toml: bot token, chat id, allowed_user_ids, session_mode, voice, topics, files, projects with worktrees_dir and worktree_base, plugins.

Kind
source-inspected
Locator
Top-level keys, transports.telegram, projects, plugins
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/config.md
takopi:spec

Takopi specification

Resume tokens and lines, normalized events, per-thread serialization, scheduling, progress and cancellation, lockfile for a single instance.

Kind
source-inspected
Locator
Sections 3 to 10
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/specification.md
takopi:codexrun

Codex runner

Runs codex app-server by default and answers approval requests with accept, permission requests with the requested scope and MCP elicitation with decline.

Kind
source-inspected
Locator
_handle_server_request
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
src/takopi/runners/codex.py
takopi:plugin

Plugin API

Entry-point plugins for engines, transports and commands.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/plugin-api.md
takopi:clauderun

Claude runner

Runs claude -p non-interactively; permissions must be preconfigured or dangerously_skip_permissions set; no interactive question handling.

Kind
source-inspected
Locator
Goals, Permissions / non-interactive runs, Config
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/runners/claude/runner.md
takopi:worktrees

Worktrees how-to

@branch runs a task in a dedicated git worktree under worktrees_dir; ctx footer carries context forward.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/how-to/worktrees.md
takopi:wtpy

Worktree implementation

Runs git worktree add (with -b for a new branch) under the project worktrees directory and refuses a non-worktree path.

Kind
source-inspected
Locator
_git_worktree_add
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
src/takopi/worktrees.py
takopi:topics

Topics

Forum topics bind a repo and branch with their own session and default engine for team chats.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/how-to/topics.md
takopi:files

File transfer

Optional /file put and /file get with upload and download size limits and a deny glob list.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/how-to/file-transfer.md
takopi:voice

Voice notes

Optional voice transcription through an OpenAI-compatible transcription endpoint.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/how-to/voice-notes.md
takopi:schedule

Schedule tasks

Relies on Telegram native scheduled messages (including daily and weekly recurrence); takopi has no scheduler of its own.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/how-to/schedule-tasks.md
takopi:env

Environment variables

Only logging, non-interactive and Pi directory variables; no telemetry settings.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
docs/reference/env-vars.md
takopi:usage-payload

takopi Claude runner usage payload

The Claude runner copies total_cost_usd, duration, num_turns and usage from the result event into the completed event, and the Pi runner keeps the last message usage. A bounded search of src/takopi/*.py, telegram/ and presenter/markdown rendering found nowhere that displays, stores or exports it.

Kind
source-inspected
Locator
_usage_payload; pi.py MessageEnd/AgentEnd usage; search of src/takopi for usage and cost
Source date
Not stated
Retrieved
2026-11-17
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
src/takopi/runners/claude.py
takopi:ci

CI workflow

CI runs ruff format and lint checks, ty type checking, pytest, uv build and a docs build, and notifies on commits.

Kind
source-inspected
Locator
jobs
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
.github/workflows/ci.yml
takopi:repo

banteg/takopi repository

MIT license, 1,059 stars on 2026-11-16, last push 2026-05-25, not archived, 52 open issues and pull requests.

Kind
documented
Locator
Repository header and GitHub API
Source date
Not stated
Retrieved
2026-11-16
takopi:rel

takopi v0.23.4 release

Release v0.23.4 published 2026-05-25; also published to PyPI as takopi 0.23.4.

Kind
documented
Locator
Release page
Source date
2026-05-25
Retrieved
2026-11-16
takopi:pypi

takopi on PyPI

Package takopi 0.23.4 with documentation, homepage, issues and repository links to takopi.dev and GitHub.

Kind
documented
Locator
Project page
Source date
Not stated
Retrieved
2026-11-16
takopi:license

MIT License

MIT license text.

Kind
source-inspected
Locator
Whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
e0123d4f9b2588bf45ec7250ad648c324e20ce20
Path
LICENSE

Comparisons with takopi

Compare takopi with any other product on adecomparison.com.