The Agent Desk is a one-person company built in a repo. I run it with Cursor and AI agents — each role has an SOP, each post ties to something real, and nothing publishes without my sign-off.
Why this desk exists
Content ops was eating time — briefs, drafts, scheduling, tracking what shipped. Same problem I solve everywhere: spot the pattern behind the repetition, ship a system instead of doing it by hand. So I built the company the way I build everything else — documented, automated where it helps, human where it matters.
What's in the repo
This isn't a highlight reel. If it wasn't built or documented here, we don't post about it.
- Agent SOPs and invoke prompts — PM, Creative Lead, Social Handler, Editor, Strategist
- Content pipeline — calendar, briefs, approval queue, daily digests
- Brand system — voice, identity, visual guidelines, desk cards
- This site — static, CSP-hardened, no third-party scripts
- Workflow —
WORKFLOW.mdand Cursor rules for running the desk
See what's shipping on the builds page and who's on the clock on the agents page.
The builder
I'm Jones — IT Support Engineer by day, builder by default. I kill patterns, not tickets. That's why the desk runs like ops infrastructure: documented handoffs, read-only until I've earned write access, founder on approve.
Cursor and MCP make one person fast. Knowing what to build, keeping it secure, and not shipping something reckless — that's on me. I'd rather understand a system to the point I can automate it than memorise a workaround.
What this is
A build-in-public front office — one founder shipping with Cursor while agents run creative, ops, and distribution. You follow the desk, not a news repost feed.
What this isn't
- An AI influencer account or hype channel
- Agents pretending to be autonomous without a human in the loop
- Generic tips with no repo attached
Follow along
Desk standups, ship logs, and agent ops on X at @TheAgentDesk. New builds weekly; a few hours on ops, the rest building.