Help & guides

Most "how do I…" answers are the same: just ask the system in chat - it handles the technical bits for you.

"It won't let me start a campaign."

That's on purpose. A campaign is built on your business foundation, so the foundation has to exist first. The system tells you what's still missing - finish answering its "Onboard" questions and approve your brand profile, and it opens up.

"Setup said something failed (a red line)."

Type "set yourself up" again - it retries and tells you, in plain words, the one thing to fix. The most common cause is Python installed without the "Add to PATH" box ticked; re-run that installer and tick it. Note that only red [FAIL] lines are real blockers - yellow [WARN] lines (like a missing thumbnail tool or Git) are optional and safe to ignore.

"I'm on a Mac (or Linux) - is there anything extra?"

One thing to know: the system's behind‑the‑scenes engine calls the command python, and many Macs and Linux machines only have python3. If that's you, the auto‑update and backup won't run. You don't have to sort this out in advance - "set yourself up" checks for it and, if it's missing, prints the exact one‑line fix (usually pointing python at python3, or using a virtual environment). Windows users don't need to worry about this.

"Do I need Git installed?"

No - Git is recommended, not required. Without it the studio runs perfectly and your OneDrive/Dropbox folder is your backup. With it, the system also keeps a full version history of your work and can push to an online backup. The setup check flags a missing Git as a yellow "recommended" note, never a blocker - install it if you want the version history, skip it if you don't.

"Do I work in the terminal, or in chat?"

Chat. The terminal was only for the one-time install. Day to day, you just talk to the system and review the web pages it makes.

"How do I add to my Best-Practice Library?"

Paste a link or a reference into chat and say "add this to my Best-Practice Library" (or "add to my marketing library"). The studio writes the full entry - what it is, why it works, how to reuse it - and files it into your Best-Practice Library: the collection of standout campaigns it draws on when creating your work. It only grows when you add to it - but once a week the studio suggests fresh examples worth adding and nudges you if it's gone stale, so you don't have to remember.

"How do I add to my Insights (research) Library?"

Your Insights Library is the separate research corpus - market data and behavioural science. It fills automatically as the studio researches your campaigns. To add a source yourself, paste its link and say "add this to my Insights Library" - the studio writes a short, cited summary and files it. (Both libraries live in the top-right menu.)

"How do I publish something it made?"

For tools it's connected to (like your email), it can send it for you once you say go. For everything else it gives you simple "paste this here" steps. You always do the final send.

"Can I change how it behaves?"

Yes - tell it in chat ("always do X", "never say Y"), or update your brand profile by saying "update my brand." For bigger changes under the hood, ask whoever maintains your system.

"Should I do everything in one long chat?"

No - start a fresh chat for each campaign, and another for each system retro. The system keeps your work in its files, so a new chat always picks up where you left off; separate chats keep the AI focused.

"Something annoys me, or I have an idea - can I improve it?"

Yes - that's the built-in System Manager. In a fresh chat, say "system idea: …" to file one, or "run a system retro" to turn lessons into a prioritised to-do list. Over time this is how the system gets better at your business.

"Where does my work go? Is anything shared?"

Everything stays as files on your computer. The only thing sent out is what you type to the system during a session - that's how the AI works. Passwords and keys are stored separately, never inside your files.

"How is my work backed up?"

Automatically - it saves at the end of every session. Keeping your folder in OneDrive or Dropbox adds an offsite copy. To connect an online backup (like GitHub), just say "set yourself up" again.

"Can my whole team use it at once?"

Right now it's built for one main person. Others can freely read the web pages it produces, but two people can't actively run it at the same time yet - that's on the way.

"Is this for a small business or a big company?"

Both. A setting adjusts how much structure it puts in front of you. Start simple; it scales up when you need it.

"Is there a map of everything - how do I find my way around?"

Yes. Open docs/NAVIGATION_INDEX.html in your system folder - it's the system's own index: every part of the system, what it's for, and where it lives (the agents, the phases, the specs, the playbooks, the operator screens). Whenever you wonder "where is X?", start there. The deepest reference is the operating manual, docs/workflow.md.