cc-haha vs skill-recorder

cc-haha is much bigger: 14.3k stars against 3.8k. Over the days we have tracked them cc-haha moved +5.3% and skill-recorder +224.4%, so skill-recorder is growing faster right now.

They split the axes: cc-haha leads on context depth and customization and privacy and model freedom, skill-recorder on setup ease.

Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.

Where they stand today

A desktop-first, local-first Claude Code workstation that combines worktree-aware code diffs, Computer Use desktop control, H5 remote access and IM integrations in one app.

Stars
14.3k
Tracked growth
+5.3%
Maturity
Last commit
3d ago
Language
TypeScript
License
MIT
Cost to run
Requires configuring your model provider API key (third‑party billing applies)

Converts a single on-screen recording (clicks, window switches, URLs, and optional narration) into a generalized, reusable Skill or scheduled Automation using the GitHub Copilot CLI.

Stars
3.8k
Tracked growth
+224.4%
Maturity
Last commit
1d ago
Language
TypeScript
License
MIT
Cost to run
Requires GitHub Copilot access
0%+224%44 tracked days
NanmiCoder/cc-hahamicrosoft/skill-recorder

Six axes, head to head

Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.

Axiscc-hahaskill-recorder
Context depth
How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository.
Diff + Worktree
Recording only
Noise control
How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only.
Approval gating
Manual review/edit
Customization
How far it bends to your team: custom rules, prompts, style guides, per-path config.
Plugins & per-project
Manual edits only
Privacy
Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only.
Self-hostable
Copilot cloud required
Model freedom
Whether you can point it at any provider, or it is wired to one.
BYOK + local models
Copilot only
Setup ease
What it takes to get a first useful run out of it.
API key & config
One-command install

Which one to pick

Pick cc-haha if…

Local-first — pick this when you want a desktop agent that runs against your repo/worktree with built-in diffing, permission approvals, extensible skills and multi-provider model support.

  • Context depth: Diff + Worktree (3/5 against 1/5)
  • Customization: Plugins & per-project (5/5 against 2/5)
  • Privacy: Self-hostable (4/5 against 2/5)
  • Model freedom: BYOK + local models (5/5 against 1/5)
Runs in cli, web-app. Works with anthropic, openai, byok, local-ollama.

Pick skill-recorder if…

Privacy-aware — captures and processes recordings locally and only uploads event data and images to GitHub Copilot when you explicitly choose Analyze, making it easy to create real-world reusable agent skills from one run.

  • Setup ease: One-command install (5/5 against 3/5)
Runs in cli. Works with other-fixed.

What people want from each one

Questions people ask

Is cc-haha better than skill-recorder?

They split the axes: cc-haha leads on context depth and customization and privacy and model freedom, skill-recorder on setup ease. cc-haha is worth picking when local-first — pick this when you want a desktop agent that runs against your repo/worktree with built-in diffing, permission approvals, extensible skills and multi-provider model support.

Which of cc-haha and skill-recorder keeps my code private?

cc-haha: Self-hostable (4/5). skill-recorder: Copilot cloud required (2/5).

What does each one cost to run?

cc-haha: Requires configuring your model provider API key (third‑party billing applies). skill-recorder: Requires GitHub Copilot access.

Full profiles: NanmiCoder/cc-haha and microsoft/skill-recorder. Everything else in Computer use.