Skip to content

docs: real-device queue is 15 minutes; --remote needs the plugin - #210

Merged
siddhant573 merged 1 commit into
LambdaTest:docs/real-device-smart-variablesfrom
rohithmone-lt:docs/real-device-smart-variables-fixes
Oct 15, 2026
Merged

siddhant573 merged 1 commit into
LambdaTest:docs/real-device-smart-variablesfrom
rohithmone-lt:docs/real-device-smart-variables-fixes

Conversation

@rohithmone-lt

Copy link
Copy Markdown
Contributor

Fixes for #209, targeting its branch.

  1. Real-device queue: "up to 10 minutes" → "up to 15 minutes" everywhere (skills, kiro steering, user guide). Source: the Appium binding the runner pins (testmuai-appium-bindings==0.4.9) sends queueTimeout = QUEUE_TIMEOUT or 900 s, and kane-cli never sets QUEUE_TIMEOUT.
  2. "Any machine, only kane-cli login" now notes that --remote also needs the remote-execution plugin and a HyperExecute plan (SKILL.md, mobile.md availability row, kiro steering).

🤖 Generated with Claude Code

- A real-device session over the plan's devices queues for up to 15
  minutes (the Appium binding's queueTimeout default, 900 s), not 10.
- Real devices from any machine need only kane-cli login, except
  --remote, which also needs the remote-execution plugin and a
  HyperExecute plan.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@siddhant573
siddhant573 merged commit 0ab86d5 into LambdaTest:docs/real-device-smart-variables Oct 15, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants