Define the KPI
Choose the trusted measure, baseline, target, direction, source of truth, deadline, and owner.
Put a measurable outcome on autopilot.
Give an autonomous workflow a KPI, target, source of truth, cadence, and action boundary.
Missions live in the Moxby browser extension, evaluate performance across every run, and use the evidence to improve the workflow over time. When approved work needs operating-system access, the Desktop Bridge can extend execution to the rest of your computer.
Autonomy becomes useful when the workflow measures the result, learns from evidence, and improves the next run.
A Mission keeps its goal, plan, runs, KPI readings, evidence, failures, and learnings together. It can act through the browser, use approved computer capabilities through the Desktop Bridge, and keep consequential actions inside explicit review boundaries.
Define success, run the loop, learn from evidence.
Set the operating boundary
Choose the browser tools, skills, schedule, approvals, and Desktop Bridge capabilities the Mission may use.
Run and improve
Track each run, measure the result, detect drift, and let the Mission preserve what worked or trial a bounded alternative.
A browser-native control plane for outcome-driven work.
Missions stay close to the websites where the work happens while preserving the measurement and recovery information an autonomous loop needs.
KPI ownership
Keep the target and latest measurement visible instead of calling a workflow successful because its steps completed.
Browser execution
Research, navigate, operate web applications, and use installed Mods without moving the workflow into a separate automation dashboard.
Full computer use
Use the Desktop Bridge when the Mission needs local files, desktop applications, operating-system capabilities, or a longer-running native process.
Schedules and triggers
Run on a cadence, respond to supported events, or start manually when a human decides the conditions are right.
Evidence and recovery
Record what happened, why the KPI moved, where the run failed, and the next safe recovery action.
Self-evolving plans
On eligible plans, let a Mission improve its skills and operating plan from measured results while preserving visible change history.
Keep the autonomous loop in the browser.
A Mission can work across research, CRM, analytics, publishing, operations, and other browser workflows without requiring a desktop application to be the primary product surface.
- Use the signed-in web apps you already operate
- Combine Mods with Missions
- Keep permissions and approvals visible
Reach the full computer when the job requires it.
The Desktop Bridge is a companion, not the main Moxby interface. It securely extends a Mission to approved local and operating-system capabilities that a browser extension cannot provide alone.
- Local file and application access
- ChatGPT and Claude authentication bridge
- Native computer-use capabilities
Strong first Missions have a clear scoreboard.
Pipeline hygiene
Monitor a trusted CRM measure, research incomplete records, prepare fixes, and report the measurable change.
Content performance
Connect published content and analytics, identify the next evidence-backed update, and measure what improved.
Operational quality
Watch a recurring browser workflow for exceptions, prepare or execute the approved remedy, and track resolution rate.
Marketplace operations
Monitor listing quality, discover gaps, prepare updates, and keep the outcome tied to the relevant KPI.
Build it where it will run.
Moxby Chat can create and evolve Mods and Missions inside the browser, with the live page and working context close at hand.
Browser-native by default
The extension is the primary Moxby experience. Features run in or beside the web applications where you already work.
Desktop Bridge when needed
Use the companion Bridge for supported subscription authentication and approved capabilities that cannot live inside the browser sandbox.
Context that restores
Token Condenser and workflow restoration help the model recover relevant state with less repeated token weight.
Questions, answered.
Product details for using Missions through the Moxby browser extension.
Does a Mission require the Desktop Bridge?
No. Browser-only Missions can run through the extension. The Desktop Bridge is used when a Mission needs approved capabilities beyond the browser sandbox.
Can a Mission act without review?
You choose the action boundary. Research and internal preparation can run autonomously while external messages, publishing, purchases, and other consequential actions remain staged for approval.
Can I build my own Mission?
Yes. Describe the outcome in Moxby Chat or use the Mission Planner, then refine the KPI, tools, cadence, and safeguards before activation.
How does a Mission improve?
Moxby keeps run evidence and KPI readings together so eligible self-evolving Missions can compare approaches and preserve the better operating plan.
Make Missions part of your browser.
Install Moxby once, then build or add the capability you need from the Marketplace.
Four connected ways to work in your browser.
Chat on any page, build Mods, run Missions, and add ready-made products from the Marketplace.