We turned Cursor.ai into an OpenClaw-style multi-agent control panel

I’ve been experimenting with Cursor agents for more than just one-off coding tasks, and I kept running into the same problem: once you have multiple agents running across different workflows, the terminal starts to feel messy fast. So we built a small open-source web UI around the Cursor CLI. The idea is simple: make Cursor agents feel more like an OpenClaw-style multi-agent cockpit. What it does: * Run multiple Cursor agent sessions in browser tabs * Keep separate `chat_id`s per agent/workflow * Persist each agent’s workspace, messages, scheduler settings, and CLI prefix * Schedule agents to run automatically * Edit each agent’s `AGENTS.md` from the UI * Edit project MCP config from the UI * Start, stop, resume, and inspect agent runs * Reorder tabs and keep the layout remembered * Use local folders like `chats/reddit`, `chats/backlinks`, `chats/getleads`, etc. as agent workspaces The main reason we built it was to manage recurring agents for practical business tasks: Reddit scouting, backlink work, lead scraping, website redesign demos, AI widget outreach, and similar workflows. One thing that surprised me: MCP config handling became really important. Cursor CLI appears to use the nearest `.cursor/mcp.json` from the workspace path, so nested agent workspaces can accidentally shadow the root MCP config. We added a simple MCP config editor because debugging that manually was painful. It’s not trying to replace Cursor. It’s more like a thin control layer on top of `cursor-agent`, so you can run multiple specialized agents without losing track of state. Curious if anyone else is building similar multi-agent setups around Cursor CLI. Also interested in ideas for making this more reliable for long-running scheduled agents.