feat(dev): supervise every runtime in project dev - #2041
Open
tejaskash wants to merge 3 commits into
Open
Conversation
tejaskash
had a problem deploying
to
e2e-testing
August 19, 2026 19:12 — with
GitHub Actions
Failure
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 19, 2026 19:51
1864da4 to
c539836
Compare
Contributor
Author
|
Both addressed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## refactor #2041 +/- ##
============================================
+ Coverage 97.22% 97.24% +0.02%
============================================
Files 391 392 +1
Lines 23677 23894 +217
============================================
+ Hits 23019 23236 +217
Misses 658 658 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 20, 2026 16:09
c539836 to
6080aa0
Compare
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 20, 2026 16:18
6080aa0 to
82af18a
Compare
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 21, 2026 15:23
82af18a to
2db7743
Compare
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 21, 2026 16:14
2db7743 to
136a454
Compare
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 21, 2026 17:51
136a454 to
35775f9
Compare
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 21, 2026 18:55
35775f9 to
a9f11fe
Compare
project dev without --agent now runs all of the project's runtimes at once: a DevSupervisor owns per-agent lifecycle (sequential port resolution — a concurrent race would put two agents on one port), merges every runner's output into one agent-attributed stream ([name] prefixes; an agent field in NDJSON), and keeps the session alive when one agent crashes. Selecting a single runtime (--agent, or a one-runtime project) keeps the direct path where a crash still fails the command.
…setup A child that stays alive without ever binding its port previously blocked every later runtime (starts are sequential) until interrupted; readiness now gives up after 120s and fails that start. Setup failures before the pump exists (port resolution, environment) now remove their parent-abort listener like every other exit path, so Inspector retries of a failing agent cannot accumulate listeners.
tejaskash
force-pushed
the
feat/dev-supervisor
branch
from
August 21, 2026 21:32
a9f11fe to
4ad026c
Compare
The #1980 rebase carried a single-runtime host check (runtime.build) into the multi-agent dev handler, where the variable is the runtimes array. Bind all interfaces when any selected runtime runs in a container.
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.
Review after #1980
What this does
agentcore project devwithout--agentruns all of the project's runtimes at once. Each agent's output is attributed ([orders] ...in the terminal, anagentfield in NDJSON); one agent crashing reports its failure and leaves the others running; Ctrl-C tears the whole set down. Selecting one runtime (--agent, or a single-runtime project) keeps the direct path where a crash fails the command — scripts and CI rely on that exit code.How
DevSupervisor(core/dev/supervisor.ts) owns per-agent lifecycle: an abort scope per agent chained to the command signal, a per-agent state machine (idle/starting/running/failed) with start dedup, TCP readiness probing, and one merged attributed event stream. It's also what the Inspector UI slice (next PR) drives via its start-on-demand API. Ports resolve sequentially — concurrent resolution raced two HTTP agents onto the same port.Verification
agentcore.json, ranproject dev— both agents started on distinct ports with attributed logs, both answered real Bedrock invocations, and the trace directory holds spans for both service names (per-runtimeOTEL_SERVICE_NAMEverified end to end). SIGTERM exits 130.tsc/lint/format clean.