Clarify press key input format

[masnwilliams]

Summary

• document that each press_key.keys item accepts one X11 keysym or chord
• show the canonical Ctrl+minus punctuation form
• direct agents to use separate array items for sequences and type_text for text

Rollout

Merge after kernel/kernel-images#364 is deployed so the documented punctuation form is supported by the runtime.

Testing

• bunx prettier --check src/lib/mcp/tools/computer-action.ts
• bun test
• bun run build compiled successfully and passed TypeScript checks, then stopped during page-data collection because required runtime configuration is unavailable locally

---

Note

Low Risk
Documentation-only change to a Zod .describe() string; no runtime validation or execution behavior is modified.

Overview
Updates the computer_action MCP tool schema so the press_key.keys field description is explicit for agents calling the API.

The new text states that each array element is a single X11 keysym or chord (with examples including Ctrl+minus), that sequences or repeats belong in separate array items (not space- or comma-separated strings), and that literal text should use type_text instead of press_key.

^{Reviewed by Cursor Bugbot for commit f6e312d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
mcp	Ready	Preview	Sep 10, 2026 2:33pm UTC

[rgarcia]

looks good. merge depends on kernel/kernel-images#364 being merged and deployed first so the documented Ctrl+minus form is supported by the runtime.