The problem
Ideas die in the gap
An idea hits at 2am. You turn it over. By morning it is still just a thought, lost between everything else on your plate. The distance between "I have an idea" and "it is live" is where most ideas quietly die.
How to use
You don't install it. Your agent does.
Copy the setup guide and paste it to your coding agent - Claude Code, Hermes, Cursor, whatever you run. It reads the steps and walks you through standing up the whole factory: the host, the runtime, the memory, and your first workflow.
Paste this to your agent
Set up Dark Factory for me. Read the guide at http://dark-factory.techmeat.dev/LLMS.txt and follow it step by step, asking me whatever you need as you go.
Copies the full step-by-step guide to your clipboard.The idea
Hand it to a factory
Drop the idea into a channel. A team of agents scopes it, plans it, builds it, and ships a live URL. Any idea becomes a deployed project. The point is the factory itself, not any single thing it happens to build.
The foundation
Two layers do the heavy lifting.
Underneath everything sit two pieces that always work together: one runs the agents, the other remembers what they do.
The hands
Hermes AgentThe runtime
Hermes runs the agents and keeps the factory alive on a server, around the clock. It turns a plan into real work: the tasks, the tools, and the agents that carry them out.
The memory
Open Second BrainThe shared memory
A file-based memory every agent reads and writes. It is how the factory remembers what happened in each project, no matter how many run through it at once.
Neither works alone. Hermes Agent is the hands, Open Second Brain is the memory. Together they are the floor the factory stands on.
Architecture
A studio, encoded.
On top of that foundation, Dark Factory is organized like a small studio that never closes.
A
An always-on host
Hermes lives on a server, so the factory is reachable at any hour. Send an idea at midnight and the work starts at midnight.
B
A team of specialists
Like a real studio: an orchestrator that runs the show, developer agents, and other roles. Each agent is focused on the one thing it does best.
C
Workflows
Fixed playbooks the team follows, so every idea is handled the same careful way instead of being improvised from scratch each time.
How a project is born
From a message to a live URL.
Five steps turn a sentence in a channel into something you can open in a browser.
01
Drop the idea
You post an idea into the channel, in plain language. No spec, no ticket, no setup.
02
A short brainstorm
The orchestrator asks a couple of clarifying questions first, so it builds the right thing rather than just something.
03
Onto the board
It breaks the work into tasks on a kanban board and hands each one to the specialist best suited to it.
04
Agents build
Research, plan, code, review. The agents do the work end to end; you are not writing any of it by hand.
05
Ship
The project is deployed to a live URL and the link comes back to the channel where it started.
Beyond day one
It keeps working after launch.
The same pipeline does not stop at version one. Need a feature on a project that is already live? One message in the channel, and the agents add it. The factory treats a change request like any other idea.
See it run
Watch the factory build, end to end.
A short walkthrough of one idea going from a channel message to a deployed site, planned and shipped by agents.
Preview · temporary cut, full walkthrough coming soon
What's next
Open the doors.
Today Dark Factory runs as a private channel. Next it becomes a service anyone can use, with a viral loop on X: post an idea, mention @darkfactoryagent, and the bot replies in the same thread with a working link. Every reply is the product demonstrating itself, in public.