Why it exists
Agent sessions, test runs, and requests for input can be scattered across terminals and logs.
Portfolio / CASE STUDY
Public macOS developer tool
A local dashboard that turns Codex and Claude Code activity into a pixel office and an inspectable session history.
Independent local tooling and interface design
Agent sessions, test runs, and requests for input can be scattered across terminals and logs.
I built a local collector and dashboard that read session logs and process metadata, normalize the activity, and show it in one place.
A standard-library HTTP server binds locally and serves a defined set of pages and datasets. Generated activity stays with the local checkout.
The server fingerprints the inputs, rebuilds the views when they change, and emits events for the browser to refresh.
Optional task-board syncing is a separate setting. The default task board reads the configured task file.
Runs locally on macOS. Coverage depends on the session logs and process metadata available on the machine.