PocketCorp Operations
Name a goal in one sentence. Your server designs the company, keeps five tasks on the desk, does the work, and shows you everything before it leaves the building.
Operations is the company that runs itself. It is already installed at operations.<your-server-id>.cloud.pocketcorp.agency: type a goal — or let the agent invent the whole company — and it names it, writes the brief, seeds six areas of work, publishes a landing page on a real subdomain, and puts exactly five tasks on your desk. Start them yourself, or flip on auto mode and let it work toward the goal on a schedule while everything it produces waits in review queues.
Operations executes its tasks through whichever agent your server shipped with — Hermes or OpenClaw — and falls back to the Claude Code CLI that every Pocketcorp carries. You don’t wire anything: the backend finds the installed agent itself, and auto mode drives it on a schedule.
Start Here: One Prompt
Copy this prompt and send it to the agent on your Pocketcorp. It sets up everything in this guide and reports back when it’s done. The steps below explain what your agent is doing — and how to check its work.
I just opened my Operations dashboard at
operations.<my-server-id>.cloud.pocketcorp.agency and I’m deciding
what company it should run.
Interview me, five questions max: what I’m good at, how much time
I’ll actually give this per week, whether I want revenue fast or an
audience first, what I refuse to do. Then propose three one-sentence
company goals I could paste into the goal box — concrete enough that
a stranger could tell after 90 days whether it worked.
If I like none of them, I’ll press “Invent one for me” in the
dashboard instead and let it surprise me.The Stack
Name the goal — or don’t
Open the dashboard and type one sentence into the goal box. That is genuinely all the setup there is: the agent designs the rest — name, positioning, a company brief it re-reads before every piece of work, and the first five tasks.
Sell a tiny SaaS that helps indie bakers take pre-orders.
Crumbqueue is ready — pre-order pages for home bakers, positioned against form builders that don’t handle pickup slots. Landing page is live on your subdomain. Five tasks are on your desk; the first one specs the order page.
No idea at all? Press “Invent one for me”. The agent picks a concrete, unsaturated business a single person plus AI agents can actually run — and you can regenerate until one fits.
Work the five tasks
There are always exactly five pending tasks, each tagged with its area — Features, Research, Marketing, Content, Ads, Operations. Read one and press Start to watch the agent execute it live, Dismiss to swap it for a fresh suggestion, or type your own task and it joins the pool.
Finished work lands in queues, not in the void: markdown documents to read, tweet drafts to approve, ad campaigns to submit, domain requests to okay. The activity feed is the company diary — everything that happened, newest first.
Nothing posts itself in manual mode. A tweet leaves the building when you press Post; an ad when you press Approve & submit. The agent proposes, you dispose.
Connect X once
Tweets post through the X API. Your Pocketcorp may already carry platform keys — Settings tells you. To use your own account instead, create a free app at developer.x.com and paste the four keys into Settings; they override the platform defaults and never leave your server.
Flip on auto mode
The Autopilot switch on the dashboard turns the company loose: on a schedule you set, it reviews the goal, picks the most useful pending task, executes it, tops the pool back up to five, and posts approved tweets within your daily cap. Ads and domains still queue for your one-click approval — those spend money and claim names, so a human stays in that loop.
- Cycle every N minutes — default 60, minimum 5.
- Daily caps on task runs and tweets, so a runaway day is impossible.
- Three failed cycles in a row pause auto mode with a note in the feed.
Talk to your company
The Chat tab is a standing conversation with your company’s operator — same agent, same workspace, full memory across sessions. Ask what it’s working on, hand it context, or argue about direction. It can read and write the company’s files, but publishing still goes through the queues.
What you end up with
A company with a name, a landing page on a real address, a desk that always holds five next moves, and an autopilot that works toward your goal while everything public waits for your yes.
