For people who already use Claude Code, Cursor, Codex, Windsurf…
Drop commando onto Claude Code, Cursor, Codex, or any AI agent you already use. It gets a real job — clocks in at 8am tomorrow morning, works through its tasks, reports to you on Feishu.
"Plain. Data-first. Never marketing-speak.
Knows my product like a co-founder."
Powered by
Claude Code + commando
Why commando
You're already paying $20/mo for Claude or $20/mo for Cursor. commando doesn't replace either — it makes them stop forgetting, show up on time, and actually integrate with your workspace.
Charter + Semantic memory live on disk. Your partner remembers your product, your users, your last quarter's reflections. Switch from Cursor to Claude Code anytime — the memory comes with you.
Outputs land in Feishu bitable verified or Obsidian vault verified — wherever your team already works. Notion, Slack, Stripe, Gmail are community-pattern connectors you can build in an evening.
Onboarding produces skills tailored to your business. Imported community skills auto-rebuild against your Charter. No more generic "write a Xiaohongshu post" templates.
The OS scheduler — launchd, systemd, cron — runs your partner. Daily briefings, weekly reflections, monthly tax checks. No SaaS daemon, no cloud subscription.
If you've heard of OpenClaw / Molty
Same goal — AI that actually does things: manage your calendar, push reminders, draft reports, scan competitors, triage your inbox. Anything an employee with a clear job description would handle.
The difference: commando runs on your machine, in your IDE, or in your IM — using the AI tool you already pay for (Claude Code, Cursor, Codex, GLM…). No cloud server. No separate token plan. No new monthly subscription.
tl;dr — cheaper, simpler, lives where you already work.
What commando adds
Hiring an employee, three things happen: you tell them their role, you put them on a calendar, you give them a desk where they store their work. commando does the same three things for the AI tool you already use.
01 · The job description
A markdown file in your repo defines this partner — the role, the product served, the voice, the red lines. Every conversation auto-loads it. It never "forgets" between sessions.
Files: charter.md · auto-injected every call
02 · The day's work
Not one skill — many. Writes posts, debriefs meetings, scans competitors, summarizes user feedback. Like a real employee, it handles whatever is on its plate. You can hand it new work anytime.
Files: skills/*.md · imported, custom, generated
03 · The calendar
Schedule says "morning brief at 8, draft review at 11, weekly reflection Sunday 7pm". The OS scheduler runs it — your partner does the work and reports to you on Feishu / Notion. You stay in your normal workflow.
Files: schedule.yaml · launchd / systemd / cron
⚠ Needs a CLI agent in PATH or an API key for the 8am fire. IDE agents (Cursor, Windsurf…) only run when you have them open — fine for Onboarding, won't wake up while you sleep.
What's inside a Skill
Each Skill bundles three things — the steps to do the task, the domain knowledge to do it well, and the connectors it reads or writes through (Feishu, Notion, Gmail, Stripe…). Skills come from two sources: commando's official Registry, or generated for you during Onboarding. Either way, every Skill gets auto-rewritten against your Charter — so it speaks in your voice and respects your red lines.
"My Growth Partner doesn't write generic Xiaohongshu posts. They land in my voice, for my ICP, using my bilingual bridge formula."
The full picture:
① A Skill = steps + knowledge + tools. Not just a prompt — it bundles the workflow, the domain references, and the external connectors (Feishu, Notion, Gmail) all in one place.
② Two sources: official Registry, or your own. Browse @commando/* in the Registry. Or have Onboarding generate them in 25 minutes.
③ Both get auto-rebuilt for YOUR role. commando rewrites every Skill's prompt against your Charter — Registry skills stop being generic, your skills stop being only-fit-once. This is the move no other AI tool makes.
25-min dialog → skills/xhs-bilingual-bridge/ already knows your ICP is "Chinese students preparing for IELTS".
commando install @commando/competitive-watch — pulls a generic competitor-scanning skill from the Registry.
commando rewrites the skill's prompt body. Now competitive-watch knows your ICP, your red lines, and which competitors to track. Speaks your voice.
Three real digital partners
Below are three real Charters. Each takes 25 minutes of Onboarding to produce. Each is the same AI tool you already use, configured by commando into a specific role.
Role · Growth partner
Live for 6+ months serving LeMingle — the reference Configuration in this repo.
Powered by Claude Code + commando · outputs land in Feishu bitableverified
Role · Personal finance advisor
Shows how strong red lines make the partner safer than a generic assistant.
Powered by Codex + commando · outputs land in Notion databasecommunity PR welcome
Role · Job search coach
Time-bounded relationships with explicit failure criteria in the Charter.
Powered by Cursor + commando · outputs land in Obsidian vaultverified
Where commando runs
commando isn't a new AI tool. It's a layer that drops onto whichever one you already use — turns it into a real employee instead of a chat box.
1 — Plug into a CLI agent
commando installs as a CLI tool. Your existing CLI agent does the LLM work; commando gives it a Charter, a Schedule, and persistent Skills.
2 — Pair with your IDE
Open your repo in any AI-powered IDE. commando's Onboarding skill loads in the chat panel and produces your agent in 25 minutes. For scheduled runs while you're away from the IDE, pair with a CLI agent or set an API key (Anthropic / Zhipu).
3 — On any cowork platform
Any platform with a base agent works — including cowork/devloop platforms emerging in China and the US. Wherever the agent runs, commando layers on top.
Wherever there's a base agent running, commando turns it into a dedicated digital partner — one with a real job, real memory, and a desk in your Feishu / Notion workspace.
Get started
30-second install. 25-minute Onboarding. Day 1: it clocks in at 8am, runs its Schedule, and pings you on IM.