Local file context
Start from your repository and directories instead of copying an entire project into another chat window.
Checking sign-in status
01LOCAL WORKSPACE / CODING CLIENT 07
A local-first AI coding client for your workspace
Cocode is a local-first AI coding client: files, terminals, and task context stay around your workspace while you choose the model connection.
Capabilities and limits follow the current release
Local execution flow
Commands, tests, diffs, and results stay centered on your machine or a remote workspace you control.
Replaceable model access
Use a DeepSeek-compatible API, self-hosted endpoint, gateway, or Cocode Nut without locking the client to one provider.
02Why it matters
Local-first does not mean isolated
Cocode puts local files and execution at the center while allowing a remote model service. You keep continuous repository context without giving up model choice.
Built for repositories, not isolated snippets
A task starts with the directory and dependencies, moves through edits, commands, and tests, then ends with a diff and conclusion in the same session.
↗
Clear boundaries make real development work easier to trust.
One task across desktop, terminal, and SSH
Use the GUI for structure and visual review, and the TUI for keyboard-first work on remote machines. Both connect to the same Host and Session.
06FAQ
Before you start, make the boundaries clear.
Is Cocode a fully offline AI coding client?
Cocode should not be described as fully offline by default. It supports local files and execution, while model access can be remote or self-hosted depending on your configuration.
Can I use my own API key?
Yes. Cocode supports a DeepSeek-compatible API key, self-hosted endpoint, gateway, or Cocode Nut.
Does code leave my machine automatically?
Whether model requests leave the local environment depends on the model service and configuration you select. Review the endpoint, privacy notice, and organization policy before use.