07 Tools / Private repository
Relay
Project containers, memory and context accounting for long-running coding sessions.
- Purpose
- Project containers, memory and context accounting for long-running coding sessions.
- My contribution
- Built the self-hosted launcher, dashboard and project context workflow.
- Result
- A working launcher that carries project decisions between sessions and makes context use visible.
A self-hosted launcher and dashboard for isolated coding projects, persistent memory and context-cost reporting.
Workflow
- 01Create project container
- 02Seed session memory
- 03Work with context guards
- 04Review usage in dashboard
Before
Long coding sessions repeatedly loaded large documents, tool lists and command output into context.
After
Projects use isolated containers, scoped memory and a searchable skill index with context reporting.
Problem#
Long coding sessions repeatedly resend context. Tool listings, large file reads and verbose commands consume the budget before the useful work is done.
Background#
Relay was built around measurements from real sessions: command text accounted for 53% of context growth in the session described by the project README, while large prompts also increased cost, latency and the chance of losing detail during compaction.
Implementation#
Built a self-hosted Flask and React dashboard with one container per project, graph-backed memory, a searchable on-disk skill index, context guards, a session ledger and transcript-based usage reporting.
Challenges#
The launcher has to keep project context and credentials isolated while still allowing approved host operations. Its restricted broker, audit log and project-specific containers provide those boundaries.
Results#
A working homelab launcher that makes context spending visible and carries decisions between sessions without loading whole documents at startup.
System structure
How the parts connect
Flask + React
The dashboard provides project entry points and usage information.
Project containers
Each project has its own working environment and context.
Graph memory + ledger
Scoped decisions and session outcomes support continuity.
Restricted broker
Approved host and credential operations cross a controlled, audited boundary.
Project outcomes
53%Context growth from commands
454Searchable skills
1Container per project
Evidence & scope
The 53% command-text figure refers to one measured session described in the original project account. It is not a general benchmark or a claimed saving. Source access is private.