Skip to content

TUI or Service?

DuckAgent has two main user-facing entry points.

Entry pointCommandUse it when
TUIduckYou want to chat locally, approve actions, switch models, switch profiles, and work in a terminal.
Gateway serviceduck gateway service startYou want external chat apps, webhooks, voice bridges, or API clients to talk to DuckAgent.

The TUI is foreground and interactive. It supports streaming output, Markdown, multiline input, bracketed paste, slash commands, approvals, model setup, profile management, and startup avatars.

Use it for local work:

Terminal window
duck

Gateway service is profile-scoped. It starts configured channel adapters and routes external messages into the same Agent Loop.

Terminal window
duck gateway service start
duck gateway service log
duck gateway service stop

service log observes routed messages. It does not replace the running service.

The TUI and Gateway share session-control commands:

/new
/resume
/resume <number>
/rewind
/rewind <number>

These commands append session transitions instead of rewriting old session history.

/rewind <number> can also restore tracked file changes from built-in file tools when the current file state still matches the recorded post-change checksum. See Session Rewind for details.