Proactive agents run without a prompt, so each run has to start from what earlier runs learned. How we built memory for Praxen Inc.'s agents on git: one repository per team, a nightly clean-up, and lessons from merged pull requests.
Proactive agents run without a prompt, so each run has to start from what earlier runs learned. How we built memory for Praxen Inc.'s agents on git: one repository per team, a nightly clean-up, and lessons from merged pull requests.
Almost none of the pull requests Praxen Inc. opens were asked for by an engineer, and a longer description does not make them easier to review. We are experimenting with a narrated video for every fix. Why, what it looks like, and what happened to merge rates.
Vi Tran Agents that run software need a context graph of the app: every resource, what it connects to, the repository that deploys it and the team that owns it. How we built one on Durable Objects, keep it fresh across every provider without polling AWS, decide what counts as a change, and delete from it safely.
Our agent makes thousands of small decisions a day. We moved them from LLMs to Jev, a model that doesn't write text, and cut the cost by 39%.
Vi Tran Nothing in your pipeline asks whether a change is safe for prod. This is the check we built that does, and how we got it to finish before your tests do.
Vi Tran Praxen Inc.'s autofix used to be a workflow of multiple agents, each responsible for a single task, with an orchestrator managing state between them. We moved to a single agent which does the entire job, from evidence gathering, hypothesis testing to pull request.
Aleksandr Diamond Cloudflare Durable Objects run in V8 isolates with a hard 128 MB limit. Ours idled at ~140 MB and was reset ~300 times a day. 130 MB of zod schemas were built at module load, most of them by code that was never called. How we profiled the production bundle, the two fixes, and the numbers, 218 MB to 82 MB and resets to zero.
Aleksandr Diamond No posts match that search.