FAQ

Do I need an internet connection or a paid API?

No. gdc works entirely against a local model — Ollama, llama.cpp, vLLM, or LM Studio — so your code never leaves your machine and there's no per-token bill. Hosted providers are supported too if you prefer them. See Model providers.

Which model should I use?

For reading, editing code, and running commands, a coding-focused, instruction-tuned model generally behaves best. Larger models are more capable but slower. Try a few and see what fits your machine. See Model providers.

What's the difference between gdc and gdc-tui?

gdc-tui is the interactive terminal app — the everyday experience. gdc is the headless command line for scripts, automation, and managing your data. See Operating modes.

Do I have to run a server?

No. gdc-tui runs everything it needs on its own. You only run gdc serve for shared or remote setups. See the Admin guide.

Will the agent run commands or change files without asking?

Not in interactive use — it asks before anything with side effects, and denies by default when uncertain. Headless runs deny such actions unless you pass --auto-approve. See Permissions.

Can I stop it from touching certain files or commands?

Yes. Set deny rules in configuration, or use a restrictive profile that removes risky tools entirely.

Is my API key safe in logs?

gdc never prints your API key in help output or error messages. For shared config files, prefer the GDC_API_KEY environment variable over writing the key into the file.

Where is my data stored?

In ~/.gdc/ — sessions, configuration, memory, and plugins. Nothing is written outside your project and this folder unless you point gdc elsewhere. See Installation.

Can I resume a previous conversation?

Yes. Every session is saved. Reopen one from the sessions list in the app, or use gdc print --session-id <id> --resume on the command line. See Sessions & projects.

How do I add my own tools?

Connect an MCP server for external tools and services, or install a plugin for self-contained ones.

How do I make the agent follow my conventions?

Record durable facts in memory, write repeatable procedures as skills, and pick an output style for tone.

Something isn't working — where do I start?

See Troubleshooting.