Choose one front door
Create one Main Agent for ideas, questions, voice notes, and anything you cannot place.
“If I am unsure where work belongs, route it for me.”
Build your own
Start with one doorway.
Add structure only when it earns its place.
You do not need a complicated dashboard. You need a front door, a clear owner for each project, three durable records, and a rule for approval.
Make a small WorkOS folder
Keep operating rules, project routing, and durable memory in a local folder the desktop task can read.
This is the operating record—not a pile of finished files.
Create one master command
Its job is to identify the owner, hand off the request, and bring the checked result back.
It coordinates. It does not silently control every other task.
Give each project a command pack
One local command pack owns one durable area such as growth, operations, social, or a product.
Ask: “Who owns this kind of work?”
Give every project three records
WORK says what belongs. PROJECT_MEMORY says the current state and exact next action. SOURCES says what evidence is trusted.
Keep changing status in PROJECT_MEMORY only.
Use focused specialists
Send bounded jobs to research, writing, design, coding, QA, scheduling, or another connected service.
Lighter models may gather or format. Stop at ambiguity or approval.
Require receipts and approval
Every job ends READY, BLOCKED, or VERIFIED. Public, paid, destructive, or irreversible actions wait for you.
Connect live services after this manual loop works.
A working shortcut
Let Codex build the structure with you.
The reusable skill checks your real setup first, labels anything it cannot verify, and stops before public or destructive actions.
Inside each project
Keep the folder boring and dependable.
Project name├── AGENTS.md├── 00 - Command├── WORK.md├── PROJECT_MEMORY.md└── SOURCES.md├── Current Work└── 99 Archive
What belongs here—and what does not.
Current truth, decisions, blockers, and exact next action.
Trusted documents, links, records, and verification evidence.
What moves by itself?
These rules prevent most confusion.
Account-owned content
Cloud chats and Drive files appear on signed-in devices that have access.
Local files
WorkOS files and unpushed code stay on the computer that holds them.
GitHub code
Push committed code to share it. Another computer must fetch or pull it.
Separate tasks
A cloud task cannot silently edit your local WorkOS. Give the master a clear update packet.
Connected services
Gmail, Calendar, Drive, and other services are read or changed only when asked and authorized.
Your first message
Say this in your Main Agent.
“Help me decide where this belongs. Read the owning project’s rules and memory first. Do not publish, send, buy, delete, or change anything live without my approval. Return READY, BLOCKED, or VERIFIED and tell me exactly what I need to do next.”
See it working