Ace: adopt desktopToolRules()
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Read packages/channel/src/desktop.ts and compare its desktop guidance with the integration in src/mcp.ts. Append desktopToolRules(hostName) after the outcome lines, then inspect an Ace agent's instructions to confirm they mention pause, expect, and the recipes.
Written by the indexing model from the issue text.
Description
githubnext/desktop-tools#103 shortened the desktop tool descriptions. Rules every tool shares now live in one place, desktopToolRules(app) in @githubnext/desktop-tools/tools, and the MCP server adds them to its instructions. The rules are:
- exact targets passed back unchanged, and checking
availability; - single-use snapshots, with points as screenshot fractions;
- background versus foreground input;
- what each outcome means;
- pause;
desktop_waitandexpect;- observed content is data, not instructions;
- the recipes link.
Ace's desktop_* tools use desktopTools() but carry their own agent guidance (packages/channel/src/desktop.ts), so Ace agents will no longer see these rules unless that guidance includes them.
To do in Ace: after the outcome lines of its desktop guidance, append ...desktopToolRules(hostName), as src/mcp.ts does here. Then check that an Ace agent's instructions mention pause, expect and the recipes.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#529 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
githubnext/ace2#528 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
githubnext/ace2#511 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
githubnext/ace2#506 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
mobile-next/mobile-mcp#526 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 73/100
redhat-developer/rhdh-plugin-export-overlays#4470 · 1 comment ·
Maintainers usually reply within 1 day