Moved from issue #4 on 2026-09-04. Issues are for bug reports and feature requests; the roadmap lives here. To pick up an item, open an issue referencing it.
- 7 platforms — OpenClaw, Codex, Claude Code, Hermes (SQLite), OMP, DeepSeek Harness and Gemini CLI, parsed from their native log formats
- Session browser with tool-call inspection, trace/waterfall view, spawn tracking and message timeline
- Prompt tooling — extraction (noise filtered), template clustering with outcome attribution, Claude-powered rewrites, and a prompt library that installs entries as native slash commands
- Global search across all platforms, insights dashboard, incremental session backup
- React + Vite frontend served by an Express backend; 332 tests on Node's built-in runner (
npm test, 2026-09-23), CI on Node 22 - Evidence-backed failure events and local review with full-result invalidation, evidence navigation and narrow-screen session layout
The product direction is local execution evidence for the coding agents you already use: what actually ran, which results support a conclusion, and what the log cannot establish. Automatic facts come first; human labels are optional. Native agents increasingly include dashboards, usage metrics and workflow progress, so generic statistics are not the differentiator. Stars, downloads and screenshots alone do not establish usefulness.
External grounding: official guidance emphasizes executable verification, background subagent workflows and coordination/resume limits. These are capabilities and engineering constraints, not market-size evidence. User issue reports and vendor-fixed bugs are research inputs, not proof of permanent product gaps.
| Priority | Outcome | Acceptance, not a promise |
|---|---|---|
| P0 | Make the new workflow immediately testable | A demo-only entry opens a clearly synthetic case: 7 pending records in 2 events, all evidence accessible, local review does not rewrite automatic results. Preserve the existing default demo and samples. |
| P1 | Current-session review portability implemented | Preview-only import and explicit plaintext download; exact identity/evidence matching, no overwrites, bounded schema and partial-failure reporting. Validate with synthetic migration and publish after CI; whole-history backup and path remapping remain out of scope. |
| P2 | Execution/verification evidence, not another statistics dashboard | Automatic health and modification/check chronology distinguish before/overlap/after and unknown outcomes. Codex process IDs now connect launch/poll/exit evidence without rewriting history or original check start. Next investigate explicit task/child linkage and per-step outcomes; reject ambiguous associations rather than relaxing shell assumptions. Deterministic tests and frozen-log checks are not file coverage, human time saved or universal accuracy. |
| P3 | Make releases reproducible for contributors | Keep clean-install tests, generated fixtures, documentation claims and release/package verification aligned. Add browser regression automation when it can run deterministically without personal logs. |
The next integration surface is a read-only offline CLI, not a new agent runtime or hosted service. inspect emits versioned facts and source references using the same generated rules as the UI. This lets an agent or CI step consume evidence without manual tagging, a browser or model scoring. Explicit exit policies and coverage failures must never become a generic "task passed" claim. Current scope is one stable Codex/OMP/Claude Code JSONL file; logs remain on the machine.
No launch dates or star-count targets are promised. Progress is gated on these observable outcomes. Physical-device/keyboard coverage and complex Trace/analytics layouts remain separate work, not implied by the session-screen checks.
- Publish to npm so
npx agent-xrayworks without cloning — automated from GitHub releases (v1.14.0+) - Hosted live demo on GitHub Pages with clearly-labeled synthetic session data, so people can try the UI before installing
- Gemini CLI adapter (
~/.gemini/tmp) — shipped (#5) - More platform adapters — opencode and Aider are candidates, not a measured demand ranking. Require representative logs and parser acceptance tests before prioritizing them over the review workflow.
- Session export & sharing — render a session (with tool calls) to a standalone Markdown/HTML file you can attach to a bug report or blog post (#6)
- Cost & token analytics — per-session and per-day token spend, broken down by model, building on the token counts we already parse for the summary panel
- Watch mode ergonomics — highlight the currently-active session and surface "agent is waiting for input" state in the sidebar
From a product review (2026-08-21) — funnel and retention fixes around the npm release:
- Demo must showcase the differentiators (search, spawn navigation, prompt library), not the thinnest layer (#12)
- First launch: auto-pick the first platform that actually has sessions (#13)
- Prompt optimization: drop the hard dependency on a local claude CLI (#14)
Structural cleanups surfaced by a code review — not features, but they lower the cost of every future one:
- Extract a unified PLATFORMS registry to collapse seven copy-pasted adapter skeletons (#8)
- Decide the legacy UI's fate and eliminate the markdown/pure double-write (#9)
- Split server.js into route modules and lib/ business logic (#10)
- Cloud sync or any server-side storage of session data — AgentXRay stays a local, read-only viewer of your own logs
- A plugin marketplace — adapters land in-tree until the format count justifies more
Issue references above are created alongside this roadmap; anything without a link is open for discussion.