FAQ
Common questions about using ClawCode as an OpenClaw wrapper for coding, parallel app creation, and agent orchestration.
OpenClaw is a free, open-source CLI agent runtime. You install it on your machine and connect it to your own AI model subscriptions — such as Anthropic Claude or OpenAI GPT. ClawCode then sits on top of OpenClaw as a desktop workspace. ClawCode does not provide AI model access — that comes from your own accounts.
Yes. OpenClaw must be installed and configured with your AI models before ClawCode will work. ClawCode is the workspace layer — OpenClaw is the runtime that actually runs your agents using your connected models.
No. ClawCode is a desktop workspace app you subscribe to. It does not include AI model access or API credits. You bring your own API keys — Anthropic, OpenAI, or other supported providers — and configure them through OpenClaw. Your model usage costs go to your model providers directly.
Any model that OpenClaw supports — including Anthropic Claude, OpenAI GPT, and other compatible providers. You connect these through OpenClaw's configuration before launching ClawCode.
OpenClaw for coding means using agent-driven execution for planning, coding, testing, and shipping flows. ClawCode wraps this into a clearer multi-project UI for day-to-day development.
Yes. ClawCode is a desktop workspace built on top of OpenClaw, adding a multi-project dashboard, role-based agents, planning tools, git actions, and a Pro subscription layer.
ClawCode is a desktop app for macOS (Apple Silicon and Intel) and Windows.
ClawCode offers Pro monthly and Pro yearly subscriptions.
Yes. Each app/project gets isolated context and agents, so multiple apps can run in parallel safely.
Each project can run multiple role-based agents in parallel. Typical setups include coding agents and manager/planner agents coordinating tasks like a real software team.
Yes. You can trigger another coding agent and continue work in parallel while preserving project context and queue state.
Yes. Agents can create and update plans, tasks, and workflows, then trigger execution loops to finish queued work.
Yes. You can queue instructions/messages and let agent loops process them as they become available.
Yes. ClawCode keeps structured project context so agents understand app goals, architecture, and current execution state.
Yes. Planner agents can break down product goals into implementation plans, tasks, and execution workflows.
Yes. ClawCode is built to reduce tool sprawl by combining planning, tasks, workflows, and execution in one app.
Yes. The central dashboard lets you monitor and trigger agents across multiple projects from one place.
Yes. You can stage, commit, and push from inside ClawCode, with project-aware visibility and logs.
Yes. ClawCode supports reusable automations and workflow execution for repeated development operations.
Yes. Speech-to-text command flow is supported with your own API key setup.
Yes. Each project has terminal access so coding and operations stay isolated and organized.
A project can run multiple roles including planner, coder, UI, and bug-fixer agents, plus additional purpose-specific agents when needed.
Yes. ClawCode is designed as one central dashboard for all your projects, with fast project switching and cross-project visibility.
Yes. Agents continue running in their project context while you operate in other projects, so work progresses in parallel.
Yes. It combines planning, tasks, workflows, orchestration, and shipping so many teams can replace separate planning/task/workflow tools.
Yes. ClawCode includes in-app git actions like stage, commit, and push, alongside logs and recent change views.
Yes. ClawCode runs on your desktop with OpenClaw, giving you local execution and project-level control.