Why terminal-native agents still matter
A terminal coding agent is useful when the shell is already the center of your work: remote machines, Git-heavy projects, scripts, SSH sessions, and fast project navigation. It should work with the files and commands you already use instead of duplicating them in a web dashboard.
Truss offers both a CLI and a terminal UI. They share the runtime model and provider configuration, but they serve different kinds of work.
Use the CLI for repeatable commands
The CLI is the better fit when you want a small surface area, shell composition, or automation. You can configure a profile, ask a scoped question, and integrate a command into an existing script or terminal habit.
Keep automation narrow and observable. An agent command can help with a focused review or generation task, but your CI, tests, and deployment process should remain explicit rather than becoming an opaque prompt.
Use the TUI for interactive workspace work
A terminal UI is better when you want files, Git status, agent chat, terminal output, and model controls together while staying keyboard-first. It gives you more workspace visibility without requiring a graphical editor.
The TUI is especially useful on machines where a desktop client is not practical but a browser-only agent would feel disconnected from the repository.
Keep the same profile across surfaces
The important part is not choosing CLI or TUI forever. It is keeping a stable provider and permission model. You can configure a local endpoint for one session, choose a BYOK model for another, and move between terminal and editor clients without a separate agent personality for every surface.
Start from the simplest surface that matches the task. When the task grows, move to the client that gives you better context and review controls—not a different vendor.
Next steps
Put it to work in your own workspace.
Pick the surface that fits your day, then connect a model you control.
FAQ
Questions developers ask before switching.
Can I use a local model from the Truss CLI?
Yes. Configure a local endpoint profile and use it from the CLI or TUI.
Is a terminal coding agent only for Linux?
No. Terminal workflows are useful anywhere you have a supported shell and can run the Truss CLI.