Pattern 5: Concurrent Event-Driven Multi-Agent Loop. Coordinates multiple Claude sessions as OS threads sharing a common event bus and memory address space. Every loop cycle is a full improvement cycle: execute, eval against benchmark (KEEP/DISCARD), emit friction events during work, close with post_run_metrics, agent self-assessment survey saved to retrospectives, memory persistence, and Triple-L
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/os-improvement-loop?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Marketing skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Concurrent Agent Loop
Pattern 5 in the agent-loops taxonomy. Treats concurrent Claude sessions as OS threads
sharing a filesystem address space. The kernel event bus coordinates signals. Every cycle
includes real work, eval against benchmark, friction tracking, agent self-assessment survey,
post-run metrics, and memory persistence. The OS learns from every run.
Triple-Loop Architecture
There are two distinct Triple-Loop orchestration cycles operating at different scopes.
[Description truncada. Veja o README completo no GitHub.]
