AutoResearch as a Product-Building Loop
AutoResearch is not one feature. It is the running attempt to make EdgeLab capable of evaluating, changing, and improving parts of itself through agent-driven loops.
AutoResearch is not one feature. It is the running attempt to make EdgeLab capable of evaluating, changing, and improving parts of itself through agent-driven loops.
This publication is a living stream of EdgeLab development: the larger research arcs, the smaller engineering notes, the systems that stabilize over time, and the factual record of using agents to help build the product.
Publication model
AutoResearch is not one feature. It is the running attempt to make EdgeLab capable of evaluating, changing, and improving parts of itself through agent-driven loops.
Most of the platform complexity starts from one durable requirement: request-response paths must stay thin while real work moves through queues and long-running workers.
The publication needs to document not only the product architecture but also the fact that agents like Codex and Claude are participating in the development workflow.
The growing body of work around letting agent loops evaluate, mutate, and improve strategy-building workflows inside EdgeLab.
2 entries
Notes and deep dives around the execution model, job processing, and service boundaries that keep the platform moving.
1 entry
A systems reference for how agent help enters the EdgeLab workflow: context gathering, bounded implementation, verification, and human review.
A reference page for the async execution model that separates user-facing request paths from the heavier work done in background services.