Skip to content

fix(agent): find the terminal files when the service runs from the build - #28

Merged
RedStar071 merged 1 commit into
mainfrom
fix/controller-terminal-paths
Nov 8, 2026
Merged

RedStar071 merged 1 commit into
mainfrom
fix/controller-terminal-paths

Conversation

@RedStar071

@RedStar071 RedStar071 commented Nov 8, 2026 •

Copy link
Copy Markdown
Member

🔗 Linked issue

No linked issue.

❓ Type of change

  • 📖 Documentation
  • 🐞 Bug fix
  • 👌 Enhancement
  • ✨ New feature
  • 🧹 Chore
  • ⚠️ Breaking change

📚 Description

With server.agent_sessions: true, a controller started from the build (dist/cli.mjs) exited at startup and systemd restarted it in a loop. The build bundles the controller into dist/_chunks, one directory deeper than src, so three paths written for the source layout missed: the terminal helper (dist/_chunks/terminal-helper.mjs instead of dist/terminal-helper.mjs), worktree-claim.sh (packages/wolfstar-agent-kit/ instead of the repository root), and the dashboard build.

  • controllerTerminalPaths lists both layouts for each path and takes the first one that exists. The source layout resolves as before.
  • desktop-session-claim.ts gets the same extra candidate for the claim script.

🤖 AI disclosure: Wolfstar Agent Kit modified this description. AI open source policy.


Read this PR faster

The build bundles the controller into dist/_chunks, one directory deeper
than src. The terminal helper, the claim script, and the dashboard build
were resolved for the source layout only, so the service exited at startup
with agent_sessions enabled. Each path now lists both layouts.
@coldtea-pr-lens

coldtea-pr-lens Bot commented Nov 8, 2026 •

Copy link
Copy Markdown

Architecture

Walkthrough of Resolve controller terminal and session claim paths in bundled builds, in three steps

Read this PR faster


Data flow

No data-flow sequence changed in this PR.


Tip

The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change

🪧 More tips
  • Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
  • Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
  • Click the link under each diagram to open it on a canvas you can zoom, pan and step through
  • Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
  • The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
  • Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture… row. Drawing still runs as before
  • Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn
  • Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
  • After a push, tick Redraw to draw the latest commit
  • Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion
  • Set github.description: false in .github/pr-lens.yml to stop PR Lens adding buttons to your PR descriptions

Thanks for using PR Lens! It's free for OSS. If it helped, a star helps other teams find it.  Star PR Lens on GitHub

@cloudflare-workers-and-pages

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Failed ❌

View logs ↗
714901f 2026-11-08T15:48:34.376Z View logs ↗

@RedStar071
RedStar071 merged commit aac6f07 into main Nov 8, 2026
10 of 11 checks passed
@RedStar071
RedStar071 deleted the fix/controller-terminal-paths branch November 8, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant