Repository navigation
Show the plugin's version and offer Codex's own update in the panel header - #17
Merged
Merged
Conversation
…eader The header shows the running version beside MainSequence, and where it stands against the catalog Codex installs from (the mainsequence marketplace on main): Up to date, Update to x.y.z, x.y.z installed · start a new chat, or Check for updates when the catalog cannot be read. One successful check serves the chat's panels for 30 minutes. Update asks first, then runs the Codex binary that started the server: `codex plugin marketplace upgrade mainsequence` and `codex plugin add mainsequence@mainsequence`. When those commands cannot run, the plugin came from another marketplace, or the update fails, the header shows the two commands to run in a terminal. The open chat keeps its version until a new chat starts. The new mainsequence_plugin tool is app-only, so the model never updates the plugin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The panel header now always shows the running plugin version next to MainSequence, plus where it stands against the catalog Codex installs from (
.agents/plugins/marketplace.jsononmain):This is the Codex counterpart of the Claude Desktop header that shipped in 0.4.23 (mainsequence-sdk/mainsequence-claude-desktop#33).
How
src/hosts/pluginUpdate.tscompares the running version with the published catalog and with the copy Codex has installed (codex plugin list --json). One successful check serves the chat's panels for 30 minutes; Check for updates reads again.codex plugin marketplace upgrade mainsequence, thencodex plugin add mainsequence@mainsequence. It only ever runs thecodexbinary that started the server (the parent process), never anothercodexonPATH.mainsequence_plugintool is app-only, so the model can't update the plugin.mainsequence-local), or the update fails, the header shows the two terminal commands instead.Testing
npm run release:checkpasses: 65 tests, and the packed 0.7.12 installs with devtools 0.3.14.tests/plugin-update.test.cjscovers the module, and three new panel tests intests/panel-ui.test.cjscover the header: confirmed update, terminal-steps fallback, manual re-check.CODEX_HOME: installed 0.7.10 from the GitHub marketplace, pointed it atmain, and the module reported "0.7.11 available", updated it, then reported "0.7.11 installed · start a new chat".scripts/preview-panel.mjsin both themes; at 360px the status wraps under the name without horizontal scroll.No version bump; releasing is separate.
🤖 Generated with Claude Code