Versions and updates
The Zekoder workflow has parts that update on their own schedule. The Version tab on the Zekoder page shows all of them. Select Zekoder in the sidebar, then Version.
What the tab shows
The header shows your Zekoder Desktop version, the release channel, and Check now, which checks every part at once.
| Row | What it is |
|---|---|
| Zekoder plugin | The Issues, Reports, and Zekoder pages. Updates arrive with the desktop app or as signed plugin updates. |
| Skills and agents | The /zekoder-* commands, the agent roles, and their wiring into Claude Code and Codex. |
| zekoder-mcp | The MCP server agents and the Issues screen use to read and write .zekoder/. It ships with the skills. |
| Zekoder server | The daemon on this host. It updates with Zekoder Desktop. |
A dot on the tab means an install, update, or migration failed, or a row has an error. Expand the row to see the log.
Skills install and update themselves
The skills are installed once for your user on each host, not into each repository. Zekoder installs or updates them:
- shortly after the app starts, then every 6 hours,
- when you create a workspace or start an agent,
- when you select Install, Update, or Retry.
The download is checked against a published checksum. If an install fails, the previous version keeps working.
The channel decides which release you get: Stable, or Beta for earlier access. Change it here or in Settings → About; see Release channels.
After an update the row reads "Skills updated to X at HH:MM". Agents started before then still use the old version: reload them with Reload agent, or run /mcp reconnect zekoder in Claude Code. Restart Codex agents.
Choose agents
The skills install for Claude Code and Codex when those providers are enabled on the host. OpenCode and Oh My Pi are opt-in: select them on the Skills and agents row. Agents you already installed stay installed.
Migrate an older repository
Older versions of Zekoder installed the skills into each repository. Those repositories still carry the old copies. When an old copy conflicts with the shared installation, Implement and Promote refuse to start and point you here.
- On the Skills and agents row, pick the project or worktree.
- Select Preview migration. Nothing changes yet; you see which files would be removed and which are kept as conflicts.
- Select Apply migration.
Migration removes only unchanged files the old installer wrote and the MCP entries it added. Files you edited, files tracked in git, and files Zekoder did not create are kept and listed as conflicts for you to handle. Plans, notes, and settings in .zekoder/ are never touched.
Migrating the skills is separate from /zekoder-migrate, which upgrades the format of the .zekoder/ folder itself.