Show HN: A provider-agnostic agent loop built on ports and adapters
An MIT-licensed agent loop — call model, run tools, feed results back, stop — works with any OpenAI-compatible endpoint, built to replace the boilerplate every framework reinvents.
12 articles · 3 categories
The finishable daily brief
Thursday, Jul 2, 2026
12 articles · 3 categories
read top to bottom · then stop
In 30 seconds
Today's signal was less about new models and more about the infrastructure and judgment needed to run coding agents reliably — four separate open-source projects (an agent loop, repo documentation, layered memory, and an architecture graph) all attack the same problem: agents lose context between sessions and across multi-repo systems.
On the compute side, Apple began running Private Cloud Compute on Google Cloud's infrastructure and NVIDIA opened its AI buildout to capital partners, both signs that production inference, not training, is now the bottleneck compute providers are racing to solve.
Four new open-source projects target the same gap — coding agents lack durable context — with a provider-agnostic tool-call loop, repo documentation generation, layered memory, and a deterministic architecture graph, plus a critique of the instruction files agents already rely on.
An MIT-licensed agent loop — call model, run tools, feed results back, stop — works with any OpenAI-compatible endpoint, built to replace the boilerplate every framework reinvents.
LangChain's OpenWiki generates and maintains codebase documentation so coding agents can pull the repo context they need instead of loading one giant instruction file.
Knotic splits agent memory into project, session, and docs layers so coding agents keep state that survives across sessions.
Built after a golf app's codebase split across iOS, Android, backend, and frontend repos, Enola generates a deterministic architecture graph so agents and humans can navigate a multi-repo system.
A critique argues Agents.md instruction files drift out of sync with the codebase they describe, and nothing currently validates that the file an agent reads still matches reality.
Practitioners focused less on new models and more on how to steer and watch agents already in production, through skill design, human-in-the-loop judgment, and dedicated observability tooling.
Paul Bakaus argues against one-shot AI design in a "loopmaxxing" era, making the case that agents still need human judgment to steer them rather than a single perfect prompt.
Citing Geoffrey Litt's talk at AI Engineer, Simon Willison frames the core challenge of collaborating with coding agents as needing to understand their output well enough to meaningfully participate in it.
A factory-safety agent design keeps the model responsible only for reasoning while deterministic code handles the actual routing and actions, separating judgment from execution.
Foglamp is a new open-source tool purpose-built for tracing and observing agent behavior in production.
Compute providers kept expanding capacity and training guidance for production AI workloads, from a confidential-compute cloud partnership to reinforcement-learning training practices.
Apple will run Private Cloud Compute on Google Cloud using NVIDIA Blackwell GPUs, Intel TDX, and Google's Titan chip, while keeping its own append-only hardware transparency log independent of the host provider.
NVIDIA is opening its compute buildout to capital partners as demand shifts from model training toward continuously operating "AI factories" that generate inference tokens at scale.
AWS lays out best practices for multi-turn RL training, covering trustworthy training environments, external evaluation setup, and reward design aligned with the end task.
You are caught up for this edition