What is read
README.md, AGENTS.md, CLAUDE.md and package.json, when present and under 40 KB each. Review the preview before importing.
Read the large text aloud. Follow the “On screen” line. Scroll to the next step.
Before starting: have your project folder ready and Codex signed in. For a quick demo, click Try the example in the project list (or Create example project on an empty workspace), then start at Step 4. Pause your recording while agents run.
“First, I open MissionMate, click Memory, and choose Projects. This is where I keep the brief, decisions and progress for each project.”
Click Memory → Projects.
Check: Look for “One project. Every agent in sync.”
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“I click Import a project, paste the path to my project folder, and click Preview import. I review the files it found before saving anything.”
Click Import a project → enter Project folder → Preview import.
Check: The preview shows which reference files will be included. The original files stay in place.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“Now I give the project a name, describe the result I want, and add the decisions we have already made. Then I click Import & save project.”
Fill in Project name, What should this project achieve?, and Decisions and constraints already agreed. Click Import & save project.
Check: Your project appears in the list with Revision 1.
Name: Enquiry tracker
Goal: Add enquiries, filter by stage, and export CSV.
Constraints: Keep data local. No sign-in or cloud sync.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“I check that Obsidian is configured. Then I open Project folder & Obsidian setup and click Sync latest revision to Obsidian. I open the new revision note in my vault.”
Expand Project folder & Obsidian setup → Sync latest revision to Obsidian. In Obsidian, open 02 Projects → Agent OS Projects → the project ID → the latest Revision note.
Check: The note contains your goal and constraints. If a sync error appears, resolve it before relying on vault copies.
Vault not configured? Open the Obsidian setup instructions. Add your vault path to the existing MissionMate configuration and restart MissionMate.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“Next, I bring over the important decisions from Claude or ChatGPT. I choose Agreed decision, paste the decision and its reason, and click Save to shared memory.”
Under Decide once. Carry it forward., choose Agreed decision → enter your decision → Save to shared memory.
Check: A new decision appears in the timeline. New decisions clear any previously accepted plan.
Keep the first version local. Use localStorage and CSV export. Do not add cloud sync or sign-in until we have tested the basic workflow.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“Now I choose Architect. I ask for the next small, testable step, then click Run architect. The agent reads the project context and returns a proposal in the timeline.”
Choose Architect → enter your task → Run architect. Wait for the proposal.
Check: The architect proposes a plan without editing your project files.
Read this project and the agreed decisions. Propose the next small, testable step. Include the files to change and the checks that will prove it works.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“I read the proposal before building. If it matches the goal and our decisions, I click Accept this plan. If it needs changes, I ask the architect for a revised proposal.”
Find the proposal in The project timeline → review it → Accept this plan.
Check: The proposal displays Accepted plan, and the developer becomes available.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“I choose Developer, explain what to implement, and click Run developer. It receives the accepted plan and shared context. Its result is saved back into the same project timeline.”
Choose Developer → check the Task → Run developer.
Check: The developer can edit this project folder. Read the result and check which files changed.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“Then I choose Reviewer and click Run reviewer. I read its findings, open the app, and test the change myself. I save the actual results as a checkpoint.”
Choose Reviewer → Run reviewer. Test the app. Then choose Checkpoint / external agent result → record what passed or failed → Save to shared memory.
Check: You have a review and a checkpoint. If something failed, give the developer the specific error and verify the fix.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
“When I stay inside MissionMate, the next run gets the saved context automatically. If I switch to Claude Desktop or ChatGPT, I download Handoff, attach it there, and save the useful reply back as a checkpoint.”
Click Handoff → attach PROJECT-HANDOFF.md in your external chat → save its useful reply as Checkpoint / external agent result.
Check: Download a fresh handoff whenever the project changes. External chats do not sync automatically.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
Your project gets one shared record. Each agent starts with the goal, constraints, accepted plan and saved history.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
Import a folder, record what is already agreed, run the architect, accept a plan, then build and review.
Open Memory → Projects → Import a project. Paste the local folder path and click Preview import.
README.md, AGENTS.md, CLAUDE.md and package.json, when present and under 40 KB each. Review the preview before importing.
A clear goal and the decisions already agreed in your chats. Import does not move or change the original project files.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
Working only in Claude Desktop or ChatGPT? Download your project files to a local folder first. Paste the important decisions into the import form. Chat histories are not discovered automatically.
MissionMate uses its configured vault. Each project revision becomes a new Markdown note, so old decisions and results remain available.
~/.agentic-os/config.json. Add "vaultRoot": "/absolute/path/to/your/vault" alongside existing settings. Keep the rest of the file.02 Projects/Agent OS Projects/<project-id>/.The configured indicator confirms the path exists. A successful save or sync confirms the note was written. A sync error leaves the local project revision intact.
Record the decision, its reason, and what evidence supports it. Save useful desktop replies as checkpoints instead of copying whole chats.
Keep the first version local. Use localStorage and CSV export. Do not add cloud sync or sign-in. Reason: validate the workflow before adding infrastructure.
A new decision clears the accepted plan. Run the architect again before development. This prevents reusing an old plan after the project changes.
Choose Architect and state the next small outcome. Read the proposal in the timeline and click Accept this plan.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
The architect uses read-only access. It cannot accept its own plan. A proposal based on an older revision cannot be accepted after new project changes.
Choose Developer after accepting a plan. Its result appears automatically in the same timeline. Then choose Reviewer to inspect the implementation.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
Can edit files in the imported project. Receives the agreed plan and current memory. Review changes before committing or publishing.
Uses read-only access. Ask it to check concrete files against the acceptance criteria. A generated summary is not a substitute for running the app.
These in-app roles use your configured Codex CLI account. A failed sign-in, timeout or empty response is recorded as a failure, not a completed build. Allow up to 10 minutes per run.
Download Handoff and attach the Markdown file to the other tool. Save the useful result back here as a checkpoint before switching again.
Follow these written steps in your own running MissionMate. Owner recordings are not included in the member installer.
Read PROJECT-HANDOFF.md before starting. Follow the goal, constraints and accepted decisions. If files or instructions disagree, explain the conflict before changing scope. End with changed files, checks actually run, unresolved issues and the next step.
This does not synchronise external chat accounts or permanently configure their memory. Download a fresh handoff when the project changes. In-app runs receive the latest context automatically.
Start with the included fictional enquiry tracker. The same pattern works for existing apps, SEO projects and content systems.
The app below was produced by the in-app architect → developer workflow. Browser checks covered entry validation, persistence, filtering and CSV export.
Goal: add enquiries, filter stages and export CSV. Decision: keep data local. Evidence: add an enquiry, reload, filter and inspect the export.
Example briefs are suggestions. The included enquiry tracker is clearly marked as a fictional demo; no customer data is needed.
Shared memory reduces repeated explanations. It does not guarantee that an AI will follow every instruction or make correct claims.
Start every new session from the latest handoff. Use checkpoints for verified progress and outstanding work.
Record a clear decision. Accept the revised plan before the next developer run. Inspect the code diff and test results.
Record the actual error as a checkpoint. Ask the reviewer for file-level evidence. Run the failing path again.
The task remains saved and is marked interrupted. Inspect the folder for partial changes before retrying.