Repository navigation
feat(pi): open the Braid panel on a single node - #54
Merged
Merged
Conversation
Add `/braid <jobId> <nodeId|executionId>` to show one node's latest or exact invocation in the live panel: status, model, loop iteration, elapsed time, token and context usage, tool calls, workspace, and the full output or error. Backspace returns to the graph, and Tab completes job handles and then node IDs, including IDs that contain spaces. Focused braid_status results share the renderer and now show the same details, rendered at the read's observation time so a saved result does not keep counting. Co-Authored-By: Claude Opus 5.5 <[email protected]>
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
Epsirom
added a commit
that referenced
this pull request
Oct 9, 2026
## Change Prepare the coordinated Braid 0.3.2 release with Pi editor progress (#52), the bounded parallel review command (#53), and focused node panels plus safe exact-ID completion (#54). Update all three package versions, the integrations' exact core dependencies, and the workspace lockfile. Publish dated changelog entries with implementing PR links and author credits, retain the current host compatibility baselines, and update the roadmap. powerfooI is an existing contributor via #24; this release has no first-time human contributors. ## Validation - `npm ci` and `npm run verify`: 227 core, 113 Pi, and 35 DSH tests (375 total), all type checks, offline examples, and package-consumer smoke checks. - `RELEASE_TAG=v0.3.2 node scripts/check-release.mjs`. - `npm pack --dry-run` inspected for all three packages. - `git diff --check`. - [x] Relevant tests and type checks pass. - [x] User-facing docs and changelog are updated where needed. - [x] No breaking changes or migration required from 0.3.1. - [x] Release notes link feature/fix PRs, credit authors, and verify contributor history. Publish the matching GitHub release only after required CI passes; the existing trusted-publishing workflow releases core, Pi, and DSH to npm.
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 changes
/braidaccepts an optional node or execution after the job ID, opening the live panel focused on that one node:The focused view refreshes live and shows status, model, loop iteration, elapsed time, token usage, context size, tool calls, workspace, and the full output or error. Backspace returns to the whole graph; switching jobs also returns to it. Tab completes job handles, then that job's node IDs.
Why
Until now, the only way to see one node's details in Pi was to ask the model to call
braid_status. The panel showed only the whole graph. This gives people a direct, live view of a single node.Details
/braid <jobId>.renderNodeResultis shared with focusedbraid_statusresults, which now show the same detail lines. A running node's elapsed time is computed at the read's observation time, so a saved tool result doesn't keep counting.Verification
npm run check,npm test(227 pass)npm run check:pi,npm run test:pi(96 pass), including new tests for:This is independent of #52 and applies cleanly on either side of it.
🤖 Generated with Claude Code
Maintainer review fixes
npm run verifypassed (227 core, 98 Pi, 35 DSH tests), including type checks, offline examples, and package-consumer smoke checks. Focused panel/render checks passed (23 tests);git diff --checkpassed.