Reason Machines' open-source Aspen Git server solves the bottleneck of high-concurrency AI agent traffic, enabling hundreds of agents to push and fetch simultaneously without interference.
AI-generated summary. Check the original reporting for context and accuracy.
This is the available feed excerpt, which may be shortened or in the publisher’s original language.
Reason Machines has released Aspen, an open-source Git server for AI agent traffic. It targets repositories that hundreds of agents push to at once. Aspen independently implements the design OpenAI described for Pando. TL;DR Size: One Rust binary. Branches live in PostgreSQL (or SQLite), packs live in object storage. Runs on: A laptop (aspen dev), one host via Docker Compose, or Helm and Terraform clouds. Performance: Pushes to different branches never wait on each other, and fetches reuse stored packs. Best: 567 pushes per second sustained for 5 minutes on one 8-core server (self-reported). Worst: Landing on main runs at about 4 per second, and the project is pre-alpha. Bottom line: Best: per-branch writes remove the per-repository push ceiling. Worst: no releases, no web UI, and the 24-hour durability gate is not met. What is Aspen? Aspen is a self-hostable Git server from Reason Machines that scales writes per branch, not per repository. It speaks plain Git over HTTPS and SSH. Packs go to S3-compatible object storage; branch history goes to PostgreSQL. Why do classic Git servers struggle with AI agents? An agent pushes every few minutes, and CI fetches after each push. Per Reason Machines, a classic server queues every push to a repository together. It also builds a fresh pack for every fetch. Server work grows with clients, not with new code. OpenAI hit this wall and built Pando. It cut median push latency by nearly 5x and serves nearly a petabyte daily. How does Aspen work? Aspen follows Pando and drops 2 claims most Git servers keep. Per-branch compare-and-swap Each branch is a chain of versions in one Postgres row. A push uploads its pack, then moves the branch with one compare-and-swap. Pushes to different branches never wait for each other. If 2 pushes race on one branch, one wins. The other gets Git’s usual “fetch first” error. The cost: branches may be read at slightly different moments. Stored packs instead of per-client packs Aspen ne
An automated sorting aid based on source trust, keywords, and entities, on a scale of 1–12. High: 9–12; medium: 6–8; low: 1–5. It does not measure urgency, verify reporting, or indicate editorial endorsement.
This matters because it highlights a practical strategy for retaining skilled employees by addressing their personal relationships and support systems.
0sec Labs open-sourced an AI security harness that automates vulnerability investigations and code reviews, allowing developers to integrate their own LLMs for enhanced software security.
MIT’s FLEX platform allows robots to interpret the broader intent behind human commands, enabling more flexible and intuitive interaction beyond literal instructions.