Coding agents.
Source-backed observations, repository reads, and evidence carried between sessions. Local validation keeps reuse grounded in the current code.
Your next agent shouldn’t have to start over.
Let useful work carry forward.
Vlaid works alongside existing coding agents.
Same tools. Shared evidence. Less rediscovery.
Useful work shouldn’t disappear when a session ends. Vlaid preserves source-backed evidence so the next agent has something to build on.
def should_retry(response): if response.status == 429: return True return response.status >= 500A recorded coding comparison, from the first read to the final check.
Measured across coding and operations workflows. We keep the full experiment history, including earlier versions and results that didn’t improve.
Read the benchmark notesAcross all valid paired operations runs.
Earlier and reverted versions included.
72 out-of-sample coding pairs.
95% confidence interval: 15.8–24.6%.
Reported across October 17–19.
Every included session passed.
Internal benchmarks, not a savings guarantee. Figures measure API-equivalent cost, not subscription bills. Workloads differ; coding results include Claude prompt-cache settings. Methodology and limitations ↗
Repeated discovery happens wherever agents gather information. We’re starting with a problem we can inspect and verify.
Source-backed observations, repository reads, and evidence carried between sessions. Local validation keeps reuse grounded in the current code.
A future where research, finance, and operations can build on work already gathered. Shared sources. Clear provenance. Context that carries forward.
Concept in development. Not currently supported.Infrastructure for agents that work together.