### Install Dependencies and Start Dev Server Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/frontend/README.md Installs project dependencies and starts the Next.js development server. Ensure to copy the example environment file and set necessary environment variables before running. ```bash npm install # set env vars (see below) cp .env.example .env.local npm run dev ``` -------------------------------- ### Run Frontend in Development Mode Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/development/README.md Change to the frontend directory, install dependencies, and start the development server using npm. Open your browser to the specified local address. ```bash cd frontend cp .env.example .env.local npm install npm run dev ``` -------------------------------- ### Fast Local Development Setup Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/AGENTS.md This sequence of commands sets up a fast local development environment by starting only the database, then running the backend and frontend services in separate terminals. ```bash docker compose -f compose.yml --env-file .env up -d db ``` ```bash cd backend && uv run uvicorn app.main:app --reload --port 8000 ``` ```bash cd frontend && npm run dev ``` -------------------------------- ### Install and Enable User Systemd Units Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/systemd/README.md Copy the generated service files to the user's systemd directory, reload the daemon, and enable/start the backend, frontend, and RQ worker services. User units start on user login; enable lingering for boot start. ```bash cp openclaw-mission-control-backend.service openclaw-mission-control-frontend.service openclaw-mission-control-rq-worker.service ~/.config/systemd/user/ systemctl --user daemon-reload systemctl --user enable openclaw-mission-control-backend openclaw-mission-control-frontend openclaw-mission-control-rq-worker systemctl --user start openclaw-mission-control-backend openclaw-mission-control-frontend openclaw-mission-control-rq-worker ``` -------------------------------- ### Install and Enable System-Wide Systemd Units Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/systemd/README.md Copy the generated service files to the system-wide systemd directory, reload the daemon, and enable/start the backend, frontend, and RQ worker services. These units start at machine boot. ```bash sudo cp openclaw-mission-control-*.service /etc/systemd/system/ sudo systemctl daemon-reload sudo systemctl enable --now openclaw-mission-control-backend openclaw-mission-control-frontend openclaw-mission-control-rq-worker ``` -------------------------------- ### Start Local Backend with Docker Postgres Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/README.md Use these commands to set up and run the backend API locally with a Dockerized PostgreSQL database. Ensure you have uv installed and a .env file configured. ```bash cp .env.example .env docker compose -f compose.yml --env-file .env up -d db cd backend cp .env.example .env uv sync --extra dev uv run uvicorn app.main:app --reload --host 0.0.0.0 --port 8000 ``` -------------------------------- ### Run the OpenClaw Mission Control installer from a cloned repository Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/README.md Execute this script from your local clone of the repository to start the interactive installation process. It will guide you through deployment mode selection, dependency installation, and environment setup. ```bash ./install.sh ``` -------------------------------- ### Install and Sync Dependencies Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/AGENTS.md Installs or synchronizes both backend and frontend project dependencies. ```bash make setup ``` -------------------------------- ### Install OpenClaw Mission Control with a single command Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/README.md Use this command to clone the repository and run the installer if you haven't cloned the repo yet. The installer is interactive and handles dependencies, environment configuration, and deployment. ```bash curl -fsSL https://raw.githubusercontent.com/abhi1693/openclaw-mission-control/master/install.sh | bash ``` -------------------------------- ### Start Dev Server for LAN Access Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/frontend/README.md Starts the Next.js development server, binding it to all network interfaces to allow access from other devices on the local network. ```bash npm run dev:lan ``` -------------------------------- ### Start Stack for E2E Tests (Terminal 1) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/testing/README.md In the first terminal, copy the environment file and start the Docker Compose stack with the specified environment file. This prepares the environment for end-to-end testing. ```bash # terminal 1 cp .env.example .env docker compose -f compose.yml --env-file .env up -d --build ``` -------------------------------- ### Start Postgres Database Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/development/README.md Use this command to start the PostgreSQL database in Docker. Ensure you are in the repository root and have a .env file configured. ```bash cp .env.example .env docker compose -f compose.yml --env-file .env up -d db ``` -------------------------------- ### Copy Environment File Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/getting-started/README.md Copies the example environment file to .env. This is a prerequisite for configuring your Mission Control instance. ```bash cp .env.example .env ``` -------------------------------- ### Run Setup and Checks (Repo Root) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/testing/README.md Execute these commands from the repository root to set up the environment and run comprehensive checks, including backend and frontend linting, type checking, and unit tests. ```bash make setup make check ``` -------------------------------- ### Start OpenClaw Gateway Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/openclaw_baseline_config.md Initiate the OpenClaw gateway service. Ensure the configuration file is saved correctly before running this command. ```bash openclaw gateway ``` -------------------------------- ### Configure Local Environment Variables Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/frontend/README.md Copies the example environment file to a local configuration file. This file should then be edited to set specific environment variables for local development. ```bash cp .env.example .env.local # then edit .env.local if your backend URL differs ``` -------------------------------- ### Start Mission Control with Docker Compose Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/getting-started/README.md Builds and starts the OpenClaw Mission Control services using Docker Compose. Ensure your .env file is correctly configured, especially LOCAL_AUTH_TOKEN if AUTH_MODE=local. ```bash docker compose -f compose.yml --env-file .env up -d --build ``` -------------------------------- ### Markdown Callout Example Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/style-guide.md Illustrates how to use markdown for notes and warnings within documentation. ```markdown > **Note** > ... ``` ```markdown > **Warning** > ... ``` -------------------------------- ### Start Mission Control and Then Enable Watch Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/README.md Starts Mission Control in detached mode and then separately enables the watch mode for development. This allows for initial startup and then enabling live reloading. ```bash docker compose -f compose.yml --env-file .env up -d --build docker compose -f compose.yml --env-file .env watch ``` -------------------------------- ### Run Backend Migration Check Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/03-development.md Execute this command from the repository root to start a temporary Postgres container, run migration checks, and clean up the container. ```bash make backend-migration-check ``` -------------------------------- ### Start Mission Control with Watch Mode Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/README.md Starts Mission Control services with automatic frontend rebuilds on source changes. Requires Docker Compose 2.22.0+. ```bash docker compose -f compose.yml --env-file .env up --build --watch ``` -------------------------------- ### Get Specific Board Details Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Retrieve details for a specific board. Requires agent token. ```bash curl -H "X-Agent-Token: $AGENT_TOKEN" \ http://localhost:8000/api/v1/agent/boards/BOARD_ID ``` -------------------------------- ### Get Agent SOUL Instructions Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Retrieve the SOUL (behavior instructions) for a specific agent on a board. Requires agent token. ```bash curl -H "X-Agent-Token: $AGENT_TOKEN" \ http://localhost:8000/api/v1/agent/boards/BOARD_ID/agents/AGENT_ID/soul ``` -------------------------------- ### Get Board Snapshot Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Retrieves the full state of a board, including tasks, agents, and memory entries, for agent use. Requires the board ID and authentication token. ```bash curl -H "Authorization: Bearer $AUTH_TOKEN" \ http://localhost:8000/api/v1/boards/BOARD_ID/snapshot ``` -------------------------------- ### Get Cross-Board Group Snapshot Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Fetches a snapshot of multiple boards for coordination purposes. Allows filtering and limiting tasks per board. Requires the board ID and authentication token. ```bash curl -H "Authorization: Bearer $AUTH_TOKEN" \ "http://localhost:8000/api/v1/boards/BOARD_ID/group-snapshot?include_self=true&include_done=false&per_board_task_limit=5" ``` -------------------------------- ### Health Check Example (curl) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/reference/api.md Example using curl to perform a health check. ```APIDOC ## Health Check Example ### Description This example demonstrates how to check the health of the Mission Control service using `curl`. ### Method GET ### Endpoint `http://localhost:8000/healthz` ### Request Example ```bash curl -f http://localhost:8000/healthz ``` ``` -------------------------------- ### Run Backend in Development Mode Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/development/README.md Navigate to the backend directory, set up the environment, and run the Uvicorn server for development. This command reloads the server on code changes. ```bash cd backend cp .env.example .env uv sync --extra dev uv run uvicorn app.main:app --reload --host 0.0.0.0 --port 8000 ``` -------------------------------- ### Load macOS LaunchAgent Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/README.md Load a configured LaunchAgent plist file into `launchd` for user-level startup. ```bash launchctl load ~/Library/LaunchAgents/com.openclaw.mission-control.backend.plist ``` -------------------------------- ### Create Task Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Adds a new task to a board. Specify title, description, status, and optionally assign agents or set dependencies. Requires board ID and authentication token. ```bash curl -X POST http://localhost:8000/api/v1/boards/BOARD_ID/tasks \ -H "Authorization: Bearer $AUTH_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "title": "Implement user authentication", "description": "Add JWT-based authentication flow", "status": "inbox", "assigned_agent_id": null, "depends_on_task_ids": [], "tag_ids": ["tag-uuid"], "custom_field_values": {"priority": "high"} }' ``` -------------------------------- ### Verify Backend Health Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/development/README.md Use curl to check if the backend health endpoint is responding correctly after starting the development server. ```bash curl -f http://localhost:8000/healthz ``` -------------------------------- ### Create Board Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Creates a new board to organize tasks and agents. Requires a name, gateway ID, and other optional details like objective and target date. ```bash curl -X POST http://localhost:8000/api/v1/boards \ -H "Authorization: Bearer $AUTH_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "Sprint Board", "gateway_id": "gateway-uuid", "board_type": "goal", "objective": "Complete Q1 feature development", "success_metrics": "All PRs merged and tests passing", "target_date": "2024-03-31", "require_approval_for_done": true, "require_review_before_done": true }' ``` -------------------------------- ### Verify Backend Health Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/README.md Checks the health status of the backend API. Use this command after starting the stack to ensure the backend is running correctly. ```bash curl -f "http://localhost:${BACKEND_PORT:-8000}/healthz" ``` -------------------------------- ### Get Board by ID Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Fetches a specific board's details using its unique identifier. Requires the board ID and authentication token. ```bash curl -H "Authorization: Bearer $AUTH_TOKEN" \ http://localhost:8000/api/v1/boards/BOARD_ID ``` -------------------------------- ### macOS LaunchAgent Plist for Backend Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/README.md Configure a LaunchAgent plist for the backend process. Ensure `REPO_ROOT` is replaced with the actual path and `uv` is in the system's PATH. ```xml Label com.openclaw.mission-control.backend ProgramArguments /usr/bin/env uv run uvicorn app.main:app --host 0.0.0.0 --port 8000 WorkingDirectory REPO_ROOT/backend EnvironmentVariables PATH /usr/local/bin:/opt/homebrew/bin:REPO_ROOT/backend/.venv/bin KeepAlive RunAtLoad ``` -------------------------------- ### Local Auth Backend Configuration Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/reference/authentication.md Configure the backend for local authentication by setting the AUTH_MODE to 'local' and providing a LOCAL_AUTH_TOKEN. ```bash AUTH_MODE=local LOCAL_AUTH_TOKEN= ``` -------------------------------- ### Environment Configuration - Core Settings Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Core environment variables for backend configuration, including environment mode, log level, database URL, CORS origins, and base URL. ```bash # Core settings ENVIRONMENT=dev # dev, staging, production LOG_LEVEL=INFO # DEBUG, INFO, WARNING, ERROR DATABASE_URL=postgresql+psycopg://postgres:postgres@localhost:5432/mission_control CORS_ORIGINS=http://localhost:3000 BASE_URL=http://localhost:8000 # Required for gateway provisioning ``` -------------------------------- ### Get Webhook Payload (Agent Read) Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Retrieves a specific webhook payload for agent consumption. Requires an agent token and the webhook and payload IDs. ```bash curl -H "X-Agent-Token: $AGENT_TOKEN" \ "http://localhost:8000/api/v1/agent/boards/BOARD_ID/webhooks/WEBHOOK_ID/payloads/PAYLOAD_ID?max_chars=10000" ``` -------------------------------- ### Run Frontend Tests (Frontend Directory) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/testing/README.md Execute frontend tests or run them in watch mode from the `frontend/` directory using npm. ```bash cd frontend npm run test npm run test:watch ``` -------------------------------- ### Set API Base URL Environment Variable Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/frontend/README.md Example of setting the NEXT_PUBLIC_API_URL environment variable in a .env.local file. This variable specifies the base URL for the backend API. ```env NEXT_PUBLIC_API_URL=auto ``` -------------------------------- ### Clerk Auth Backend Configuration Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/reference/authentication.md Configure the backend for Clerk authentication by setting AUTH_MODE to 'clerk' and providing the CLERK_SECRET_KEY. ```bash AUTH_MODE=clerk CLERK_SECRET_KEY= ``` -------------------------------- ### Useful Repository Root Commands Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/development/README.md Execute these commands from the repository root for common development tasks like dependency synchronization, linting, type checking, testing, and building. ```bash make help make setup make check ``` -------------------------------- ### Environment Configuration - Database Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Database-related environment variable for automatic migration execution. ```bash # Database DB_AUTO_MIGRATE=true # Auto-run Alembic migrations on startup ``` -------------------------------- ### Run Backend Linting and Formatting Checks Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/README.md Execute backend code quality checks, including formatting, linting, and type checking, using the provided make targets. These commands help maintain code consistency and quality. ```bash make backend-lint ``` -------------------------------- ### OpenClaw Baseline Configuration (JSON) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/openclaw_baseline_config.md This is the normalized JSON configuration for OpenClaw, serving as a baseline for local setup and Mission Control integration. It controls various aspects of the OpenClaw runtime, including environment, updates, agent defaults, messaging, commands, hooks, channels, gateway, memory, and skills. ```json { "env": { "shellEnv": { "enabled": true } }, "update": { "channel": "stable" }, "agents": { "defaults": { "model": { "primary": "", "fallbacks": [] }, "models": { "": {} }, "workspace": "/home/asaharan/.openclaw/workspace", "contextPruning": { "mode": "cache-ttl", "ttl": "45m", "keepLastAssistants": 2, "minPrunableToolChars": 12000, "tools": { "deny": [ "browser", "canvas" ] }, "softTrim": { "maxChars": 2500, "headChars": 900, "tailChars": 900 }, "hardClear": { "enabled": true, "placeholder": "[Old tool output cleared]" } }, "compaction": { "mode": "safeguard", "reserveTokensFloor": 12000, "memoryFlush": { "enabled": true, "softThresholdTokens": 5000, "prompt": "Write any lasting notes to memory/YYYY-MM-DD.md; reply with NO_REPLY if nothing to store.", "systemPrompt": "Session nearing compaction. Store durable memories now." } }, "thinkingDefault": "medium", "maxConcurrent": 5, "subagents": { "maxConcurrent": 5 } }, "list": [ { "id": "main" } ] }, "messages": { "ackReactionScope": "group-mentions" }, "commands": { "native": "auto", "nativeSkills": "auto" }, "hooks": { "internal": { "enabled": true, "entries": { "boot-md": { "enabled": true }, "command-logger": { "enabled": true }, "session-memory": { "enabled": true }, "bootstrap-extra-files": { "enabled": true } } } }, "channels": { "defaults": { "heartbeat": { "showOk": true, "showAlerts": true, "useIndicator": true } } }, "gateway": { "port": 18789, "mode": "local", "bind": "lan", "controlUi": { "allowInsecureAuth": true }, "auth": { "mode": "token" }, "trustedProxies": [ "127.0.0.1", "::1" ], "tailscale": { "mode": "off", "resetOnExit": false }, "reload": { "mode": "hot", "debounceMs": 750 }, "nodes": { "denyCommands": [ "camera.snap", "camera.clip", "screen.record", "calendar.add", "contacts.add", "reminders.add" ] } }, "memory": { "backend": "qmd", "citations": "auto", "qmd": { "includeDefaultMemory": true, "update": { "interval": "15m", "debounceMs": 15000, "onBoot": true }, "limits": { "maxResults": 3, "maxSnippetChars": 450, "maxInjectedChars": 1800, "timeoutMs": 8000 } } }, "skills": { "install": { "nodeManager": "npm" } } } ``` -------------------------------- ### Run E2E Tests (Terminal 2) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/testing/README.md In the second terminal, navigate to the `frontend/` directory and run the end-to-end tests using npm. ```bash # terminal 2 cd frontend npm run e2e ``` -------------------------------- ### Environment Configuration - Authentication Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Environment variables for authentication modes, including local token and Clerk integration. ```bash # Authentication AUTH_MODE=local # local or clerk LOCAL_AUTH_TOKEN=your-50-char-minimum-token # Required for local mode # Clerk (optional) CLERK_SECRET_KEY=sk_test_xxx CLERK_API_URL=https://api.clerk.com ``` -------------------------------- ### Clerk Auth Frontend Configuration Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/reference/authentication.md Configure the frontend for Clerk authentication by setting NEXT_PUBLIC_AUTH_MODE to 'clerk' and providing the NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY. ```bash NEXT_PUBLIC_AUTH_MODE=clerk NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY= ``` -------------------------------- ### Check Backend Code Formatting (Make) Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/README.md Use this make target to check if the backend code is correctly formatted without applying any changes. It's a convenient way to ensure compliance before committing. ```bash make backend-format-check ``` -------------------------------- ### Local Auth Frontend Configuration Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/reference/authentication.md Configure the frontend for local authentication by setting NEXT_PUBLIC_AUTH_MODE to 'local'. The token is provided via the login UI. ```bash NEXT_PUBLIC_AUTH_MODE=local ``` -------------------------------- ### Generate Systemd Unit Files Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/systemd/README.md Use this script to replace placeholders in the systemd unit files with your specific paths and ports. Ensure REPO_ROOT does not contain spaces. ```bash REPO_ROOT="$(pwd)" for f in docs/deployment/systemd/openclaw-mission-control-*.service; do sed -e "s|REPO_ROOT|$REPO_ROOT|g" -e "s|BACKEND_PORT|8000|g" -e "s|FRONTEND_PORT|3000|g" "$f" \ > "$(basename "$f")" done ``` -------------------------------- ### Open Cypress for Interactive E2E Testing Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/testing/README.md Launch Cypress in interactive mode from the `frontend/` directory to develop and debug end-to-end tests. ```bash cd frontend npm run e2e:open ``` -------------------------------- ### Pagination Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/reference/api.md Guidelines for implementing pagination in list endpoints. ```APIDOC ## Pagination ### Description List endpoints commonly support pagination. When implementing new list endpoints, adhere to the following conventions for parameters and response structure. ### Parameters - `limit`: The maximum number of items to return. - `offset`: The number of items to skip from the beginning. ### Response Structure - `items`: An array of items. - `total`: The total number of items available. - `limit`: The limit applied to the current request. - `offset`: The offset applied to the current request. ``` -------------------------------- ### Run Frontend Tests and Coverage Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/AGENTS.md Executes the frontend test suite using vitest and Testing Library. Coverage information is generated within the `frontend/coverage/` directory. ```bash make frontend-test ``` -------------------------------- ### Sync Gateway Templates with Token Rotation via CLI Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/troubleshooting/gateway-agent-provisioning.md Execute this Python script from the repository root to sync gateway templates and rotate agent tokens. Ensure you are in the 'backend' directory and provide the gateway ID and rotation flag. ```bash cd backend && uv run python scripts/sync_gateway_templates.py --gateway-id GATEWAY_ID --rotate-tokens ``` -------------------------------- ### Create OpenClaw Configuration Directory Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/openclaw_baseline_config.md Create the necessary directory structure for OpenClaw configuration files. This is a prerequisite for saving the configuration file. ```bash mkdir -p ~/.openclaw ``` -------------------------------- ### Ask User via Gateway Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Escalate a question to a human user through the gateway. This is a lead-only action and requires the lead agent's token. Includes the question and context. ```bash curl -X POST http://localhost:8000/api/v1/agent/boards/BOARD_ID/gateway/main/ask-user \ -H "X-Agent-Token: $LEAD_AGENT_TOKEN" \ -H "Content-Type: application/json" \ -d '{"question": "Should we proceed with the risky deployment?", "context": "Production database migration"}' ``` -------------------------------- ### Create Task on Board Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Create a new task on a specified board. This endpoint is restricted to lead agents and requires their token. Includes fields for title, description, status, assigned agent, and dependencies. ```bash curl -X POST http://localhost:8000/api/v1/agent/boards/BOARD_ID/tasks \ -H "X-Agent-Token: $LEAD_AGENT_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "title": "New task from lead", "description": "Task description", "status": "inbox", "assigned_agent_id": "worker-agent-uuid", "depends_on_task_ids": [] }' ``` -------------------------------- ### Check Backend Code Formatting Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/README.md Verify that the backend code adheres to the project's formatting standards without making any changes. This is useful for pre-commit checks. ```bash cd backend uv run isort . --check-only --diff uv run black . --check --diff ``` -------------------------------- ### Apply Alembic Database Migrations Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/README.md Run these commands from the backend directory to apply pending database migrations using Alembic. This ensures your database schema is up-to-date. ```bash cd backend uv run alembic upgrade head ``` -------------------------------- ### Clean Rebuild and Deploy Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/README.md Performs a fully clean rebuild of services without using cached build layers and pulls the latest images. It then forces recreation of containers. ```bash docker compose -f compose.yml --env-file .env build --no-cache --pull docker compose -f compose.yml --env-file .env up -d --force-recreate ``` -------------------------------- ### View Systemd Unit Logs Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/docs/deployment/systemd/README.md Use journalctl to view logs for the Mission Control backend, frontend, or RQ worker services. Use the --user flag for user units or sudo for system-wide units. The -f flag follows the logs in real-time. ```bash journalctl --user -u openclaw-mission-control-backend -f ``` ```bash sudo journalctl -u openclaw-mission-control-backend -f ``` -------------------------------- ### Sync Gateway Templates Script Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/templates/README.md Use this script to initiate the synchronization of gateway templates. Requires a gateway ID as an argument. ```bash python backend/scripts/sync_gateway_templates.py --gateway-id ``` -------------------------------- ### Run Backend Linting and Type Checking Source: https://github.com/abhi1693/openclaw-mission-control/blob/master/backend/README.md Perform detailed linting and type checking on the backend code using flake8 and mypy. These commands help catch potential errors and enforce code style. ```bash cd backend uv run flake8 --config .flake8 uv run mypy ``` -------------------------------- ### List Available Tags for Task Creation Source: https://context7.com/abhi1693/openclaw-mission-control/llms.txt Retrieve a list of tags that can be used when creating tasks on a board. Requires agent token. ```bash curl -H "X-Agent-Token: $AGENT_TOKEN" \ http://localhost:8000/api/v1/agent/boards/BOARD_ID/tags ```