threadroot 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,19 @@ All notable changes to Threadroot will be documented here.
4
4
 
5
5
  Threadroot follows semantic versioning after the first public release. While `0.x`, minor versions may include breaking changes as the harness format settles.
6
6
 
7
+ ## 0.1.3 - Verified Codex MCP setup
8
+
9
+ ### Added
10
+
11
+ - `threadroot mcp check` to verify Codex MCP config, launch the stdio server, complete a JSON-RPC initialize handshake, and assert required Threadroot tools are available.
12
+ - MCP server initialization instructions that tell agents how to use `context`, `doctor`, skills, tools, and durable memory.
13
+ - Doctor checks for configured-but-broken Codex MCP.
14
+
15
+ ### Changed
16
+
17
+ - `bootstrap --mcp` and `setup --global --mcp` now write a local-aware MCP command. Package-bin symlinks and local dev runs resolve to `node /path/to/dist/index.js mcp`, with `threadroot mcp` as the fallback.
18
+ - Package smoke now verifies MCP from the packed tarball.
19
+
7
20
  ## 0.1.2 - One-command bootstrap and session start
8
21
 
9
22
  ### Added
package/README.md CHANGED
@@ -38,7 +38,9 @@ node dist/index.js --help
38
38
 
39
39
  ```bash
40
40
  tr bootstrap --yes # one-time machine setup + local-only .threadroot/
41
+ tr bootstrap --yes --mcp # also configure and verify global Codex MCP
41
42
  tr start "write tests" # doctor, status, relevant context, and command map
43
+ tr mcp check # verify Codex MCP config and server handshake
42
44
  tr expose codex # optional: write a thin project skill shim for Codex
43
45
  ```
44
46
 
@@ -71,6 +73,7 @@ tr connections list | check
71
73
  tr connections add <name> --provider <p> --command <cmd>
72
74
  tr packs list | inspect <pack> | validate <pack> | install <pack>
73
75
  tr mcp # run the local MCP server (stdio)
76
+ tr mcp check # verify Codex MCP config and required tools
74
77
  tr mcp setup [--write] # wire MCP into agents
75
78
  ```
76
79
 
@@ -100,14 +103,16 @@ vendor file is preserved; Threadroot only owns the block it marks as generated.
100
103
  The simple path is:
101
104
 
102
105
  ```bash
103
- tr bootstrap --yes
106
+ tr bootstrap --yes --mcp
104
107
  tr start "current task"
105
108
  ```
106
109
 
107
110
  Without `--yes`, `tr bootstrap` prints a dry-run plan. With `--yes`, it installs global
108
111
  agent bootstrap skills, initializes `.threadroot/` if needed, runs doctor, and prints
109
- task context. It does not write provider-specific project files unless you pass
110
- `--expose`.
112
+ task context. With `--mcp`, it also writes Codex MCP config using the current CLI entry
113
+ (`node /path/dist/index.js mcp` when Threadroot can resolve the package path, or
114
+ `threadroot mcp` as a fallback) and verifies the stdio server handshake. It does not write
115
+ provider-specific project files unless you pass `--expose`.
111
116
 
112
117
  Global setup installs a tiny `threadroot` skill into supported agent user-skill
113
118
  directories so agents know to call `threadroot bootstrap --yes` when setup is missing
@@ -237,6 +242,7 @@ Threadroot runs a local MCP server over stdio that exposes the harness to agents
237
242
 
238
243
  ```bash
239
244
  tr mcp
245
+ tr mcp check # verify Codex global MCP config and required tools
240
246
  tr mcp setup # print config snippets and a pasteable agent bootstrap prompt
241
247
  tr mcp setup --write # opt-in: write project-local MCP config for supported agents
242
248
  ```
@@ -249,6 +255,10 @@ Tools: `context`, `skills_list`, `skills_get`, `tools_list`, `tools_check`, `too
249
255
  check availability, run `threadroot bootstrap --yes`, run `threadroot start "<task>"`,
250
256
  and ask before writing project-local MCP config.
251
257
 
258
+ After changing Codex MCP config, reload VS Code/Codex or start a new Codex session. `tr mcp
259
+ check` proves the server works from the terminal; the agent surface still has to load its
260
+ MCP configuration.
261
+
252
262
  ## Profiles
253
263
 
254
264
  `nextjs`, `vite-react`, `fastapi`, `python-cli`, `node-cli`, `dbt`, `empty`.
@@ -287,7 +297,8 @@ THREADROOT_ROOT="$(pwd)"
287
297
  TMP_REPO="$(mktemp -d /tmp/threadroot-smoke.XXXXXX)"
288
298
  rsync -a --exclude .git --exclude node_modules --exclude dist ./ "$TMP_REPO/"
289
299
  cd "$TMP_REPO"
290
- HOME="$TMP_REPO/home" node "$THREADROOT_ROOT/dist/index.js" bootstrap --yes --agent codex --no-import
300
+ HOME="$TMP_REPO/home" node "$THREADROOT_ROOT/dist/index.js" bootstrap --yes --agent codex --mcp --no-import
301
+ HOME="$TMP_REPO/home" node "$THREADROOT_ROOT/dist/index.js" mcp check
291
302
  HOME="$TMP_REPO/home" node "$THREADROOT_ROOT/dist/index.js" start "write tests"
292
303
  node "$THREADROOT_ROOT/dist/index.js" expose codex
293
304
  node "$THREADROOT_ROOT/dist/index.js" status