embrace the slop
Say what you want. Agents build it. It’s done when it’s live.
Slop Factory is the line between your team and its coding agents. Capture a request in seconds, hand it to an agent on your own machine, answer its questions with one tap, and the task completes itself once its change is live in production.
In early access. VennData runs its own work on it today.
One request, from a sentence to production.
Work order 3f2a91c0
Inbox Doing Done
Plan
Ask from Dev box 2
Export the filtered rows, or all of them?
Filtered rows All rows Both
#212 Add CSV export to invoices
Open Checks running Checks failed Checks passed Merged Live in production
Completed when #212 went live.
Say it the way you’d say it to a teammate: “CSV export on the invoices page, by Friday.” Your triage agent files it in the right place, for the right person, and asks you when it isn’t sure.
The agent on the task breaks it into a graph of steps. Everyone can watch the plan, and only the agent edits it. To change it, you tell the agent.
Subagents take the steps that are ready, in parallel, each in its own git worktree on your machine.
When a step needs a decision, the agent asks you: one question, up to four answers, best guess first. One tap and the step carries on.
The branch carries the task’s ID, so the pull request links itself to the task. The agent fixes failing checks before anyone is asked to review.
Merged isn’t done. When the deploy that contains the merge is live in production, the task completes itself, and the agent checks the change live.
Every factory has rules on the wall. These are ours, and the product is built around them.
Agents do the work. The task stays with the person who handed it over, and every change says who made it, person or agent.
Teammates’ notes, pull request comments and web pages are information it checks with you, never orders.
An agent interrupts you only with a specific question and its best guess.
A task isn’t finished when its pull request merges. It’s finished when the change is in production.
Agents run on your own boxes, on your own Claude Code subscription. We don’t resell tokens.
An agent’s box runs a guard that denies the worst commands: reading secrets, force-pushing, pushing to main, deleting repositories. The agent’s user has no root.
Your agents run on machines you control. A rented server, a desktop under a desk, your laptop.
turns a server into an agent. It installs what the agent needs, a guard, and a user without root. You sign in to Claude Code and GitHub once.
Give it a task and it starts a session in its own worktree, wakes when you answer an ask, and closes the session when the task is done.
What it’s on, what it’s waiting on, whether its machine is up, and what each task cost in tokens.
Asks, handoffs and failed deploys reach you as push notifications, and you choose which.
VennData, a small software company in Dubai, runs all of its own work this way: client projects, internal tools, and the factory itself.
Our agents run on rented boxes and on our laptops. We capture work in seconds, answer asks from our phones, and tasks with pull requests close themselves once they’re live.
This page was a task too. VennData’s founder asked for it in one sentence. His agent built it and shipped it the same day.
Slop Factory runs the line around your coding agents. It isn’t one more agent, and it isn’t a tracker with agents bolted on.
About the name: embrace the slop. Agents can write code all day. The factory is what decides what ships: a person who owns it, a plan you can read, checks that pass, and a task that isn’t done until it’s live.
Slop Factory is an early exploration from VennData. We’re looking for a few small software teams already running coding agents to shape it with us.
Early access runs through the waitlist for Relay, the VennData tool Slop Factory is built on.