preloader
blog post

AGTerm now runs Calliope as its engine

author image

AGTerm is our web terminal for AI coding agents: Express, node-pty, and tmux on the server, Next.js and xterm.js in the browser, deployable standalone or as a per-user container behind JupyterHub. It gives every agent a persistent session that survives restarts and disconnects, split panes, recordings with replay, and an agent builder that saves engine, provider, and model as YAML.

Until this week it also carried its own CLI and its own agent orchestration code. That is gone. AGTerm 1.6 vendors @calliopelabs/cli 3.0 and runs Calliope as the built-in engine, next to Claude Code, Codex, OpenCode, and Antigravity in the roster.

The wiring is small on purpose. When you launch a Calliope session, AGTerm resolves the command in order: an explicit CALLIOPE_BIN override, then a calliope on PATH so a locally linked dev build wins, then the vendored release. Provider and model come from CALLIOPE_PROVIDER and CALLIOPE_MODEL, and the full backend list applies, from Anthropic and OpenAI down to a local Ollama.

What AGTerm gained by deleting its own agent code: hash-chained audit logs for every Calliope session, budget caps, the policy hook, and a config format that migrates itself. One engine to maintain instead of two, and it works out of the box.

Related Articles