Devtools 0.3.17

One repositories folder for every MainSequence tool, and agent storage that survives a killed process.

• writeWorkspacePreferences({ backend?, baseDir?, commandCenterUrl? }) saves only the fields given into the mainsequence CLI's configuration and keeps every other setting, so Claude Desktop saves the repositories folder alone where the Codex plugin and the CLI keep it. A call with none is refused.
• readWorkspacePreferences also returns baseDirSaved: whether the folder comes from that configuration or the <home>/mainsequence default.
• The saved agent requests' lock appears with its owner already recorded in it. A process killed while taking it no longer leaves an empty lock that made every later call fail with "Saved agent requests could not be read safely"; an empty lock left by an older version is removed once it is ten seconds old.

npm: @dev-mainsequence/devtools@0.3.17, integrity sha512-lwh2hnyb1cilfc2LKwUHrNdCavLjkE1wnYtpNdPVzJMsK94Jcn7N/tr1muVWwTmF66YhdfaHFnQwxMuOh8QVCw==.

Devtools 0.3.16

The repositories folder is read as the mainsequence CLI reads it, by every action.

• repositoriesFolder(value, home?) (exported) follows the CLI's normalize_mainsequence_path: ~ is the home folder, a bare name such as mainsequence-dev is a folder in it, and any other path is an ordinary one.
• Setup no longer resolves a bare name against the working directory. For the Claude worker that is the Code session's folder, so a session open in another directory cloned into a mainsequence-dev folder inside it.
• local-repositories and the other project operations, organization project setup and saved workspace settings accept a bare name instead of rejecting it as not absolute; settings save it absolute, as the CLI saves mainsequence_path.
• Checkouts stay in <base>/<organization>/projects/, the folder the CLI uses from SDK 9.0.33.

npm: @dev-mainsequence/devtools@0.3.16, integrity sha512-pUjv7gheqrMLslOXJvo9itf90topkYdx5poeSDs0ZuJSgvv3EUaTP79pp2x0sFX8pM4ginS46m2NeMD0ut5x0w==.

Devtools 0.3.15

Hosts now know when the saved MainSequence login ends, and a missing permission no longer asks you to sign in again.

• auth-status reports sessionEndsAt, the saved login's end (its refresh token's expiry; the backend ends a CLI/desktop login a fixed time after sign-in, five days by default, and does not rotate refresh tokens). The summary names it: "The selected session is usable until … UTC."
• Once that moment has passed, the session reads as signed out without contacting the backend. A checked status, every request and refresh-token answer "The saved session for … ended on … UTC. Sign in again." and send nothing; the saved session is kept for the next sign-in to replace.
• HTTP 403 is a new error code, FORBIDDEN, for the platform API and project MCP endpoints: no renewal, no retry and no sign-in prompt. 401 stays AUTH_REJECTED: the backend answers 401 for every expired, revoked or unknown login.

Hosts that check authenticated or AUTH_REJECTED / NOT_AUTHENTICATED get the right state without changes; Claude Desktop 0.4.25 adds the warning before the end.

npm: @dev-mainsequence/devtools@0.3.15, integrity sha512-YBU65IB57QMz3A/fcZCOaSSgdT7wND1iCdLmz0cItu57qsjm7AmUxYbXKw5DcfucJtT//IqxZDMK1zn8cj1kWQ==.

Devtools 0.3.13

Documentation release; no runtime change.

• The README opens with "Which MainSequence tool do I install?": VS Code, Codex, Claude Desktop and the terminal CLI, what each gives you, how to install it, the shared sign-in and platform support. The rest describes the command line, the library API, the project MCP client, the shared project-tool registry and the release procedure in the present tense, without version numbers.
• Deleted: the integration roadmap, the Phase-1 and Phase-2 verification records, the Phase-2 release record and the conversational-MCP redirect stub. The guides are version-free.
• scripts/check-docs.cjs runs in release:check: links in the README, guides and ADRs resolve, named npm scripts exist, the README and guides name no versions beyond the two SDK minimums sync requires.

npm: @dev-mainsequence/devtools@0.3.13, integrity sha512-alIVkOx+unsoN37hAOavB1R5h7+/YiC506Y+WfSbe/RVCoSi11rCPW2buPKyv/MJ1xVkPEkbhlRq8ZsPQYgpOg==.

Devtools 0.3.12

Shared project-tool registry (ADR 0004). Both host plugins present every saved project MCP connection's tools as first-class host tools named ms_<tool>_<hash>; this package now owns that registry: projectToolName, projectToolDefinition(s), projectToolResult, readProjectToolCatalog, createProjectToolCatalog (the shared on-disk project-tool-catalog.json), and the mcp-catalog and mcp-tool-call actions with the ms-devtools mcp-catalog [--refresh] command line.

Project MCP requests get their own budget (projectRequestTimeoutMs, default 120 s) and a tools/call honours the tool's advertised _meta["mainsequence.ai/timeout-seconds/v1"] up to 300 s. Error messages name the endpoint, the request and the status, tell a timeout from a connection failure, and keep a JSON-RPC error's own message.

npm: @dev-mainsequence/devtools@0.3.12, integrity sha512-tV4k57P5iaH5dQuuqN1uvxaneZ9G/Hok0fmBRCXZlJSLMUOcDLRFjfRN/R0q8gtuMUlf1jm3Kg0hxjfMAf16Lg==.

Devtools 0.3.2

Devtools 0.3.2 provides shared, typed discovery for host integrations: bounded environment pagination, account-bound reads, read-only saved MCP listings and optional repository-name enrichment.

The built-in session validates the account actually used for requests and safe retries. Existing unscoped callers retain their previous behavior. Claude is unchanged.

Validation: 124 tests plus typecheck and standalone package checks; Linux and macOS CI passed. Published through npm trusted publishing with provenance.

The attached npm archive is the exact published artifact. Its SHA-512 integrity is:

sha512-NIIMG67fgezXdc+6yZrlcLZDEkI+5yYcOvmwE37b1EuRtj2GgmgKy/lRttj7YSG/YKOfGcia/ilmwNQMD0NL1Q==

MainSequence Developer Tools 0.2.7

Fixes MCP connections for FastAPI releases whose detail response omits the discovery-only name field.

• Use the release UID as the connection identity; retain name only as an optional display label.
• Allow add, tool listing, and calls with nameless release details and saved connections, without an extra discovery request.
• Preserve release UID, endpoint, resource metadata, credential-target, and access validation.

Validation: all 110 tests and package checks passed. The packed release discovered and added the deployed CRM MCP, then loaded the saved connection in a fresh client and listed 70 tools.

Resolves issue #6.