[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74808":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":30,"readmeContent":31,"aiSummary":32,"trendingCount":16,"starSnapshotCount":16,"syncStatus":33,"lastSyncTime":34,"discoverSource":35},74808,"openclaw-mission-control","abhi1693\u002Fopenclaw-mission-control","abhi1693","AI Agent Orchestration Dashboard - Manage AI agents, assign tasks, and coordinate multi-agent collaboration via OpenClaw Gateway.","",null,"TypeScript",4039,830,37,46,0,20,32,92,60,30.76,"MIT License",false,"master",[26,27,28,29],"ai-agents","automation","openclaw","orchestration","2026-06-12 02:03:28","# OpenClaw Mission Control\n\n[![CI](https:\u002F\u002Fgithub.com\u002Fabhi1693\u002Fopenclaw-mission-control\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fabhi1693\u002Fopenclaw-mission-control\u002Factions\u002Fworkflows\u002Fci.yml) ![Static Badge](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FJoin-Slack-active?style=flat&color=blue&link=https%3A%2F%2Fjoin.slack.com%2Ft%2Foc-mission-control%2Fshared_invite%2Fzt-3qpcm57xh-AI9C~smc3MDBVzEhvwf7gg)\n\nOpenClaw Mission Control is the centralized operations and governance platform for running OpenClaw across teams and organizations, with unified visibility, approval controls, and gateway-aware orchestration.\nIt gives operators a single interface for work orchestration, agent and gateway management, approval-driven governance, and API-backed automation.\n\n\u003Cimg width=\"1896\" height=\"869\" alt=\"Mission Control dashboard\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F49a3c823-6aaf-4c56-8328-fb1485ee940f\" \u002F>\n\u003Cimg width=\"1896\" height=\"858\" alt=\"image\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F2bfee13a-3dab-4f4a-9135-e47bb6949dcf\" \u002F>\n\u003Cimg width=\"1890\" height=\"865\" alt=\"image\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F84c2e867-5dc7-4a36-9290-e29179d2a659\" \u002F>\n\u003Cimg width=\"1912\" height=\"881\" alt=\"image\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F3bbd825c-9969-4bbf-bf31-987f9168f370\" \u002F>\n\u003Cimg width=\"1902\" height=\"878\" alt=\"image\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002Feea09632-60e4-4d6d-9e6e-bdfa0ac97630\" \u002F>\n\n## Platform overview\n\nMission Control is designed to be the day-to-day operations surface for OpenClaw.\nInstead of splitting work across multiple tools, teams can plan, execute, review, and audit activity in one system.\n\nCore operational areas:\n\n- Work orchestration: manage organizations, board groups, boards, tasks, and tags.\n- Agent operations: create, inspect, and manage agent lifecycle from a unified control surface.\n- Governance and approvals: route sensitive actions through explicit approval flows.\n- Gateway management: connect and operate gateway integrations for distributed environments.\n- Activity visibility: review a timeline of system actions for faster debugging and accountability.\n- API-first model: support both web workflows and automation clients from the same platform.\n\n## Use cases\n\n- Multi-team agent operations: run multiple boards and board groups across organizations from a single control plane.\n- Human-in-the-loop execution: require approvals before sensitive actions and keep decision trails attached to work.\n- Distributed runtime control: connect gateways and operate remote execution environments without changing operator workflow.\n- Audit and incident review: use activity history to reconstruct what happened, when it happened, and who initiated it.\n- API-backed process integration: connect internal workflows and automation clients to the same operational model used in the UI.\n\n## What makes Mission Control different\n\n- Operations-first design: built for running agent work reliably, not just creating tasks.\n- Governance built in: approvals, auth modes, and clear control boundaries are first-class.\n- Gateway-aware orchestration: built to operate both local and connected runtime environments.\n- Unified UI and API model: operators and automation act on the same objects and lifecycle.\n- Team-scale structure: organizations, board groups, boards, tasks, tags, and users in one system of record.\n\n## Who it is for\n\n- Platform teams running OpenClaw in self-hosted or internal environments.\n- Operations and engineering teams that need clear approval and auditability controls.\n- Organizations that want API-accessible operations without losing a usable web UI.\n\n## Get started in minutes\n\n### Option A: One-command production-style bootstrap\n\nIf you haven't cloned the repo yet, you can run the installer in one line:\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fabhi1693\u002Fopenclaw-mission-control\u002Fmaster\u002Finstall.sh | bash\n```\n\nThis clones the repository into `.\u002Fopenclaw-mission-control` if no local checkout is found in your current directory.\n\nIf you already cloned the repo:\n\n```bash\n.\u002Finstall.sh\n```\n\nThe installer is interactive and will:\n\n- Ask for deployment mode (`docker` or `local`).\n- Install missing system dependencies when possible.\n- Generate and configure environment files.\n- Bootstrap and start the selected deployment mode.\n\nInstaller support matrix: [`docs\u002Finstaller-support.md`](.\u002Fdocs\u002Finstaller-support.md)\n\n### Option B: Manual setup\n\n### Prerequisites\n\n- **Supported platforms**: Linux and macOS. On macOS, Docker mode requires [Docker Desktop](https:\u002F\u002Fwww.docker.com\u002Fproducts\u002Fdocker-desktop\u002F); local mode requires [Homebrew](https:\u002F\u002Fbrew.sh) and Node.js 22+.\n- Docker Engine\n- Docker Compose v2 (`docker compose`)\n\n### 1. Configure environment\n\n```bash\ncp .env.example .env\n```\n\nBefore startup:\n\n- Set `LOCAL_AUTH_TOKEN` to a non-placeholder value (minimum 50 characters) when `AUTH_MODE=local`.\n- Ensure `BASE_URL` matches the public backend origin if you are not using `http:\u002F\u002Flocalhost:8000`.\n- `NEXT_PUBLIC_API_URL=auto` (default) resolves to `http(s):\u002F\u002F\u003Ccurrent-host>:8000`.\n  - Set an explicit URL when your API is behind a reverse proxy or non-default port.\n\n### 2. Start Mission Control\n\n```bash\ndocker compose -f compose.yml --env-file .env up -d --build\n```\n\nIf you are iterating on the UI in Docker and want automatic frontend rebuilds on\nsource changes, run:\n\n```bash\ndocker compose -f compose.yml --env-file .env up --build --watch\n```\n\nNotes:\n\n- Compose Watch requires Docker Compose **2.22.0+**.\n- You can also run watch separately after startup:\n\n```bash\ndocker compose -f compose.yml --env-file .env up -d --build\ndocker compose -f compose.yml --env-file .env watch\n```\n\nAfter pulling new changes, rebuild and recreate all services:\n\n```bash\ndocker compose -f compose.yml --env-file .env up -d --build --force-recreate\n```\n\nFor a fully clean rebuild (no cached build layers):\n\n```bash\ndocker compose -f compose.yml --env-file .env build --no-cache --pull\ndocker compose -f compose.yml --env-file .env up -d --force-recreate\n```\n\n### 3. Open the application\n\n- Mission Control UI: http:\u002F\u002Flocalhost:3000\n- Backend health: http:\u002F\u002Flocalhost:8000\u002Fhealthz\n\n### 4. Stop the stack\n\n```bash\ndocker compose -f compose.yml --env-file .env down\n```\n\n## Authentication\n\nMission Control supports two authentication modes:\n\n- `local`: shared bearer token mode (default for self-hosted use)\n- `clerk`: Clerk JWT mode\n\nEnvironment templates:\n\n- Root: [`.env.example`](.\u002F.env.example)\n- Backend: [`backend\u002F.env.example`](.\u002Fbackend\u002F.env.example)\n- Frontend: [`frontend\u002F.env.example`](.\u002Ffrontend\u002F.env.example)\n\n## Documentation\n\nComplete guides for deployment, production, troubleshooting, and testing are in [`\u002Fdocs`](.\u002Fdocs\u002F).\n\n## Project status\n\nMission Control is under active development.\n\n- Features and APIs may change between releases.\n- Validate and harden your configuration before production use.\n\n## Contributing\n\nIssues and pull requests are welcome.\n\n- [Contributing guide](.\u002FCONTRIBUTING.md)\n- [Open issues](https:\u002F\u002Fgithub.com\u002Fabhi1693\u002Fopenclaw-mission-control\u002Fissues)\n\n## License\n\nThis project is licensed under the MIT License. See [`LICENSE`](.\u002FLICENSE).\n\n## Star History\n\n[![Star History Chart](https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=abhi1693\u002Fopenclaw-mission-control&type=date&legend=top-left)](https:\u002F\u002Fwww.star-history.com\u002F#abhi1693\u002Fopenclaw-mission-control&type=date&legend=top-left)\n","OpenClaw Mission Control 是一个AI代理编排仪表盘，用于管理和协调通过OpenClaw网关运行的AI代理任务。该项目采用TypeScript开发，核心功能包括统一的工作编排、代理和网关管理、基于审批的治理以及API支持的自动化。它提供了一个集中化的操作界面，使得团队可以在单一平台上规划、执行、审查和审计活动。适用于需要跨团队协作、人机交互执行、分布式环境控制以及流程集成等场景。",2,"2026-06-11 03:50:56","high_star"]