You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4b8b7be
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,12 @@
1
1
# Changelog
2
2
3
+
## 2.0.1
4
+
5
+
- Name MCP tools `intent_runtime_prepare`, `intent_runtime_accept`, `intent_runtime_cancel` (host) and `intent_runtime_parse` (executor) by default across embedded adapters, stdio, HTTP and Codex. Optional `toolPrefix` adds to the complete name; multiple instances still share one tool set. Update the Codex Skill, diagnostics, examples and documentation. Tool parameters and result schemas are unchanged.
6
+
- MCP callers using the 2.0.0 tool names must update their explicit calls; old tool-name aliases are not registered. Codex users should rerun `setup` with their existing configuration and registration name to refresh the managed Skill, then reload the client.
7
+
- Clarify how to add tools to an existing MCP server, preserve other tools and reject duplicate names. Complete the user documentation and response examples, preserve existing MCP section links, and validate both LF and CRLF documentation.
8
+
- Fix installed-entry release verification and allow for npm registry processing before verifying the published package and default installation.
9
+
3
10
## 2.0.0
4
11
5
12
- Rewrite the recognition core. The complete intent tree lives in `effective`; `turn.intentIds` and `changes` associate the current turn with that tree. Results and baselines use format version `2.0-draft.6`.
Connect the client to `http://127.0.0.1:3001/mcp`. Change the listener with `--host`, `--port`, and `--path`. Set `--public-origin https://mcp.example.com` when using a public domain or HTTPS proxy; wildcard listeners require an explicit public origin. See the [remote deployment example](https://devcodex-labs.github.io/intent-runtime/integrations/mcp.html#远程地址与-https-代理). HTTP supports the stateful MCP 2025-06-18 and 2025-11-25 protocols; stdio also supports 2026-07-28. Authentication and HTTPS belong to your deployment layer.
145
145
146
-
Ask your client to use the intent tools to identify the goal and prohibition in the example request. It should use `intent_prepare`, produce a candidate with its current model, and submit it through `intent_accept` in the same session. The tools do not automatically process every chat message. See [MCP client configuration and usage](https://devcodex-labs.github.io/intent-runtime/integrations/mcp.html).
146
+
Host mode exposes `intent_runtime_prepare`, `intent_runtime_accept`, and `intent_runtime_cancel` by default; executor mode exposes `intent_runtime_parse`. Embedded adapters use the same names, so ordinary integrations need no `toolPrefix`. Multiple instances share the tool set and use `instance` for selection. An optional extra prefix such as `orders_` produces `orders_intent_runtime_prepare`; merged tool names must still be unique.
147
+
148
+
Ask your client to use the intent tools to identify the goal and prohibition in the example request. It should use `intent_runtime_prepare`, produce a candidate with its current model, and submit it through `intent_runtime_accept` in the same session. The tools do not automatically process every chat message. See [MCP client configuration and usage](https://devcodex-labs.github.io/intent-runtime/integrations/mcp.html).
147
149
148
150
For an existing MCP server, start with the [four integration changes](https://devcodex-labs.github.io/intent-runtime/integrations/mcp-sdk.html); keep your existing transport, resources, prompts, and tool handlers.
Copy file name to clipboardExpand all lines: RELEASING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,11 +29,11 @@ GitHub Pages must use GitHub Actions as its source. The docs workflow deploys to
29
29
30
30
1. Update the version in both `package.json` and the root package entries in `package-lock.json`. Add a matching `## 2.x.y` section to `CHANGELOG.md`; its body becomes the GitHub Release notes. Do not change result `schemaVersion` just because the npm package version changes.
31
31
2. Review the current public API, upgrade instructions and examples. Run `npm ci`, `npm run typecheck`, `npm run lint`, `npm test`, `npm run test:release`, and `npm run check:package`. For documentation, run `npm --prefix website ci`, `npm run docs:check`, and `npm run docs:build`.
32
-
3. Commit and push the reviewed source. Tag that exact commit, then push the tag. For version 2.0.0:
32
+
3. Commit and push the reviewed source. Tag that exact commit, then push the tag. For version 2.0.1:
33
33
34
34
```bash
35
-
git tag v2.0.0
36
-
git push origin v2.0.0
35
+
git tag v2.0.1
36
+
git push origin v2.0.1
37
37
```
38
38
39
39
The version guard rejects prereleases, mismatching tags, and inconsistent lock metadata. Tags outside the supported stable V2 line do not publish.
0 commit comments