docs: add smooth typing with typo injection to computer controls

[ulziibay-kernel]

Summary

• Updates the Type text section in computer controls docs with new smooth and typo_chance parameters
• Adds parameter table, code examples in TypeScript, Python, and CLI for all four modes (instant, fixed delay, smooth, smooth+typos)
• Includes demo GIF and MP4 showing the visual difference between instant and human-like typing

Depends on: kernel/kernel-images#201 (implementation PR)

Test plan

• Verify docs render correctly on preview
• Confirm GIF loads and plays in the Frame component

Made with Cursor

---

Note

Low Risk
Low risk documentation-only change; main risk is minor doc/API mismatch (new smooth/typo_chance options and CLI flags) or a broken demo asset link.

Overview
Updates the Type text section in browsers/computer-controls.mdx to document human-like typing via new smooth and typo_chance parameters, clarifying how they interact with the existing fixed delay option.

Adds a parameter table plus expanded TypeScript, Python, and CLI examples covering instant typing, fixed-delay typing, smooth typing, and smooth typing with typo injection, and includes a new "Smooth vs instant typing" demo GIF embed.

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

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Apr 6, 2026, 2:57 PM

[cursor]

Risk Assessment: Very Low

I assessed the PR from the actual diff only.

• Changed files are documentation/media only: browsers/computer-controls.mdx, images/smooth-typing-demo.gif, and images/smooth-typing-demo.mp4.
• The MDX changes add/clarify usage docs and examples for typing options (smooth, typo_chance) plus a demo embed.
• No runtime application code, infrastructure config, auth/permissions logic, or shared production codepaths are modified.
• No .git-blame-ignore-revs file is present to alter attribution scope.

Given the narrow, docs-only blast radius, this is Very Low risk and safe to approve.

  

_{Sent by Cursor Automation: Assign PR reviewers}