The Issues screen
The Issues screen lists every work item in your Zekoder projects: features, bugs, followups, vendor issues, decisions, and ideas. It reads them through the same Zekoder MCP server your agents use, so it always matches what agents see.
Open it
- Select Issues in the sidebar to see items across projects.
- In a workspace, open + → Zekoder issues to see that workspace's project only.
- Press
Cmd+Kand choose Open Zekoder issues.
A project appears only when its folder contains a .zekoder/ folder. If none does, the screen says "No Zekoder project has a .zekoder/ workspace yet." See Set up a repository.
Find items
- Project: when more than one project has a
.zekoder/folder, pick one from the Project menu. - Status: pick one of Open, Planned, In Progress, Done, or All.
Filter Shows Open Open and in-progress items (the default) Planned Items ready to implement ( open/planned)In Progress Items being implemented Done Closed and cancelled items - Type: turn on any of Features, Bugs, Followups, Vendor issues, Decisions, and Ideas. With none selected, every type shows.
- Search issues: full-text search, ranked by relevance.
The screen remembers your project and filters. Select the refresh button to reload.
Each row shows the title, the type and ID, the severity for bugs, a short excerpt, and the status.
Read an item
Select an item to open its details: a side panel on wide windows, a full-screen sheet on narrow ones.
- Details: the item's file path and fields such as status, sub-status, dates, and author.
- Relations: items it depends on, blocks, or relates to.
- Packages: for features, the packages the plan splits into. Expand one to see its status, branch, and files.
- Documents: the item's documents. Select one to read it.
Implement an item
Implement appears on features, bugs, and followups. It is available only when the item is open/planned, meaning a plan has been approved.
When you select it, Zekoder:
- Checks that the Zekoder skills are installed for the coding provider.
- Starts an agent named Implement <id> in the project's workspace, using your Coding defaults for provider, model, effort, and access mode.
- Sends the provider's implement command (
$zekoder-implement <id>on Codex and/zekoder-implement <id>on other providers) and takes you to the agent.
Copy command copies the command for your Coding provider for any item, so you can run it in an agent of your choice.
Promote an idea
Promote idea appears on ideas that are open/captured. It starts an agent named Promote <id> with your Planning defaults and sends /zekoder-promote <id>. The agent asks whether the idea becomes a feature, a followup, or a decision, then plans or records it and closes the idea as promoted.
Migrate an old workspace
When a project's .zekoder/ folder was made by an older version, the screen shows a warning and a Migrate button. It starts an agent named Migrate zekoder workspace that runs /zekoder-migrate: it previews the changes, applies them, and asks before committing.
When a button does not start an agent
| Message | What to do |
|---|---|
| "No coding provider is set yet." or "No planning provider is set yet." | Select Choose a provider and pick one, or set it in project settings. |
| "Zekoder is not installed for this user yet." | Open Zekoder → Version and install it. |
| "Only a planned feature, bug or followup can be implemented." | The item changed since the screen loaded. Refresh, or plan it with /zekoder-plan. |
| A model or effort error naming a setting | The saved model is not offered by the provider. Change it in project or machine defaults. |