active Automatic scheduler, orchestrator, forwarder, and sanity auto-heal actions are allowed.
idle Kick off a Jules enhancement round once the tracked repo is ready.
Request: not requested yet
Summary: Request an enhancement round for Stbmap/dev-manager when you want the scheduler to look for follow-up improvements.
Open issues / PRs / active enhancer sessions: 0 / 0 / 0
Welcome to the dev-manager orchestration cockpit. It auto-refreshes, remembers your place, and keeps the state visible without manual reloads.
Listens to the manager event stream while that tab is open, without reloading the whole page.
The background Jules sync, scheduler, watcher, forwarder, and orchestrator loops are started in cmd/dev-manager/main.go and read their cadence from DB-backed runtime settings.
GitHub intake watches the tracked repository and imports open issues and pull requests into the queue before the scheduler starts sessions.
Clarification threads are exposed through the JSON API so Codex can read Jules questions and answer them directly without using the UI.
1
1
5
4
10
0
8
3
Repo: Stbmap/dev-manager
Status: ok: scanned 1 repo(s), 267 items total (Stbmap/dev-manager=267)
Status: ok: synced 155 Jules session(s) (0 imported, 1 updated)
Status: waiting for the first webhook delivery
Status: ok: no sanity issues detected
Status: error: drift detected: risky: repo Stbmap/stbmap workspace /home/stbmap/stbmap has 2 uncommitted change(s) and no active sessions
Status: waiting: reused 1 canonical self-improvement issue(s), policy denied 2 candidate(s)
Status: ok: no expired memory entries (retention=180d)
Candidates: 1
Quietest / Noisiest: 1m (14216493617128889234) / 1m (14216493617128889234)
Total: 16
Split / Blocked / Launchable: 1 / 0 / 15
Total: 1
Proposed / Approved / Applied: 1 / 0 / 0
Total: 26
Active / Blocked / Failed / Completed: 0 / 15 / 0 / 1
Total: 51
Blocked / Allowed / Failed: 35 / 13 / 0
Main-first drift: 0
escalating Why the manager is waiting, launching, escalating, or refusing work.
Next: resolve the operator-owned items before opening fresh work
This is the manager's self-check trail. Auto-heal only repairs safe queue drift and uses long thresholds before it pauses or requeues expired work.
| Time | Event | Summary |
|---|---|---|
| 3m ago | sanity_ok | ok: no sanity issues detected |
| 5m ago | sanity_ok | ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists |
| 5m ago | sanity_auto_heal | Repaired 2 item(s). |
| 7m ago | sanity_ok | ok: no sanity issues detected |
| 9m ago | sanity_ok | ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists |
| 9m ago | sanity_auto_heal | Repaired 2 item(s). |
| 13m ago | sanity_ok | ok: no sanity issues detected |
| 15m ago | sanity_ok | ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists |
Sessions tracked by dev-manager in the local database. These are the normalized manager-owned rows the scheduler, watcher, and orchestrator actively manage end to end.
Pause keeps a session visible and held by the manager. Kill stops local management, requeues the linked GitHub item when possible, and may still leave the remote Jules session visible upstream because Jules does not expose a hard delete.
Click any session row to open its details here. The selection is remembered across auto-refreshes.
| Trace / ID / Item | State | Details | Actions |
|---|---|---|---|
|
Stbmap/dev-manager Issue #256 14216493617128889234 |
running |
Poor Prompting. Manager API Links MUST be in initial message
Created: 26m ago
Last Active: 1m ago
Lease Remaining: in 2d 23h
|
Remote sessions pulled from the Jules API for any configured Jules accounts. This is the raw upstream mirror. The manager-owned queue lives in Local Sessions and uses normalized internal states for automation.
Loading remote Jules sessions...
First-class attention queue for Jules sessions that need a response, recovery nudge, or operator decision. This view listens to the manager event stream and refreshes only when something changes.
Loading sessions that need attention...
Single place for human decisions. This queue collects escalations, provider failures, blocked messages, and other items the manager cannot safely finish on its own.
Loading operator inbox items...
Paste a Jules web suggestion here when the upstream surface does not expose a clean API. Suggestions are tracked advisory work first, then they can be promoted to a GitHub issue, turned into a directive inbox item, or ignored as noise.
Loading suggestions...
Durable memory rows capture incidents, prompt changes, self-improvement notes, split plans, and other lessons the manager should remember across sessions. Rows now carry an expiry and a retention sweep prunes stale memory so prompts stay current.
Loading memory entries...
Goal plans turn broad work into ordered, reusable slices. Each row records the target, dependency graph, and the split/blocked/launchable disposition the manager derived before a worker starts.
| Time | Target | Goal | Disposition | Graph |
|---|---|---|---|---|
| 26m ago |
Stbmap/dev-manager goal-plan:Stbmap/dev-manager#256 |
Ensure every new Jules session receives complete manager API instructions in the first `CreateSession` prompt, using the configured manager API base URL and explicit endpoint guidance, so reviewer and task sessions can ask questions, report blockers, share progress, and finish work even if the later notify follow-up is never delivered. Plan: Poor Prompting. Manager API Links MUST be in initial message This is a focused runner prompt-path fix under the fat policy: the runtime prompt change, manager-URL/settings reuse, and prompt assertions belong in one slice, and splitting them would create artificial dependencies between implementation and verification. |
launchable |
deps=0 history=0 children=0 ordered=1 |
| 5h 37m ago |
Stbmap/dev-manager goal-plan:Stbmap/dev-manager#267 |
Verify on merged main that the split-plan apply flow now treats parent-comment failures as warnings rather than fatal errors, confirm the regression test passes, and close PR #267 as a redundant verification-only follow-up. Plan: Verify issue 251 fix in main This is a fast-lane verification and closeout item, not a multi-slice implementation. Under the current fat split policy, there is no safe or useful child breakdown because the work is just to confirm the merged mainline fix and close the redundant PR. |
launchable |
deps=0 history=0 children=0 ordered=1 |
| 6h 26m ago |
Stbmap/dev-manager goal-plan:Stbmap/dev-manager#264 |
Change Apply so a parent-comment posting failure is stored in result.Warnings rather than appended to failures, allowing the core apply flow and MarkSplitPlanApplied transition to complete; add regression coverage for that path. Plan: Fix PR #251 comment error behavior This is a tight behavioral fix in one Apply code path plus a focused regression test. Under the current fat split policy, separating it would add artificial coordination without creating independently useful slices. |
launchable |
deps=0 history=0 children=0 ordered=1 |
| 6h 40m ago |
Stbmap/dev-manager goal-plan:Stbmap/dev-manager#263 |
Update split-plan apply so that when child issue creation succeeds, a failure to post the parent comment does not fail the overall apply operation. The comment problem should be surfaced as a warning, while the parent closeout and persisted/returned applied state remain consistent with the success path. Plan: Fix PR #251 comment error behavior This PR is a narrow split-plan apply closeout repair, not a broad feature slice. Recent goal-plan memory for #255/#258/#261 already converged on keeping this as one cohesive apply-success fix, and the current fat policy plus PR fast-lane behavior both argue against splitting it further. |
launchable |
deps=0 history=0 children=0 ordered=1 |
| 6h 45m ago |
Stbmap/dev-manager goal-plan:Stbmap/dev-manager#261 |
Make approved split-plan apply end in one coherent outcome: child issue creation, parent comment/close behavior, and the stored and returned split-plan state should agree, while non-fatal closeout failures remain warnings instead of derailing an otherwise successful apply. Plan: Fixes #253 This is a single split-plan apply/closeout fix concentrated in one workflow. The likely code and tests all sit on the same state-machine surface in `internal/splitplanops` plus its persistence and command-facing checks, so splitting it would create overlapping child work with little independent value under the current fat policy. |
launchable |
deps=0 history=0 children=0 ordered=1 |
Split plans are the operator-approved workflow that turns a broad item into linked child GitHub issues. Approve a proposal, apply it to create the child issues, or request a regeneration if the slice set needs another pass.
| Time | Target | State | Parent | Children | Summary | Actions |
|---|---|---|---|---|---|---|
| 10h 53m ago |
Stbmap/dev-manager Stbmap/dev-manager#244 issue_split:Stbmap/dev-manager#244 |
proposed | needs_split |
|
Prove from merged main that the manager can survive a supervised multi-cycle workload window, capture incident-grade evidence, and stop deterministically when drift, duplicate work, stale leases, repeated recoveries, or manual intervention appear. The issue is too broad for one fresh worker because it mixes three separable concerns while repo guidance still says keep the manager supervised, not unattended: a long-running driver, durable soak evidence, and deterministic stop conditions. |
|
Durable handoff rows record role transitions such as planner to implementer, implementer to reviewer, and orchestrator escalations. This is the visible multi-agent ownership trail.
Loading handoffs...
Durable role-owned tasks are derived from handoffs and tracked separately from raw GitHub items. They keep planner, implementer, reviewer, repairer, and reconciler work visible across retries and scheduler restarts.
By status:
By role/state:
| Task | Role / Status | Target | Chain | Updated |
|---|---|---|---|---|
|
agent-task:stbmap/dev-manager:github_item:Stbmap/dev-manager#267:reconciler handoff:pr_closeout:reviewer->reconciler:17318204966995998097:Stbmap/dev-manager#267 |
reconciler ready |
Stbmap/dev-manager github_item Stbmap/dev-manager#267 |
chain: handoff:pr_closeout:reviewer->reconciler:17318204966995998097:Stbmap/dev-manager#267
origin: handoff:pr_closeout:reviewer->reconciler:17318204966995998097:Stbmap/dev-manager#267
session: 17318204966995998097
|
5h 15m ago |
|
agent-task:stbmap/dev-manager:github_item:Stbmap/dev-manager#264:reconciler handoff:pr_merge:reviewer->reconciler:12288488647733156000:Stbmap/dev-manager#264 |
reconciler ready |
Stbmap/dev-manager github_item Stbmap/dev-manager#264 |
chain: handoff:pr_merge:reviewer->reconciler:12288488647733156000:Stbmap/dev-manager#264
origin: handoff:pr_merge:reviewer->reconciler:12288488647733156000:Stbmap/dev-manager#264
session: 12288488647733156000
|
5h 32m ago |
|
agent-task:stbmap/dev-manager:github_item:Stbmap/dev-manager#261:reconciler handoff:pr_merge:reviewer->reconciler:11793685936959923904:Stbmap/dev-manager#261 |
reconciler ready |
Stbmap/dev-manager github_item Stbmap/dev-manager#261 |
chain: handoff:pr_merge:reviewer->reconciler:11793685936959923904:Stbmap/dev-manager#261
origin: handoff:pr_merge:reviewer->reconciler:11793685936959923904:Stbmap/dev-manager#261
session: 11793685936959923904
|
5h 59m ago |
|
agent-task:stbmap/dev-manager:github_item:Stbmap/dev-manager#263:reconciler handoff:pr_merge:reviewer->reconciler:4466040978523295785:Stbmap/dev-manager#263 |
reconciler ready |
Stbmap/dev-manager github_item Stbmap/dev-manager#263 |
chain: handoff:pr_merge:reviewer->reconciler:4466040978523295785:Stbmap/dev-manager#263
origin: handoff:pr_merge:reviewer->reconciler:4466040978523295785:Stbmap/dev-manager#263
session: 4466040978523295785
|
6h 25m ago |
|
agent-task:stbmap/dev-manager:github_item:Stbmap/dev-manager#255:reconciler handoff:pr_merge:reviewer->reconciler:5533709358743498917:Stbmap/dev-manager#255 |
reconciler ready |
Stbmap/dev-manager github_item Stbmap/dev-manager#255 |
chain: handoff:pr_merge:reviewer->reconciler:5533709358743498917:Stbmap/dev-manager#255
origin: handoff:pr_merge:reviewer->reconciler:5533709358743498917:Stbmap/dev-manager#255
session: 5533709358743498917
|
7h 8m ago |
Imported work items from the tracked repository. These feed the scheduler.
Closed items are hidden by default.
464 closed item(s) are hidden. Use ?show_closed=1 to reveal them.
| Repo / Issue | Title | State | Updated | Link |
|---|---|---|---|---|
|
Stbmap/dev-manager Issue #245 |
Add replayable incident and recovery drills | deferred | 1m ago | Open |
|
Stbmap/dev-manager Issue #244 |
Add a long-running soak harness for unattended autonomy | blocked | 1m ago | Open |
|
Stbmap/dev-manager Issue #243 |
Phase 5: Production Hardening and Unattended Autonomy | blocked | 1m ago | Open |
|
Stbmap/dev-manager Issue #256 |
Poor Prompting. Manager API Links MUST be in initial message | in-progress | 1m ago | Open |
|
Stbmap/dev-manager Issue #257 |
Jules recieves multiple consecutive messages | ready | 1m ago | Open |
|
Stbmap/dev-manager Issue #259 |
Local agent should help when Jules clearly can't resolve issues, reviews etc. | ready | 1m ago | Open |
|
Stbmap/dev-manager Issue #260 |
feature: dev-manager scheduled tasks | ready | 1m ago | Open |
|
Stbmap/dev-manager Issue #262 |
feature: max dev cycle configuration knop | ready | 1m ago | Open |
|
Stbmap/dev-manager Issue #247 |
Tighten truth reconciliation for workspace_dirty_orphan:Stbmap/stbmap | deferred | 1m ago | Open |
|
owner/repo Issue #1 |
Test trace item | deferred | 25m ago | Open |
Imported pull requests from the tracked repository.
Closed items are hidden by default.
464 closed item(s) are hidden. Use ?show_closed=1 to reveal them.
No imported pull requests found.
Manager-level secrets loaded at runtime.
Map each GitHub repository to a local checkout so intake can watch it and Codex can answer from the correct codebase. This is the seam that makes multi-repo orchestration work.
Every repository policy save records a durable snapshot. Use restore to roll a repo back to a known-good policy version.
| Repo | Version | Status | Summary | Description | Updated | Actions |
|---|---|---|---|---|---|---|
| Stbmap/dev-manager | #1 | active | - | seeded from repo_configs | 1d ago | |
| Stbmap/stbmap | #1 | active | - | seeded from repo_configs | 1d ago |
These DB-backed settings control the automatic loops and decision thresholds without code changes or restarts. Use Go duration strings like 30s, 5m, or 2h. The issue split policy lives here too, so you can keep Jules on fat issues unless you explicitly flip it to split.
Budget thresholds live in runtime settings for global defaults and in each repository mapping for overrides. They control how much Jules and provider burn the manager will tolerate before it slows fresh launches.
| Scope | Policy | Jules | Codex | Gemini | Status | Blocking |
|---|---|---|---|---|---|---|
| global | global defaults | 30/unbounded | 69/unbounded | 0/unbounded | pass | - |
| Stbmap/dev-manager | inherited | 27/unbounded | 69/unbounded | 0/unbounded | pass | - |
| Stbmap/stbmap | inherited | 3/unbounded | 0/unbounded | 0/unbounded | pass | - |
| Name | Limits (Concurrent/Daily) | Active |
|---|---|---|
|
work_1 ID: 490a1869-f32f-4189-83cc-85b4334e8fcd |
Conc: 10 Daily: 85 Used: 30 Remaining: 55 |
Active Jules API Key: OK Last Used: never |
Roles describe the worker lanes the manager knows about. Updating a role now creates a new prompt version instead of overwriting the previous one.
Prompt versions are the durable source of truth for worker instructions and recovery playbooks. Use scope_type=role and scope_key=implementer/reviewer/orchestrator/responder/admission/completion_review for defaults, scope_type=repo plus a repo full name for repo overrides, or scope_type=playbook to manage named recovery playbooks.
| Scope | Prompt | Version | Status | Description | Content | Updated | Actions |
|---|---|---|---|---|---|---|---|
| playbook: global | awaiting_clarification | #1 | active | Clarification waiting path | {
"key": "awaiting_clarification",
"summary": "Answer or escalate a worker question with the smallest safe step.",
"audience": "responder",
"trigger_states": ["awaiting_clarification"],
"allowed_actions": ["answer", "escalate"],
"message_template": "This session is waiting on clarification. Answer the question directly from the repository docs and current codebase. If the docs do not cover it, say exactly what is missing and the smallest next step. Question: {{.Reason}}.",
"operator_note_template": "Clarification playbook selected for {{.SessionID}}.",
"stop_conditions": ["question answered", "escalated to human review"],
"evidence": ["clarification question present", "confidence available"]
} |
2d 4h ago | |
| playbook: global | blocked_merge | #1 | active | Merge blocker recovery | {
"key": "blocked_merge",
"summary": "Clear merge conflicts or report the exact blocker.",
"audience": "reviewer",
"trigger_states": ["blocked"],
"allowed_actions": ["nudge", "escalate"],
"message_template": "This session is blocked by merge or review state. Resolve the blocker directly now. If this is a merge conflict or behind-base PR, update from the base branch, resolve conflicts, rerun the relevant tests, and push an updated PR. If you still cannot proceed, report the exact blocker and the smallest next step.",
"operator_note_template": "Merge-block playbook selected for {{.ItemLabel}} because {{.Reason}}.",
"stop_conditions": ["blocker resolved", "human review required"],
"evidence": ["merge conflict", "branch protection", "base branch drift", "changes requested"]
} |
2d 4h ago | |
| playbook: global | duplicate_session | #1 | active | Duplicate session recovery | {
"key": "duplicate_session",
"summary": "Prevent duplicate work from spawning more quota burn.",
"audience": "operator",
"trigger_states": ["running", "blocked", "failed"],
"allowed_actions": ["escalate", "release"],
"message_template": "This session appears to duplicate another worker or a recently completed attempt. Stop new changes, keep the current evidence intact, and wait for manager reconciliation before starting more work.",
"operator_note_template": "Duplicate-session playbook selected for {{.ItemLabel}}.",
"stop_conditions": ["duplicate ownership resolved"],
"evidence": ["duplicate launch", "similar branch", "similar PR title", "same item already owned"]
} |
2d 4h ago | |
| playbook: global | failed_session | #1 | active | Failed session recovery | {
"key": "failed_session",
"summary": "Stop active work and surface the smallest clean recovery path.",
"audience": "operator",
"trigger_states": ["failed"],
"allowed_actions": ["escalate", "release"],
"message_template": "This session appears failed or unrecoverable. Stop active work, preserve the current evidence, and report the smallest clean recovery step for {{.ItemLabel}}.",
"operator_note_template": "Failed-session recovery selected for {{.ItemLabel}}.",
"stop_conditions": ["operator intervenes", "session is terminalized"],
"evidence": ["failed state", "stale lease", "missing remote activity"]
} |
2d 4h ago | |
| playbook: global | local_only_session | #1 | active | Local-only session recovery | {
"key": "local_only_session",
"summary": "Handle rows that exist locally without a reachable remote worker.",
"audience": "operator",
"trigger_states": ["blocked", "failed"],
"allowed_actions": ["reassign", "escalate", "release"],
"message_template": "This session is local-only or missing its remote worker. Do not assume the work is progressing remotely. Reconcile ownership, then decide whether to reassign or release {{.ItemLabel}}.",
"operator_note_template": "Local-only recovery selected for {{.ItemLabel}}.",
"stop_conditions": ["remote owner restored", "item requeued", "item released"],
"evidence": ["no remote account", "missing Jules session", "stale lease with no activity"]
} |
2d 4h ago | |
| playbook: global | operator_paused_work | #1 | active | Operator paused work recovery | {
"key": "operator_paused_work",
"summary": "Respect operator pauses and wait for an explicit resume.",
"audience": "implementer",
"trigger_states": ["paused"],
"allowed_actions": ["noop", "escalate"],
"message_template": "This session is paused by operator policy. Do not start new work or self-reassign. Wait for an explicit resume or a fresh operator instruction.",
"operator_note_template": "Operator-paused work selected for {{.ItemLabel}}.",
"stop_conditions": ["operator resumes", "operator changes the pause reason"],
"evidence": ["operator pause reason", "manager pause reason", "sanity pause"]
} |
2d 4h ago | |
| playbook: global | quiet_running_session | #1 | active | Quiet running worker | {
"key": "quiet_running_session",
"summary": "Nudge a running worker that has gone quiet but is still expected to continue.",
"audience": "implementer",
"trigger_states": ["running", "starting"],
"allowed_actions": ["nudge"],
"message_template": "This session has been quiet for {{.QuietFor}}. Continue from the repository docs and current branch. If you are blocked, report the exact blocker and the smallest next step for {{.ItemLabel}}.",
"operator_note_template": "Quiet running worker nudged for {{.ItemLabel}} after {{.QuietFor}}.",
"stop_conditions": ["worker responds", "state changes"],
"evidence": ["quiet_for >= nudge_after", "session still has an active owner"]
} |
1d 2h ago | |
| playbook: global | remote_only_session | #1 | active | Remote-only session recovery | {
"key": "remote_only_session",
"summary": "Handle sessions that exist remotely but are missing locally.",
"audience": "operator",
"trigger_states": ["blocked", "failed"],
"allowed_actions": ["escalate"],
"message_template": "This session appears to exist remotely without a matching local owner. Stop assuming local state is authoritative and wait for manager reconciliation before taking any more action.",
"operator_note_template": "Remote-only recovery selected for {{.SessionID}}.",
"stop_conditions": ["local mirror reconciled"],
"evidence": ["remote session missing local row", "mirror drift", "unmatched remote activity"]
} |
2d 4h ago | |
| playbook: global | stale_lease | #1 | active | Stale lease recovery | {
"key": "stale_lease",
"summary": "Reassign or release work that has exceeded its lease.",
"audience": "operator",
"trigger_states": ["running", "paused", "blocked", "awaiting_clarification"],
"allowed_actions": ["reassign", "escalate", "release"],
"message_template": "This session's lease looks stale. Confirm whether the worker is still actively making progress. If not, reassign or release the smallest work item possible and leave a clear trace for the next worker.",
"operator_note_template": "Stale-lease playbook selected for {{.ItemLabel}} after {{.QuietFor}}.",
"stop_conditions": ["lease refreshed", "work requeued", "operator decides to hold"],
"evidence": ["quiet_for beyond lease threshold", "lease expired", "worker not responding"]
} |
2d 4h ago | |
| role: admission | admission | #1 | active | Decides whether to start a new Jules session. | You are the orchestrator for dev-manager. Your job is to decide whether it is worth starting a fresh Jules session for a queued work item. Be patient. Avoid duplicate sessions. Prefer waiting when an existing worker is already handling the same issue or pull request. If the task is not clearly ready for a new worker, say so. If the task is clearly ready, say so and give the smallest useful reason. |
2d 4h ago | |
| role: another-role | another-role | #1 | active | Desc | Prompt |
1d 2h ago | |
| role: completion_review | completion_review | #1 | active | Reviews terminal Jules sessions and reports whether the result looks trustworthy. | You are the orchestrator for dev-manager. Your job is to assess a Jules session that just reached a terminal state. Use the repository docs, current codebase, and manager context to produce a short completion review. Say whether the completion looks trustworthy and what the smallest next manager step should be. Be concrete, calm, and brief. |
2d 4h ago | |
| role: reconciler | reconciler | #1 | active | Closes out finished work and reconciles the queue. | You are a reconciler. Tidy up, verify the final state, and close the loop. |
12h 49m ago | |
| role: repairer | repairer | #1 | active | Repairs blocked work and clears merge conflicts. | You are a repairer. Fix the blocker or conflict that is preventing the work from progressing. |
12h 49m ago | |
| role: responder | responder | #1 | active | Answers clarification questions from Jules. | You are the clarification responder for dev-manager. Your job is to answer Jules' question directly, briefly, and concretely. Prefer repository docs, tracked issue/PR context, and the current codebase. If the answer depends on live manager state, query the manager API yourself and turn that into a direct answer for Jules. Never tell Jules to query localhost, the manager API, or any other local-only service. If the docs do not cover the question, say exactly what is missing and the smallest next step. |
2d 4h ago | |
| role: splitter | splitter | #1 | active | Splits broad work into smaller slices. | You are a splitter. Break broad work into smaller, actionable slices and hand the next slice to the right worker. |
12h 49m ago | |
| role: test-role | test-role | #2 | active | Updated Description | Updated Prompt |
1d 2h ago | |
| role: test-role | test-role | #1 | inactive | Test Description | Test Prompt |
1d 2h ago |
| Time | Actor | Event | Target | Details |
|---|---|---|---|---|
| 1m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 1m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 1m ago | dev-manager-drift | reconciliation_observed | reconciliation_record: workspace_dirty_orphan:Stbmap/stbmap | {"kind": "workspace_dirty_orphan", "status": "active", "details": "git status --porcelain reported 2 change(s): M lib/src/platform_core/application/app_release_info.dart; M pubspec.yaml", "summary": "risky: repo Stbmap/stbmap workspace /home/stbmap/stbmap has 2 uncommitted change(s) and no active sessions", "seen_count": 81, "subject_id": "/home/stbmap/stbmap", "subject_type": "workspace", "repo_full_name": "Stbmap/stbmap", "reconciliation_key": "workspace_dirty_orphan:Stbmap/stbmap"} |
| 3m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 5m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 5m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 6m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 6m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 7m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 9m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 9m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 11m ago | dev-manager-drift | reconciliation_observed | reconciliation_record: workspace_dirty_orphan:Stbmap/stbmap | {"kind": "workspace_dirty_orphan", "status": "active", "details": "git status --porcelain reported 2 change(s): M lib/src/platform_core/application/app_release_info.dart; M pubspec.yaml", "summary": "risky: repo Stbmap/stbmap workspace /home/stbmap/stbmap has 2 uncommitted change(s) and no active sessions", "seen_count": 80, "subject_id": "/home/stbmap/stbmap", "subject_type": "workspace", "repo_full_name": "Stbmap/stbmap", "reconciliation_key": "workspace_dirty_orphan:Stbmap/stbmap"} |
| 11m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 11m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 13m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 15m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 15m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 16m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 16m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 17m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 19m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 19m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 21m ago | dev-manager-drift | reconciliation_observed | reconciliation_record: workspace_dirty_orphan:Stbmap/stbmap | {"kind": "workspace_dirty_orphan", "status": "active", "details": "git status --porcelain reported 2 change(s): M lib/src/platform_core/application/app_release_info.dart; M pubspec.yaml", "summary": "risky: repo Stbmap/stbmap workspace /home/stbmap/stbmap has 2 uncommitted change(s) and no active sessions", "seen_count": 79, "subject_id": "/home/stbmap/stbmap", "subject_type": "workspace", "repo_full_name": "Stbmap/stbmap", "reconciliation_key": "workspace_dirty_orphan:Stbmap/stbmap"} |
| 21m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from deferred to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 21m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from deferred to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 23m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 25m ago | scheduler | duplicate_session_prevented | repo: owner/repo | {"reason": "recent session sess-test-trace handling same issue #1", "item_number": "1", "repo_full_name": "owner/repo", "duplicate_of_session": "sess-test-trace"} |
| 25m ago | scheduler | duplicate_session_prevented | repo: Stbmap/dev-manager | {"reason": "recent session 3262775867211545215 handling same issue #243", "item_number": "243", "repo_full_name": "Stbmap/dev-manager", "duplicate_of_session": "3262775867211545215"} |
| 25m ago | scheduler | duplicate_session_prevented | repo: Stbmap/dev-manager | {"reason": "recent session 7170792322157361129 handling same issue #244", "item_number": "244", "repo_full_name": "Stbmap/dev-manager", "duplicate_of_session": "7170792322157361129"} |
| 25m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 25m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 26m ago | scheduler | goal_plan_recorded | github_item: Stbmap/dev-manager#256 | {"goal": "Ensure every new Jules session receives complete manager API instructions in the first `CreateSession` prompt, using the configured manager API base URL and explicit endpoint guidance, so reviewer and task sessions can ask questions, report blockers, share progress, and finish work even if the later notify follow-up is never delivered.", "reason": "This is a focused runner prompt-path fix under the fat policy: the runtime prompt change, manager-URL/settings reuse, and prompt assertions belong in one slice, and splitting them would create artificial dependencies between implementation and verification.", "summary": "Move manager API links and notify guidance into the initial Jules session prompt so startup does not depend on a follow-up message.", "repo_policy": "", "should_split": false, "verification": ["Issue, PR-reviewer, and task-session runner tests assert the initial `CreateSession` prompt includes the configured manager API base URL and the expected live-context endpoint list: `/questions`, `/sessions`, `/sessions/{id}`, `/jules-sessions`, `/jules-sessions/{id}/activities`, `/repos`, `/github-items`, `/roles`, and `/settings`.", "The initial prompt includes notify instructions for `POST /api/agent/notify/{session_id}` and the required `kind` values (`question`, `blocker`, `progress`, `enhancements`, `done`) instead of only promising a later follow-up message.", "If the best-effort post-create follow-up message is skipped or fails, the initial session prompt still contains enough manager API guidance for the worker to proceed correctly."], "admission_reason": "No existing session is recorded, and main's initial Jules session prompt still omits the manager API base URL and endpoint list.", "split_suppressed": false, "dependency_reason": "", "split_recommended": false, "issue_split_policy": "fat"} |
| 26m ago | dev-manager-codex | provider_result | github_item: Stbmap/dev-manager#256 | {"action": "issue_split", "status": "success", "provider": "codex", "item_type": "issue", "latency_ms": 179674, "item_number": 256, "prompt_name": "issue_split", "repo_full_name": "Stbmap/dev-manager"} |
| 26m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 26m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 27m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 29m ago | dev-manager-codex | provider_result | github_item: Stbmap/dev-manager#256 | {"action": "admission", "status": "success", "provider": "codex", "item_type": "issue", "latency_ms": 82738, "item_number": 256, "prompt_name": "admission", "repo_full_name": "Stbmap/dev-manager", "prompt_version_id": "11aac04d-7598-4ef2-9ea7-53be951f00c1", "prompt_version_number": 1} |
| 29m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 29m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 31m ago | dev-manager-drift | reconciliation_observed | reconciliation_record: workspace_dirty_orphan:Stbmap/stbmap | {"kind": "workspace_dirty_orphan", "status": "active", "details": "git status --porcelain reported 2 change(s): M lib/src/platform_core/application/app_release_info.dart; M pubspec.yaml", "summary": "risky: repo Stbmap/stbmap workspace /home/stbmap/stbmap has 2 uncommitted change(s) and no active sessions", "seen_count": 78, "subject_id": "/home/stbmap/stbmap", "subject_type": "workspace", "repo_full_name": "Stbmap/stbmap", "reconciliation_key": "workspace_dirty_orphan:Stbmap/stbmap"} |
| 31m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from deferred to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 31m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 33m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 35m ago | scheduler | duplicate_session_prevented | repo: Stbmap/dev-manager | {"reason": "recent session 7170792322157361129 handling same issue #244", "item_number": "244", "repo_full_name": "Stbmap/dev-manager", "duplicate_of_session": "7170792322157361129"} |
| 35m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
| 35m ago | dev-manager-sanity | sanity_auto_heal | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "remaining_findings": []} |
| 36m ago | dev-manager-github-intake | github-item-state-sync | github_item: 567df8df-5af1-44b9-b296-7e74d1429705 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "244", "repo_full_name": "Stbmap/dev-manager"} |
| 36m ago | dev-manager-github-intake | github-item-state-sync | github_item: 1f78cd4b-7750-4c49-b109-496dcad965c1 | {"state": "blocked", "reason": "state synced from ready to blocked", "item_number": "243", "repo_full_name": "Stbmap/dev-manager"} |
| 37m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: no sanity issues detected", "repairs": [], "findings": []} |
| 39m ago | dev-manager-sanity | sanity_ok | manager: sanity | {"status": "ok: auto-healed 2 issue(s): Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists; Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists", "repairs": ["Stbmap/dev-manager|issue|244 moved from blocked to ready because no active session exists", "Stbmap/dev-manager|issue|243 moved from blocked to ready because no active session exists"], "findings": []} |
The manager exposes the following JSON API endpoints for orchestration tooling:
GET /api/admin/sessions - List active sessionsGET /api/admin/sessions/{id} - Get one local sessionGET /api/admin/jules-sessions - List remote Jules sessions visible to configured accountsGET /api/admin/jules-sessions/{id}/activities - Inspect a remote Jules session's activity streamGET /api/admin/accounts - List configured accountsGET /api/admin/repos - List repository-to-workspace mappings used for intake and CodexGET /api/admin/github-items - List imported GitHub issues and pull requestsGET /api/admin/audit - List recent audit eventsGET /api/admin/report - Generate the daily factory report as JSON or text with ?format=textGET /api/admin/resume-checkpoint - Fetch the latest operator resume checkpoint as JSON or text with ?format=textGET /api/admin/repo-policies - List repo policy snapshots and historyPOST /api/admin/repo-policies/{id}/rollback - Restore a repo policy snapshotGET /api/admin/events - Subscribe to manager change events as an SSE streamGET /api/agent/context - Fetch the read-only agent-to-manager context bundle with report, questions, resume checkpoint, and sandbox capabilitiesPOST /api/agent/verify - Ask the manager to run an ephemeral verify sandbox for a repo with the current safe profilePOST /api/agent/notify/{session_id} - Send a session-scoped Jules notification to the manager with kind, optional title/body, and trace metadataPOST /api/agent/notify - Record an operator inbox item for human follow-upGET /api/admin/handoffs - Browse durable agent handoff rows by repo, roles, trace, session, item number, or free text queryGET /api/admin/settings - List runtime settingsPUT /api/admin/settings/{key} - Update a runtime setting via JSONGET /api/admin/decisions - Preview the orchestrator's next actionsGET /api/admin/questions - List sessions waiting on clarification, blocked, or paused with latest Jules activity, manager rationale, and routing confidenceGET /api/admin/inbox - List operator inbox items that still need attentionGET /api/admin/suggestions - List Jules suggestions that were manually relayed or imported from the dashboardGET /api/admin/memory - Browse durable manager memory entries by repo, kind, trace, session, item number, or free text queryPOST /api/admin/inbox/{id}/acknowledge - Mark an inbox item as acknowledgedPOST /api/admin/inbox/{id}/assign - Assign an inbox item to a person or teamPOST /api/admin/inbox/{id}/snooze - Snooze an inbox item until a future timePOST /api/admin/inbox/{id}/resolve - Resolve an inbox item and update the linked GitHub thread when possiblePOST /api/admin/suggestions - Relays a Jules suggestion into the manager ledgerPOST /api/admin/suggestions/{id}/promote - Promote a relayed suggestion into a GitHub issue or directivePOST /api/admin/suggestions/{id}/ignore - Ignore a relayed suggestion while keeping the historyPOST /api/admin/sessions/{id}/answer - Send a direct answer back to Jules for a sessionPOST /api/admin/sessions/{id}/pause - Pause a session locally without letting the remote Jules mirror overwrite itPOST /api/admin/sessions/{id}/resume - Resume a paused sessionPOST /api/admin/sessions/{id}/kill - Stop local management and requeue the linked GitHub item when possibleGET /api/admin/roles - List all agent rolesGET /api/admin/roles/{name} - Get details for a specific rolePUT /api/admin/roles/{name} - Update or create an agent roleGET /api/admin/prompts - List prompt versions and recovery playbooksPOST /api/admin/prompts - Create a new prompt version or recovery playbookPOST /api/admin/prompts/{id}/activate - Activate a prompt versionPOST /api/admin/prompts/{id}/rollback - Roll back to a previous prompt versionGET /api/admin/repo-policies - List repo policy versions and snapshotsPOST /api/admin/repo-policies/{id}/rollback - Restore a prior repo policy snapshot