Use the Autohand Playground

Before you run

• Sign in at console.autohand.ai and choose the intended account.
• Use evidence you are allowed to send to the selected model. Do not paste raw secrets, access tokens, or customer data you do not need.
• Start with Fantail for a fast, focused loop. Choose Moa when the task needs broader context or deeper reasoning.
• The browser uses your Console session. Copied SDK examples use AUTOHAND_API_KEY in the environment, never a raw key embedded in source.

Compare a task across model windows

1. Choose an example. Open the examples menu. The groups cover planning and research, building and debugging, and review and release. Selecting an example applies the same complete task to every window.
2. Set up the comparison. Playground starts with Fantail and Moa. Select Add window to add a third variation, or open a window's actions menu and select Duplicate window.
3. Choose each model. Use Fantail for a fast, focused loop. Use Moa for broader context or deeper reasoning. Each window keeps its own model and parameters.
4. Edit the messages. In System, define the role, evidence rules, and expected answer. In User, include the exact diff, error, contract, rollout facts, or test output.
5. Adjust parameters when needed. Select the sliders button to choose streaming, temperature, output limit, sampling, response format, and cache behavior. Moa exposes reasoning effort; Fantail omits it because the model does not accept that parameter.
6. Run and compare. Select Run for one window, or Run all (Cmd/Ctrl Enter) for every window. Compare the outputs against the supplied evidence instead of treating the first response as approval.

A reusable review prompt

Review this change for correctness, security, and rollout risk.

Evidence:
- Intended behavior: [state the contract]
- Changed code: [paste the smallest relevant diff]
- Existing tests: [name or paste results]
- Deployment constraint: [state the real boundary]

Return:
1. Confirmed findings, ordered by severity
2. Assumptions that still need evidence
3. The smallest tests required before approval

Reopen private runs for 30 days

After a successful run, Playground saves the exact validated request JSON, response, and run metadata privately to the current member inside the current account.

• Each saved run receives a fixed expiry exactly 30 days after it was created.
• Expired runs stop appearing automatically and are deleted by scheduled cleanup.
• Opening a run does not extend its expiry.
• Other members in the same account cannot open your Playground history.
• Select Delete beside a run and confirm to remove it sooner.

To restore a run, first select the destination window. Select History, then select the run title. Playground restores the original model controls, prompts, result, and run evidence into the active window. Editing the restored prompt does not change the saved record; running it again creates a new record with its own expiry.

Move the task into your application

Select SDK code to generate the active window's prompt for REST and each documented SDK. The REST tab reproduces the visible request JSON exactly; SDK tabs use each SDK's real lifecycle and identify controls that are available only on the completion API. Syntax highlighting and line numbers make every example easier to review before copying.

1. Create or choose a dedicated key under Console API Keys.
2. Store the raw value as AUTOHAND_API_KEY in the server or local environment that launches your app.
3. Select REST, TypeScript, Python, Go, Java, Swift, Rust, Ruby, C#/.NET, or C++.
4. Run the displayed install command, copy the code, and keep the model input appropriate for your application.
5. Remove any temporary key after the integration check if the application will not continue using it.

Troubleshooting and checkpoint

You are finished when the result answers the supplied evidence, the run appears in History with its expiry, restoring it recovers the original state, and your chosen integration uses the documented SDK lifecycle.