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 an MCP tool schema description; no auth, data handling, or runtime behavior in this diff.

Overview
Expands the MCP computer_action Zod description for press_key.keys so agents get clearer guidance at the tool boundary—no execution logic changes in this repo.

The new text states that each array element is a single X11 keysym or chord (e.g. Return, Ctrl+t, Ctrl+minus), that sequences belong in separate 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 9d02f79. 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 3, 2026 1:15am UTC