A mod is a set of patches to a harness like OpenCode or Codex, made against one of its releases. Install one and your opencode becomes that release with the mod built in. Your stock install is never touched, and you can switch back any time.
Installs the openmods command. Then openmods install <owner>/<mod>, and pick the harness. Read the script first if you like; it is short.
| Mod | Harnesses and releases |
|---|---|
| shouryamaanjain/session-history Adds session_history_search and session_history_read: the agent can find and reread earlier turns from this project's saved sessions, after compaction or from other sessions. |
fx 0.0.12 · behind Codex CLI 0.161.0 · behind OpenCode 2.0.24 · behind |
| shouryamaanjain/space-invaders Adds /invaders: Space Invaders while the agent keeps working, in the right half of OpenCode's session screen or in Codex's bottom pane. |
Codex CLI 0.160.1 · behind OpenCode 2.0.24 · behind |
A mod is named owner/mod and supports one or more harnesses, each with its own patches made against one of that harness's releases. openmods install clones that release, applies the patches, builds it with the exact toolchain the release pins, and puts the result first on your PATH. openmods off steps aside so the stock binary runs again.
When a harness ships a new release, CI applies and typechecks every mod for it, unless the release changed how the harness builds; then the mods wait until a maintainer has built it. A mod that still works has its release moved forward here automatically. A mod that does not stays on its last working release, shows as behind, and its maintainers get an issue with the error and the steps to rebase.