Quick start

Go from a fresh install to a running agent, then to your first planned and implemented change.

This guide takes about fifteen minutes. You need Zekoder Desktop installed and Claude Code or Codex signed in on your computer.

1. Add a project

  1. On the home screen, select Add a project, or Add project at the bottom of the sidebar.
  2. Type a path or select Browse…, pick the folder of a git repository, and confirm.

The project appears in the sidebar with one workspace: your folder as it is on disk.

2. Start an agent

  1. Select the workspace. A new agent tab opens with the composer focused.
  2. Pick the provider and model in the composer toolbar.
  3. Describe a small task, for example "Explain how this project is built and tested", and press Enter.

The agent works in the project folder. If it asks for permission to run a command or edit a file, a Permission Required card appears: choose Accept or Deny. See Agents and the composer for modes, queued messages, and attachments.

3. Install the Zekoder skills

The Zekoder workflow needs its skills, agents, and MCP server installed for your user on this computer. The app does this automatically after it starts and before each new agent. To check:

  1. Select Zekoder in the sidebar and open the Version tab.
  2. The Skills and agents row shows the installed version. If it says it is not installed, select Install.

Agents that were already running when the skills were installed need a reload: open the agent tab's menu and select Reload agent.

4. Choose your planning and coding providers

On the Zekoder page, a Set up providers banner appears until you pick them.

  1. Open the Defaults tab.
  2. Under Planning, set Provider (and optionally Model, Effort, Access mode).
  3. Do the same under Coding.

Planning agents write and review plans. Coding agents implement them.

5. Plan your first change

In an agent tab on your project, run:

/zekoder-plan Add a --version flag to the CLI

On Codex, type $zekoder-plan instead of /zekoder-plan.

The first time you plan in a repository, Zekoder offers to set it up: it creates the .zekoder/ folder, writes a short description of the repository, and asks a few one-time questions (merge mode, simplify mode, package limit). Approve each step. Then the planner asks clarifying questions, writes the plan, has it reviewed, and asks you to approve it before committing. See what /zekoder-plan does.

6. Implement it

  1. Select Issues in the sidebar. Your new item shows under the Open filter with status open.
  2. Select the item to open its details.
  3. Select Implement. Zekoder starts a coding agent that runs /zekoder-implement <id> and takes you to it.

The coding agent confirms the merge mode, splits the work into tasks, runs each in its own git worktree, reviews and checks the result, and merges it, either through a pull request or locally. When it finishes, the item moves to Done. See what /zekoder-implement does.

Next steps

ZeKoder

The flight recorder for AI-built software.

ZeKoder is a product of Cybernetic Labs Ltd, London.