Daytona Strawberry

Sandboxes, ssh accesses and codes, worked for you

Your Daytona, worked while you do something else: 5 reads to go through it, 9 writes to change it, and a card in front of every one of those changes.

Open the sandbox. Check it against something else. Write the change. Move to the next one. That is the Daytona afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a sandbox until you approve it.

What it can do is exactly what Daytona exposes to an account you authorise and nothing beyond it: 14 operations, 5 reads and 9 writes. In practice that means it can stop a sandbox, start a sandbox and run a command, and work across the sandboxes, ssh accesses and codes.

The Daytona API stops at Daytona. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Does it read the sandboxes or ask you for them?

5 of the 14 operations are reads.

Your account, not a guess at it: a companion can wait until stopped, list snapshots and list sandboxes, and the full list below is the whole list, with nothing inferred from Daytona's documentation.

The sandboxes are what most of this inventory is about, alongside the ssh accesses. A companion can hold all 14 of these operations and forty open tabs in the same pass, which is how an afternoon of Daytona admin becomes a queue you review.

  • Wait Until Stopped
  • List Snapshots
  • List Sandboxes
  • Get Sandbox
  • Get Preview Link

Can it change a sandbox without asking?

All 9 write operations wait for you.

A companion can stop a sandbox, start a sandbox and run a command, and each one is staged on an approval card first: you see the sandbox, the field and the new value before it lands in Daytona.

Nothing in Daytona is sent, changed or deleted on your behalf without that click, and a rejected card leaves the sandbox exactly as it was. The gate is the same one on every surface, described at security.

  • Stop Sandbox
  • Start Sandbox
  • Run Command
  • Run Code
  • Revoke SSH Access
  • Delete Sandbox
  • Create SSH Access
  • Create Sandbox
  • Clone Git Repository

Does the sandbox sweep have to be asked for every time?

Yes.

Saved as a routine, the Daytona sandboxes pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the Daytona sandboxes sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Daytona account and a companion works 14 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide