mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-07 08:27:12 +00:00
283eab181f
Invert the docs convention so the Mintlify-published site lives under docs/public/ and internal artifacts (strategy docs, brainstorms, plans, etc.) sit at docs/ root or docs/internal/. Tools that default to writing into docs/ now land in the catch-all instead of leaking into the published tree. - Move Mintlify content (administration/, agents/, api-reference/, changelog/, core-concepts/, examples/, execution/, getting-started/, human-tools/, integrations/, languages/, reference/, tutorials/, workflows/, images/, logo/, docs.json, favicon.svg, dot-highlight.js) into docs/public/. - Collapse docs-internal/ into docs/internal/. - Update Rust path references (fabro-api/build.rs, fabro-server, fabro-dev), TypeScript generator arg, CI path filters, clippy.toml reasons, AGENTS.md/CLAUDE.md, and README.md image refs. Mintlify dashboard project root must be updated to docs/public/ in a follow-up. .mintignore move/trim and .claude/skills/ updates land in a separate commit.
64 lines
2.3 KiB
Text
64 lines
2.3 KiB
Text
---
|
|
title: "SSH Access"
|
|
description: "Connect to sandbox environments via SSH for direct inspection and debugging"
|
|
---
|
|
|
|
When a workflow runs in a [Daytona sandbox](/execution/environments#daytona), you can SSH into the sandbox to inspect files, run commands, and debug issues — all while the workflow is still executing.
|
|
|
|
<Note>
|
|
SSH access is only available with the Daytona sandbox provider. Local, Docker, and exe.dev sandboxes do not support SSH access.
|
|
</Note>
|
|
|
|
## Connecting to a run's sandbox
|
|
|
|
Use `fabro sandbox ssh` to connect to the Daytona sandbox from any completed or in-progress run:
|
|
|
|
```bash
|
|
fabro sandbox ssh <run-id>
|
|
```
|
|
|
|
Fabro creates temporary SSH credentials and connects directly. Use `--print` to print the SSH command instead of connecting, or `--ttl` to set the credential expiry:
|
|
|
|
```bash
|
|
fabro sandbox ssh <run-id> --print
|
|
fabro sandbox ssh <run-id> --ttl 120
|
|
```
|
|
|
|
## Keeping the sandbox alive
|
|
|
|
By default, Daytona sandboxes are destroyed when the workflow finishes. To keep the sandbox running after the workflow completes — so you can continue debugging — pass `--preserve-sandbox`:
|
|
|
|
```bash
|
|
fabro run workflow.fabro --sandbox daytona --preserve-sandbox
|
|
```
|
|
|
|
Without `--preserve-sandbox`, the SSH session is terminated when the run ends and the sandbox is cleaned up.
|
|
|
|
You can also set `auto_stop_interval` in your run config to control how long an idle sandbox stays alive:
|
|
|
|
```toml title="run.toml"
|
|
[run.sandbox]
|
|
provider = "daytona"
|
|
preserve = true
|
|
|
|
[run.sandbox.daytona]
|
|
auto_stop_interval = 60
|
|
```
|
|
|
|
## What you can do over SSH
|
|
|
|
Once connected, you have a full shell inside the sandbox VM:
|
|
|
|
- **Inspect the working directory** — Agent file changes are at `/home/daytona/workspace`
|
|
- **Run commands** — Execute tests, check logs, inspect process state
|
|
- **Edit files** — Make manual fixes while the workflow is paused at a human gate
|
|
- **Debug failures** — Reproduce and diagnose issues in the exact environment where they occurred
|
|
|
|
## Credential lifetime
|
|
|
|
SSH credentials are temporary and expire after **60 minutes** by default. With `fabro sandbox ssh`, you can set a custom TTL with `--ttl <MINUTES>`. If your session expires, run `fabro sandbox ssh` again to get fresh credentials.
|
|
|
|
## Limitations
|
|
|
|
- SSH access is **Daytona-only**.
|
|
- SSH access is currently available only from the **CLI**. The API server and web UI do not yet expose an SSH endpoint.
|