[dogfood][windsurf,cline,roo-code][npm+main] No documented uninstall; copied rule files not covered by symlink sweep

Open Beginner friendly
#210 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, shell

Research direction

Start with the Uninstall section in docs/install.md and the install scripts at adapters/windsurf/install.sh and adapters/cline/install.sh. Reproduce the install and uninstall flow in the isolated HOME described in the issue, then document cleanup for the copied rule files and verify that every listed adapter leaves no files behind.

Written by the indexing model from the issue text.

Description

dogfood P2

Adapter: windsurf, cline, roo-code
Install path: main 829f516 and npm 1.5.0

Exact command: follow docs/install.md → Uninstall

Expected: A documented uninstall for every adapter that leaves nothing behind.

Actual: The Uninstall section covers only symlink adapters under ~/.claude ~/.cursor ~/.grok ~/.copilot. No uninstall is documented for ~/.codeium/windsurf, ~/.cline, or ~/.roo-code. These adapters also copy rule files (cp, not ln), so a symlink sweep wouldn't remove them even if the paths were added.

Output

docs/install.md:187  Symlink-based adapters (`claude-code`, `cursor`, `grok`, `vscode`):
docs/install.md:193  find ~/.claude ~/.cursor ~/.grok ~/.copilot -type l -lname "${CLONE}/*" -delete
adapters/windsurf/install.sh:77   cp "$mdc" "$TARGET_HOME/rules/$name"
adapters/cline/install.sh:54      cp "$rule" "$TARGET_HOME/rules/$name"

Found by: Simay (SI dogfood 2026-09-24). Isolated HOME under /workspace/si-dogfood/simay/home/; raw logs in /workspace/si-dogfood/simay/logs/.

Dominant language
HTML
Stars
347
Forks
12
Avg merge
2d 16h
Merged PRs (30d)
95

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coco-research/coco

All issues in coco-research/coco

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.