MC
Mid Conversation Keep ticket context, project history, and release state in view
theme mission control dark release v3.24 build 32 MCP tools View downloads
For teams tired of AI losing the thread

The control surface for serious AI work.

Mid Conversation keeps ticket context, project history, and release state in one signed desktop surface so your team can inspect the work, recover a handoff fast, and ship without losing the thread.

  • See the ticket, changed files, and activity trail behind AI work.
  • Keep tracked files and handoff history visible across sessions.
  • Run, verify, and distribute from the same release-aware surface.
View downloads See product proof MCP tools

The page is public. Signed desktop builds and the full release archive are behind approved access.

Open At A Glance ticket + project + release
Ticket Surface See the brief, files, and activity trail Review the work instead of a vague summary.
Project Memory See tracked files and handoff history Start from context, not reconstruction.
Launch + Release See health, sync state, and build access Check the release before you run it.
Product Proof

See the product before the copy starts explaining it

One main surface. Three supporting views. All from the current product.

Mid Conversation ticket overview showing description, owner, progress summary, and activity signals
Live Ticket Surface
The work stays legible after the first prompt

One ticket keeps the brief, owner, progress, and recent activity in view.

  • Brief
  • Progress
  • Activity
  • File count
Mid Conversation ticket directives tab showing numbered directives, priorities, owners, and statuses
Plan View
Directives stay readable
Mid Conversation project sessions tab showing session counts, activity totals, and historical operator sessions
Session View
Handoffs stay visible
Mid Conversation project sync tab showing tracked, mirrored, pending, and missing files
Sync View
Mirror state stays obvious
These are real current Mid Conversation surfaces. They are product proof, not decorative filler.
What Stays In View

Three things the product keeps in the open

The product is built to keep the work legible, the handoff survivable, and the release deliberate.

Tickets
See the work before you trust it

Open one ticket and see the plan, files, and activity trail in one view.

  • Review progress without hunting across tabs.
  • Check changed files before approval.
  • Spot drift early when the work starts moving off course.
Projects
Keep handoffs from going cold

See tracked files, recent sessions, and the project story before you touch the repo.

  • Keep tracked files and recent history in view.
  • Carry session context across operators.
  • Rebuild the project story without guesswork.
Launcher
Run and ship from the same surface

Start the stack, check health, sync the right files, and distribute signed builds without side rituals.

  • Check health before you trust the environment.
  • Sync the right files before a handoff.
  • Keep release distribution controlled and deliberate.
MCP Tooling

Mission Control MCP tools and what they do

These are the current tools in the Mission Control MCP server used by both Codex and Visual Studio Copilot integrations.

Tool Primary purpose Typical usage
ticket_create Create SQL tickets with initial directives, tags, and project linkage. Intake new work and bootstrap ticket metadata in one call.
ticket_get Load canonical ticket detail, directives, files, and bootstrap payload. Hydrate an AI session with trusted ticket context.
ticket_validate_handoff Check required handoff sections and directive hygiene. Gate completion before pause/close to reduce context drift.
ticket_sync Run markdown-to-database sync via canonical ticket sync pipeline. Apply ticket markdown edits and keep DB state aligned.
ticket_regen_brief Regenerate the ticket AI brief/development story snapshot. Refresh bootstrap context after substantive ticket updates.
ticket_repo_state Capture git branch/head/dirty-state details for commit discipline. Preflight pause/close actions and audit repository status.
echo_guidance_get Return effective Echo Guidance profile used by Mission Control. Ensure AI tooling follows the same operator preferences.
Need integration specifics for Codex and VS Copilot? Open the MCP tools reference page.
Why Trust It

Visibility without loose access

You should be able to inspect the work without turning build access loose.

Visibility
Inspect the change trail before you say yes

See what changed, what still looks risky, and what is ready to hand off.

Control
Keep the story public and the build controlled

The page is public on purpose, while current and archived signed builds stay behind approved access.

Public explanation outside. Controlled build access inside.
Best Fit

Who feels this problem first

This is for teams already feeling the cost of AI drift in real work.

Teams tired of paying the tax for repeated AI drift

You keep re-explaining settled context, reopening solved issues, or cleaning up after handoffs that should have been easier.

Operators responsible for launch quality

You need to inspect the work and the release state before a build moves forward.

Builders shipping with AI in the loop

You want AI speed without turning project memory and release control into side rituals the team cannot inspect.

Next Step

See the product. Request approved access when you need the build.

Signed desktop builds stay behind approved access to current and archived releases. The product story stays public.

View downloads & release archive