Hmbown / Hmbown/Codewhale

One easy install from all three doors: website app, marketplace plugin, GitHub repo

Open
#6,303 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
41k
Forks
3.6k
Avg merge
13h 59m
Merged PRs (30d)
299

Description

Installing Computer Use should be smooth from all three doors, and today each door tells a different story:

1. Website Mac app download ([codewhale.net/computer-use]()) — the signed .app with bundled helper; needs Accessibility + Screen Recording grants with a guided path when missing.
2. Marketplace plugin (codewhale-plugin-marketplace plugins/computer-use) — install/enable/trust flow inside CodeWhale; must land on the same helper + grants without a second ceremony.
3. GitHub repo (Hmbown/codewhale-cu-plugin) — source checkout: npm test, build:app/install:app, MCP stdio wiring for other hosts (muse bundle pattern), dev prerequisites.

Work: audit what each surface says and does today; converge on one install narrative (same version truth, same grant troubleshooting, same verify step — e.g. request_access receipt); fix the repo-side surfaces in this project (README quickstart, DISTRIBUTION/RELEASE_CHECKLIST, marketplace install copy); prepare website source changes for human-gated deploy (gh workflow run web.yml — never deploy from this work).

Acceptance sketch: a clean-machine user coming through any one door reaches a working background TextEdit observe-act-verify loop following only that door's instructions, with every failure naming the missing piece (app vs grant vs host), and all three doors agree on the current version and the verify receipt.

Contributor guide

Open the contributing guide

Research direction

Start by auditing the README quickstart, DISTRIBUTION/RELEASE_CHECKLIST, marketplace install copy, and the website source, then run npm test and inspect build:app/install:app plus web.yml. Done means all three doors state the same version, grant troubleshooting, and request_access verification, and a clean-machine TextEdit observe-act-verify loop works without deploying the website.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript, rust
Domain
developer-experience, devops, documentation, release
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.