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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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).
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
Command [unsupported] Approvals are auto-accepted for Codex and not surfaced for Claude. Sources: takopi:codexrun.
Tool [unsupported] No tool approval UI. Sources: takopi:clauderun.
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.
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.
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.
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).
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
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
Branches [supported] @branch creates or checks out branches in worktrees. Sources: takopi:wtpy.
Worktrees [supported] Worktrees under worktrees_dir. Sources: takopi:wtpy.
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
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.
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.
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
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.
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.
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.
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
Currency [supported] No price. Sources: takopi:readme.
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
One person [supported] Free. Sources: takopi:readme.
Two people [supported] Free. Sources: takopi:readme.
Five people [supported] Free. Sources: takopi:readme.
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.
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
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
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.
Voice transcription, mentions-only trigger mode, chat sessions stored in telegram_chat_sessions_state.json, forum topics, outbox with rate limiting and backoff.
Runs codex app-server by default and answers approval requests with accept, permission requests with the requested scope and MCP elicitation with decline.
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