Skip to content

AgentsView live mode: the workstation unit syncs continuously as the live view of all jobs - #424

Merged
seathatflowsinourveins merged 3 commits into
mainfrom
claude/agentsview-live-mode-20260927
Sep 27, 2026
Merged

seathatflowsinourveins merged 3 commits into
mainfrom
claude/agentsview-live-mode-20260927

Conversation

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator

Scope

  • What this PR changes: the AgentsView user unit runs in live mode (no --no-sync) as the live view of all jobs, and the docs, example unit and recipe now say so.
  • Base commit: a260a0f5
  • Lane: lane:foundation
  • Owned paths touched: docs/native-dashboards.md, examples/agentsview-archive.service.example, recipes/README.md, manifests/evidence.json (re-registration only)

Why. The user chose AgentsView as the live "all jobs" view (2026-09-27). The workstation unit already runs this way. Main still documented the frozen --no-sync archive.

Changes

  • docs/native-dashboards.md:
    • a dated "Live mode on the workstation (2026-09-27)" section covering what serve does without --no-sync, lane homes through [agents.codex] homes, one local observation, the alternative, and the overturn condition;
    • the unit sentence and the data-dir caveat now match live mode.
  • examples/agentsview-archive.service.example: ExecStart without --no-sync, with a comment on when to add it back (an archive that must stay frozen).
  • recipes/README.md: one sentence. The on-demand recipe keeps --no-sync for a dedicated scoped archive; the persistent unit runs live.

SOTA sources

Evidence-class table

Claim Evidence class Command / receipt
What serve does without --no-sync source_review the pinned lines above
The workstation unit runs without --no-sync local_integration (observation) systemctl --user cat agentsview-archive.service (ExecStart has no --no-sync) and agentsview serve status, both run 2026-09-27
New Codex sessions appear without a manual sync local_integration (observation, not a receipt) agentsview session list --agent codex --active-since 2026-09-27T18:57:00Z --include-automated --include-one-shot --include-children --json. All 14 thread ids of the 18:58–19:04Z jcodemunch probe were listed; the unit had restarted in live mode at 18:37Z

Local commands run

$ python3 scripts/validate.py
{"components": 69, "hashed_files": 7348, "profiles": 4, "receipts": 159, "status": "passed"}

Decision record

The dated section in docs/native-dashboards.md names:

  • the alternative: a frozen archive plus on-demand agentsview session sync, which does not show running jobs;
  • the overturn condition: an archive that must stay frozen, for example one a receipt cites, or continuous sync's load or a parser regression harming the host.

Host evidence

None changed. The 2026-09-27 persistence receipt (#404) records the unit before the switch. A live-ingestion use receipt is a follow-up.

🤖 Generated with Claude Code

…live view of all jobs

The user chose AgentsView as the live "all jobs" view (2026-09-27), so the
user unit drops --no-sync. At v0.43.0 (9be7745a) serve then runs its initial
sync, the sync engine, file watchers, a 2-minute poll of unwatched directories
and a 15-minute periodic sync (cmd/agentsview/main.go#L43-L45, L206, L306-L325,
L1969, L2726). Lane CODEX_HOMEs are added through [agents.codex] homes, which
add to the defaults (docs/configuration.md#L988-L1013). The on-demand recipe
keeps --no-sync for a dedicated scoped archive.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Sep 27, 2026
Scout and others added 2 commits September 27, 2026 15:46
…o upstream

GPT-6 read-only review of #424 (two P3 findings, both verified at 9be7745a):
- the scheduled 15-minute reconciliation covers only providers that declare
  PeriodicReconcile (main.go#L2910-L2955); Codex and Claude Code do not, so
  their sessions arrive through the watcher and the 2-minute poll;
- [agents.codex] homes is the workstation's selected method, not the only one;
  dirs, the directory environment overrides and [[session_sources]] are the
  supported alternatives (docs/configuration.md#L1011-L1013).

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…r the hot-file protocol

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator Author

Cross-family review (GPT-6, read-only codex exec on head 2271719) and repair

The review reported two P3 findings and nothing higher. Both were verified against AgentsView v0.43.0 (9be7745a) and fixed in 08e250c:

  1. The 15-minute pass. It reconciles only providers that declare PeriodicReconcile (cmd/agentsview/main.go#L2910-L2955).
    • At this pin those are OpenHands, Goose, Aider, Evener, Omnigent and Codebuff (internal/parser/types.go).
    • Codex and Claude Code sessions arrive through the file watcher and the 2-minute poll.
    • The doc and the example unit's comment now say so.
  2. [agents.codex] homes. The doc now calls it the workstation's selected method and names the supported alternatives: dirs, the directory environment overrides and [[session_sources]] (docs/configuration.md#L1011-L1013).

b72c7c1 merges main (0f76651) under the hot-file protocol, and python3 scripts/validate.py passed. This was one review round and one repair round; there are no residual findings.

🤖 Generated with Claude Code

@seathatflowsinourveins
seathatflowsinourveins merged commit e82e6be into main Sep 27, 2026
24 checks passed
@seathatflowsinourveins
seathatflowsinourveins deleted the claude/agentsview-live-mode-20260927 branch September 27, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant