wehub-resource-sync
f99010fae1
CI / lint (push) Failing after 1s
CI / frontend (push) Failing after 1s
CI / scripts (push) Failing after 1s
CI / Go Test (ubuntu-latest) (push) Failing after 0s
CI / frontend-node-25 (push) Failing after 1s
CI / docs (push) Failing after 0s
CI / coverage (push) Failing after 0s
CI / e2e (push) Failing after 0s
Docker / build-and-push (push) Failing after 1s
CI / integration (push) Failing after 4m43s
CI / Go Test (windows-latest) (push) Has been cancelled
CI / Desktop Unit Tests (Windows) (push) Has been cancelled
Desktop Artifacts / Desktop Build (Linux (arm64)) (push) Has been cancelled
Desktop Artifacts / Desktop Build (Linux) (push) Has been cancelled
Desktop Artifacts / Desktop Build (Windows) (push) Has been cancelled
Desktop Artifacts (macOS) / Desktop Build (macOS (aarch64)) (push) Has been cancelled
Desktop Artifacts (macOS) / Desktop Build (macOS (x86_64)) (push) Has been cancelled
48 lines
1.6 KiB
Markdown
48 lines
1.6 KiB
Markdown
# Product
|
|
|
|
## Register
|
|
|
|
product
|
|
|
|
## Users
|
|
|
|
agentsview is for developers who run multiple AI coding agents and need to
|
|
inspect, search, compare, and audit their local session history. They are
|
|
usually in a debugging, review, or cost-monitoring workflow where dense,
|
|
trustworthy data is more useful than promotional framing.
|
|
|
|
## Product Purpose
|
|
|
|
agentsview syncs agent session files into a local archive and serves a fast web
|
|
UI for browsing sessions, searching transcripts, tracking usage, and reviewing
|
|
costs across projects, models, and agents. Success means users can understand
|
|
what happened across their agent runs without sending data to an external
|
|
account or re-parsing raw files by hand.
|
|
|
|
## Brand Personality
|
|
|
|
Local-first, technical, focused. The interface should feel like an operational
|
|
tool: direct, compact, and calm enough for repeated daily use.
|
|
|
|
## Anti-references
|
|
|
|
Avoid marketing-site hero patterns, decorative SaaS dashboards, vague
|
|
assistant-themed illustrations, and visual treatments that make local developer
|
|
data feel like a hosted analytics product. Avoid hiding density behind oversized
|
|
cards or ornamental motion.
|
|
|
|
## Design Principles
|
|
|
|
- Put the session data first.
|
|
- Preserve local-first trust.
|
|
- Keep repeated workflows compact and predictable.
|
|
- Make freshness, filtering, and state legible.
|
|
- Prefer familiar product affordances over novelty.
|
|
|
|
## Accessibility & Inclusion
|
|
|
|
No project-specific accessibility profile is documented yet. Default to clear
|
|
focus states, keyboard-reachable controls, readable contrast in light and dark
|
|
themes, reduced-motion-safe transitions, and chart labels that remain visible
|
|
across supported viewport sizes.
|