• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

lsm / neokai / 25951491329 / 8
81%
dev: 81%

Build:
DEFAULT BRANCH: dev
Ran 16 May 2026 03:24AM UTC
Files 30
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

16 May 2026 03:21AM UTC coverage: 83.918%. Remained the same
25951491329.8

push

github

web-flow
fix: register node-agent MCP tools in eager-spawn workflow sessions (#1917)

* fix: register node-agent MCP tools in eager-spawn workflow sessions (#1913)

Eager-spawn sessions have IDs ending in `:agent:<name>` rather than
`:exec:<id>`, so `isWorkflowSubSession` was always false for them.
The self-heal block in QueryRunner.start() never fired, leaving
mcp__node-agent__* tools unregistered when the Coding agent ran.

Two fixes:
1. Extend `isWorkflowSubSession` to match `:agent:` session IDs so
   self-heal and structured logging work for eager-spawn sessions.
2. Add `restartQuery({ force: true })` so `reinjectNodeAgentMcpServer`
   can flush the updated server config into the SDK even when the
   eager session's initial empty query has already exited (idle state).

* fix(space): node-agent MCP tools not visible in eager-spawn Coder sessions

Two root causes:

1. `attachSpaceToolsToMemberSession` (space-runtime-service.ts) only skipped
   exec sub-sessions (`:exec:`) but not eager-spawn sessions (`:agent:`). This
   caused a generic `space-agent-tools` server to be hot-swapped onto the
   eager-spawn session via `setMcpServers`, disrupting the node-agent in-process
   MCP server connection and overwriting its specialised context.

2. `QueryOptionsBuilder.build()` set `allowedTools = CODER_TOOLS` (built-in
   tools only) for workflow node-agent sub-sessions without auto-allowing the
   MCP server wildcards. Unlike `space_chat`, which explicitly adds
   `<server>__*` wildcards, Coder sessions had no access to node-agent tools
   even when the server was correctly attached.

* fix(space): force-load workflow MCP tools so agents can see them

Root cause of node-agent tools being unavailable: the Claude Code CLI
defers ALL MCP tools behind tool search by default. Its deferral check
is `isDeferredTool(t) => t.alwaysLoad ? false : t.isMcp ? true : ...` —
every MCP tool is deferred unless explicitly marked alwaysLoad.

A GLM-backed Coder node-agent session's S... (continued)

2296 of 2736 relevant lines covered (83.92%)

39.67 hits per line

Source Files on job daemon-0-shared - 25951491329.8
  • Tree
  • List 30
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 25951491329
  • 7b143f48 on github
  • Prev Job for on dev (#25935710436.1)
  • Next Job for on dev (#25952202576.16)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc