> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bead.run/llms.txt
> Use this file to discover all available pages before exploring further.

# bead sandbox FAQ

> Find answers in the bead sandbox FAQ about signup, credit, machine kinds, snapshots, local tools, and application access.

Use this bead sandbox FAQ when choosing a workflow or checking how an account or machine behaves. Each answer points to the relevant guide for the next step.

## Getting started

### Can an agent sign up by itself?

Yes. Run `bead signup` without a card or human sign-in. Agent enrollment can receive trial credit. Check `bead balance` for your grant and expiry. Human GitHub signup starts with zero credit. See [Agent trial credit](https://docs.bead.run/platform/trial-credit.md).

### How do I see an agent's machines in the dashboard?

Create an ownership link with `bead account claim-link` using admin scope. The intended human signs in and confirms the claim. It adds no credit and keeps trial restrictions. See [Account ownership](https://docs.bead.run/organizations/ownership.md).

## Pricing and limits

### Do idle machines cost money?

Running machines incur configured memory charges and measured busy CPU charges. Paused machines incur retained storage charges. Run `bead pricing` or call `GET /v1/pricing` for current rates. See [workload estimates](https://docs.bead.run/platform/estimates.md).

### Why is available credit less than balance?

Credit is reserved for authorized work before usage settles. Reservations are commitments, rather than final charges. See [Prepaid credit](https://docs.bead.run/platform/prepaid-credit.md).

### Does credit guarantee capacity?

No. Admission also checks organization limits, shape limits, and placement capacity. Inspect `bead limits` and the returned `next_action`.

## Machines and snapshots

### What is the difference between temporary and persistent?

Temporary machines delete when their timeout ends. Persistent machines keep memory and disk when paused and use funded storage. See [Machine lifetime](https://docs.bead.run/run-work/lifetime.md).

### Do snapshots keep running processes?

Snapshots capture memory, disk, and device state. External connections may need to reconnect. Environment values, files, and browser sessions can survive capture. See [Snapshots](https://docs.bead.run/snapshots/overview.md).

### Can I resume at a different size?

Memory restores and forks retain the source CPU and memory bounds. To use another size, create a new machine from a disk template. See [Machine sizes](https://docs.bead.run/machines/sizes.md).

## Local tools and networking

### Are my laptop tools installed remotely?

No. Worktree commands run on Linux with the selected template's tools. Your preparation script installs project dependencies. See [Set up a worktree](https://docs.bead.run/worktrees/quickstart.md).

### Do edits sync continuously?

Worktree sync is explicit and one way. A dev service syncs once when it starts; stop and restart it to sync edits. See [Dev services](https://docs.bead.run/worktrees/services.md).

### Is every application URL public?

Machine application URLs require authentication. Worktree preview links grant possession-based access to a specific application. See [Application URLs](https://docs.bead.run/connect/public-urls.md) and [Preview sharing](https://docs.bead.run/worktrees/sharing.md).

### Where do I check service health?

Open [status.bead.run](https://status.bead.run). Read timestamps as well as status; missing observations do not prove availability. See [Service status](https://docs.bead.run/help/status.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.