Help with Handrail

Start small, stay present.

Handrail is being built for macOS first. Its current development scope is a small set of identified button actions and short waits. A target app being allowed does not make every control or gesture supported.

SEA can explain the interface and propose a next step. Chat does not authorize execution. Handrail’s staged apps still run on your real desktop; staging is not a virtual machine or protection for personal documents.

From demonstration to a reviewed skill

1. Check setup. In Settings, review the helper and the permissions needed for the feature. Recording uses Accessibility, Screen Recording, and Input Monitoring for HandrailHelper. Voice is optional.
2. Choose a disposable target. Follow the instructions supplied with your development build. Use a small task and ordinary physical input. A screenshot alone does not prove that input was recorded.
3. Stop and inspect. Check the trace and proposed actions. Unsupported input, ambiguous controls, or a changed target should produce a refusal. Read it before trying again.
4. Review the plan. Move or remove captured button actions and adjust existing waits within the offered limits. At least one button action must remain. Reset restores the original proposal without changing your recording.
5. Choose an outcome. Select a non-sensitive control and the final value you expect. Choose a result that shows the task succeeded, rather than a value that was already true. Review the outcome again if you change the steps.
6. Save, then confirm separately. Saving signs a local skill. It does not run it. Invoke requires another confirmation, and you should stay with the target until the run and outcome check finish.

The development plan is limited to 25 steps, with waits up to five seconds. Complete physical recording, replay, Stop, keyboard, and VoiceOver acceptance is still pending.

Stop and recover

Use Stop when a run is wrong or you want to interrupt it. Wait for the acknowledgement. If cleanup or stopping cannot be confirmed, close the test target if necessary and retain a description of what happened.

• A safety refusal: read the explanation, return to the selected test app, and start a fresh supported demonstration. Do not broaden permissions to bypass it.
• A stale helper after an update: use Reset Helper in Setup & Permissions, quit and reopen Handrail from the supplied location, then refresh status.
• A damaged staged app: quit the target and use Reset Staged Apps in Beta Support. Stage its original again. This reset removes staged copies only.
• A provider connection problem: check the configured server and endpoint. Preserve any custom settings before resetting them.

SEA and optional voice

Text input works without voice permissions. Push to Talk uses microphone access and on-device Speech Recognition. Review the transcript in the composer before sending it to a model.

Your configured model endpoint determines where text requests go. Local servers can also retain or forward requests. See Handrail’s data and privacy information.

A useful problem report

Record the app version, macOS version, target app, steps to reproduce, expected result, and what happened. Include the visible refusal or Stop acknowledgement, whether the input was physical, and whether it repeats after relaunch.

Beta Support can create a local support export. Inspect it before sharing: it may contain local paths and your account name. Exporting does not submit a report. Do not attach personal screenshots, recordings, skills, prompts, keys, credentials, or the whole Handrail data folder.

A public beta support process and response coverage are still being prepared. General AlphaBytez enquiries are available through Contact; this does not promise a Handrail support response time.