Skip to main content
Farmslot

Your OS and IDE for scaling agentic engineering work.

Run many agents across many project types, computers, and model subscriptions. Watch and steer them while they work, then trust the result through visual validation, executable recipes, and proof artifacts instead of final claims.

Watch-and-steer loopDemo-ready
Poster preview of the Farmslot recipe evidence loop
DispatchWatchSteerValidateReviewImprove
Active development previewFarmslot is moving quickly while the product is finalized in one repo. Experimental features, large/transient files, APIs, runner contracts, fixtures, and docs may change while the project matures.
Why it matters

Scale your own workflow without losing trust.

Farmslot is the product layer around agents: a framework for many project types, an OS for coordinating the fleet, an IDE for watching and steering work, and a proof-first recipe layer for visually and mechanically validating the result.

Demo plan

Each short clip should explain one product promise.

The best demos are narrated feature explainers: dispatch real work, watch and steer it live, validate with recipes, review the evidence, and feed lessons back into the next run.

Poster showing a Command Center run timeline with terminal and artifact panelsVideo planned
Video planned

Watch and steer a supervised run

Show dispatch, slot assignment, live terminal output, decision gates, and how the human can redirect before trusting the result.

Poster showing a recipe graph flowing into screenshots, traces, and a summary artifactVideo planned
Video planned

Recipe evidence run

Show a recipe run turning setup, real actions, visual validation, assertions, HUD messages, and proof artifacts into review evidence.

Poster showing a mobile companion watching worker status and run progressVideo planned
Video planned

Companion mobile supervision

Show the operator checking workers, terminal status, and run progress from the mobile companion without losing control.

Recording checklist

The landing page currently uses static public-safe placeholders. When final clips are recorded, keep them short, caption-friendly, poster-backed, and verify representative frames before publishing.

View recording plan →
Recursive feedback

Every run should make the next run better.

Farmslot treats validation and retrospectives as part of the product loop. Runs create evidence, review finds gaps, retrospectives capture durable lessons, and those lessons improve recipes, prompts, docs, and adapters.

Read the feedback loop
  1. RunExecute in an isolated slot with live logs, artifacts, and human decision gates.
  2. ObserveCapture terminal streams, screenshots, traces, summaries, and reviewer notes.
  3. ReviewUse humans and independent model reviewers to find gaps before merging.
  4. RetrospectConvert failures, flakes, and repeated review comments into curated learnings.
  5. CurateKeep only reusable lessons that can become checks, prompts, recipes, docs, or adapters.
  6. ImproveUpdate prompts, recipes, docs, and project adapters before the next run.

Start small, then deepen the contract.

Import a project with hooks, add a runner manifest, adopt recipes where behavior needs proof, then use retrospectives to keep improving the system.