M A N G O M A G I C · 7 . 1
Less setup.
More doing.
The business AI system for the modern worker.
Mac · Restarts ChatGPT · Sign-in may be needed.
Your next move.
All tools ↗One click copies your next move.
Commands & prompts
Copy a command into Terminal. Copy a prompt into your connected project chat.
Step-by-step guide ↗ · Assistant guide ↗ · Read setup script ↗
Full setup.
bash -c 'f=$(mktemp) || exit; trap "rm -f \"$f\"" EXIT; curl -fsSL https://raw.githubusercontent.com/mango-magic/mangomagic/main/setup-operations.sh -o "$f" && bash "$f" --with-mangomagic'
Folders only.
bash -c 'f=$(mktemp) || exit; trap "rm -f \"$f\"" EXIT; curl -fsSL https://raw.githubusercontent.com/mango-magic/mangomagic/main/setup-operations.sh -o "$f" && bash "$f"'
Model only.
bash -c 'f=$(mktemp) || exit; trap "rm -f \"$f\"" EXIT; curl -fsSL https://raw.githubusercontent.com/mango-magic/mangomagic/main/install.sh -o "$f" && bash "$f"'
Fix missing model.
Refreshes MangoMagic, reconnects it and restarts the app. Your workspace stays in place.
bash -c 'f=$(mktemp) || exit; trap "rm -f \"$f\"" EXIT; curl -fsSL "https://raw.githubusercontent.com/mango-magic/mangomagic/main/install.sh?v=20260914-repair2" -o "$f" && bash "$f"'
Build my assistant.
Build an actually useful assistant for me in this AI Operations workspace. Read START_HERE.md, AGENTS.md and 00_Command_Centre/BUILD_MY_ASSISTANT.md. First verify that you can read the files; if access is missing, say exactly what is missing. Use the context and permissions I have already given you. Ask only for material gaps, up to five concise questions together, and follow my preferred pace. Learn from real tasks and examples of my writing. Adapt your communication to my preferences without mentioning personality types. Follow the playbook to build my profile, specific task register and reusable assistant instructions. Mark facts, assumptions and gaps honestly. Preserve existing work, update project_tasks.json, and produce one useful first deliverable with checks. Prepare three practical tasks for week one and the rollout audit. Account connections, external actions and schedules need their actual tools and my authorisation; never report them active just because files exist.
Brief my team.
Read AGENTS.md, CURRENT_MISSION.md and project_tasks.json. Deliver [specific outcome] in 03_Projects/[project]. Use [source files] and meet [acceptance criteria] by [deadline]. If supported, delegate independent parts to up to three relevant specialists. Give each a role file to read, exact inputs, a separate output path, file scope and a definition of done. Use fewer agents when practical. If delegation is unavailable, work sequentially and say so. Integrate the work, verify it against the evidence, update the tracker and return the deliverable with any remaining decisions. Continue authorised work without unnecessary check-ins.
Draft a document.
Read AGENTS.md, CURRENT_MISSION.md, the business brief and my assistant profile. Draft the document needed for my current task using the relevant source files and my working preferences. If the document or audience is unclear, ask one concise question. Use verified facts, show material assumptions and keep the result useful to its reader. Check figures, dates and links. Save the draft in the relevant project folder without overwriting existing work, then update project_tasks.json with its path and checks. Keep external delivery within my actual authorisation.
Research.
Research [decision] for [audience] using [approved documents and research scope]. Verify time-sensitive facts with primary sources when research tools are available. Record source dates and links. Separate facts, inference and unknowns; include conflicting evidence and what could change the answer. Save a one-page decision brief with options, recommendation, key risks and next action in 03_Projects/[project]. Check every material claim against its source. Update project_tasks.json and state any sources you could not access.
Plan automation.
Prepare a recurring [job] for this project. Cadence: [schedule]. Timezone: [Area/City]. Inputs: [specific accessible files or connected tools]. Output: [file and success check]. Read 04_Automations/AUTOMATION_BRIEF.md and fill a copy for this routine. Define duplicate prevention, retry limit, stop condition and usage budget. Notify only on a meaningful change, actionable failure or required decision. Run one bounded manual test and inspect its output. Keep this a draft until I ask to schedule it; a saved file is not a scheduled task. Then verify the saved app schedule, timezone, enabled status and input access before reporting it active. Do not send messages, publish or spend as part of this routine.
Check my work.
Review [deliverable path] against [task brief] and its cited sources. Check factual claims, calculations, links, missing requirements and whether the output is useful to its intended reader. Distinguish checks actually performed from checks still needed. Return pass, needs changes or blocked, with evidence and specific corrections. Fix routine issues within the authorised scope, recheck them and update project_tasks.json. Keep owner approval separate from technical completion. If this reviews your own work, disclose that the review is not independent.