Skip to main content
This is a closest-match map: the gt and gc CLIs have non-identical architectures, so each row gives the nearest gc or bd equivalent. Two rules help a lot to find the closest home (gc or bd) for a command equivalent:
  • the closest home is gc if the gt command is about orchestration, sessions, routing, hooks, or runtime behavior
  • the closest home is bd if the gt command is really about bead CRUD or bead content.
See the gc CLI reference and the bd CLI reference for the full CLI surfaces, and The six primitives for the canonical model these commands map onto.

Workspace And Runtime

Configuration And Extension

Work Routing And Workflow

Sessions, Roles, And Agents

Communication And Nudges

Beads, Events, And Diagnostics

Practical Translation Rule

If you are unsure where a gt command went, ask this in order:
  1. Is it now just gc with nearly the same name?
  2. Is it really a bead operation that should stay in bd?
  3. Is it no longer a special command because Gas City moved that behavior into config, orders, waits, formulas, or orchestrator logic?
Last modified on September 19, 2026