@dev-mainsequence/codex-plugin 0.3.0 → 0.7.9

package/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mainsequence",
-  "version": "0.3.0",
-  "description": "Use MainSequence project MCPs from conversation and run explicit developer commands with the bundled runner.",
+  "version": "0.7.9",
+  "description": "Message MainSequence agents in Codex chat, recover saved replies, discover project MCPs and run developer commands using your shared session.",
   "author": {
     "name": "MainSequence"
   },
@@ -9,13 +9,14 @@
   "hooks": "./hooks/hooks.json",
   "skills": "./skills/",
   "interface": {
-    "displayName": "MainSequence Developer Tools",
-    "shortDescription": "Use project MCPs and run MainSequence developer commands.",
+    "displayName": "MainSequence",
+    "shortDescription": "Agents, messages and tools with your shared MainSequence session.",
     "developerName": "MainSequence",
     "category": "Productivity",
     "websiteUrl": "https://www.main-sequence.io/",
     "composerIcon": "./assets/mainsequence-icon.svg",
     "logo": "./assets/mainsequence-icon.svg",
     "logoDark": "./assets/mainsequence-icon.svg"
-  }
+  },
+  "mcpServers": "./.mcp.json"
 }

package/.mcp.json

@@ -0,0 +1,17 @@
+{
+  "mcpServers": {
+    "mainsequence": {
+      "command": "node",
+      "args": [
+        "./dist/panel-server.js"
+      ],
+      "cwd": ".",
+      "env_vars": [
+        "MAINSEQUENCE_ENDPOINT",
+        "MAINSEQUENCE_ACCESS_TOKEN",
+        "MAINSEQUENCE_REFRESH_TOKEN"
+      ],
+      "tool_timeout_sec": 300
+    }
+  }
+}

package/README.md

@@ -1,14 +1,32 @@
 # MainSequence for Codex
 
-The `mainsequence` plugin registers the `ms` slash-menu entry in Codex and executes its
-commands with a trusted `UserPromptSubmit` hook before inference: login, session status,
-repositories, project status, dependency sync, SDK updates and more, with readable results
-and no model call. Its `mainsequence-mcp` skill lets Codex discover MainSequence project
-MCPs in conversation, remember a selection and use that project's tools through a bundled
-MCP client.
-
-Version **0.3.0** is the first release from this repository. Until devtools 0.2.8 the plugin
-was built and published from
+This repository is the **MainSequence Codex plugin**. Its production code lives in
+`src/`, its Codex manifest in `manifests/codex/`, and its installable bundle in `codex/`.
+
+The **0.7.1 development build** follows Claude's MainSequence panel layout using
+Codex theme tokens: Home, Code, Projects, Agents, Tools, Activity and Settings.
+It includes repository setup and maintenance, project setup and links, deployment
+history/stages/logs, shared account/settings controls, direct messages and agent tasks.
+Replies and task results use native MCP tools and remain in Codex conversation context.
+
+Ask Codex to **open MainSequence**. Shared devtools **0.3.5** owns authentication,
+account binding, domain APIs, local project operations, authenticated assets and durable
+delivery. Claude's repository and dependency remain unchanged. See the
+[capability matrix and verification](docs/agents-tools-panel.md), including the stock
+Codex host differences. No probe or custom Codex build is shipped.
+
+Choose **Talk**, select **Message** or **Task** when the agent supports both, write a
+message, then **Send in Codex**. The reply returns through a native
+MCP tool and stays in chat context. After Stop, use **Messages and recovery → Recover in
+Codex** on the original request. Recovery reuses saved work; an unknown remote outcome
+blocks resend. Browsing or selecting an example never sends a message automatically.
+
+The plugin also registers the `ms` slash-menu entry for explicit developer commands and
+the `mainsequence-mcp` skill for conversational project MCP access. The independent
+Claude application is unchanged.
+
+Version 0.3.1 added saved MCP names (see [the release notes](docs/codex-verification.md)). Version 0.3.0 was the first
+release from this repository. Until devtools 0.2.8 the plugin was built and published from
 [mainsequence-devtools](https://github.com/mainsequence-sdk/mainsequence-devtools) under the
 name `mainsequence-devtools` ([ADR 0003 there](https://github.com/mainsequence-sdk/mainsequence-devtools/blob/main/docs/adr/0003-codex-plugin-extraction.md)).
 The shared implementation is still that package; this repository owns the hook adapter, the
@@ -84,6 +102,19 @@ metatable-mcp", "Use it to list my tables." See
 [conversational project MCP connections](docs/conversational-mcp.md) and
 [ADR 0002](docs/adr/0002-conversational-project-mcp-client.md).
 
+Every saved project MCP's tools are also registered directly, as the Claude Desktop
+plugin registers them: `ms_<tool>_<hash>` (for example `ms_crm_contacts_list_…`), each
+with the project's own schema and bound to one saved connection and environment. Codex
+calls them like any other tool, with no `contextId` or environment selection. The list
+comes from devtools' shared project-tool catalog (`project-tool-catalog.json` beside the
+shared CLI state, the same names, schemas and results as the Claude Desktop plugin; devtools
+ADR 0004) and is refreshed in the background; a connection saved in the current chat appears
+in the next chat, and is usable at once through `mainsequence_tools` /
+`mainsequence_call_tool`. A cold project MCP can take over a minute to answer: devtools gives
+project requests 120 s and honours a tool's advertised timeout up to 300 s, and the plugin's
+server allows Codex tool calls 300 seconds (`tool_timeout_sec` in `.mcp.json`) instead of
+the host default of 60.
+
 ## Architecture and development
 
 Shared functionality comes from the exact `@dev-mainsequence/devtools` package API. The
@@ -109,18 +140,25 @@ results. `tests/dependency-boundary.test.cjs` forbids private devtools imports.
 recorded in `package-lock.json`. While that version is not published yet, run
 
 ```sh
-node scripts/install-devtools.cjs /path/to/dev-mainsequence-devtools-0.3.0.tgz
+node scripts/install-devtools.cjs /path/to/dev-mainsequence-devtools-0.3.2.tgz
 ```
 
 with the archive from `npm pack` of the devtools release branch, or without an argument to
 build it from the devtools repository at `DEVTOOLS_SOURCE_REF` (default `v<pinned version>`).
 Either way the archive must match the lockfile integrity, and the registry pin is not
 changed (`scripts/use-local-devtools.cjs`). CI does the same until the version is
-published. After publication, confirm that `npm view @dev-mainsequence/devtools@0.3.0
+published. After publication, confirm that `npm view @dev-mainsequence/devtools@0.3.2
 dist.integrity` equals the lockfile entry before tagging a release; if the registry archive
 differs, update the lockfile and rebuild so `build-info.json` records the published
 integrity.
 
+For a discovery upgrade, use the exact devtools archive while it is unpublished;
+with build dependencies already installed,
+`node scripts/use-local-devtools.cjs /path/to/dev-mainsequence-devtools-0.3.2.tgz` verifies
+its integrity and stages it without changing the registry pin. Publish devtools first,
+verify its registry integrity, then release the Codex plugin. No desktop activation
+or authenticated live-service acceptance is implied by a successful local build.
+
 ### Verification and release
 
 ```sh