| Is a paid API required? |
No; use a local compatible model. Tools and extensions may still access external services. |
| Which binary starts the interface? |
gdc-tui; gdc provides headless, server and data commands. |
| Must I start a server? |
No for local TUI use. Use gdc serve for an explicit server deployment. |
| Does every edit ask for approval? |
No. Permissions, profile rules and remembered grants decide each operation. |
| How do I restrict files or commands? |
Configure deny rules or select a restricted profile. |
| Is the API key shown in help? |
Its environment value is hidden for --api-key. Keep credentials out of shared config. |
| Can I resume a session? |
Open it in the TUI or use gdc print --session-id <id> --resume. |
| Why does CLI history differ from TUI history? |
Local TUI databases are per project; CLI/server defaults use another database. |
| How do I add tools? |
Connect MCP or install plugins. |
| How do I supply conventions? |
Use skills for procedures and memory for durable notes. |
| Where should I investigate a failure? |
Troubleshooting. |