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

# Current limits

> The explicit boundary of Dure's alpha persistence, SSH, platform, and isolation guarantees.

Dure is an alpha. These boundaries are part of the product contract, not fine
print.

## Persistence matrix

| Scenario                    | Current behavior                                                                                                      |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Close or restart Dure       | Managed local agents continue in the detached Hmux host and reattach.                                                 |
| Webview reload or app crash | Same process boundary as an ordinary app restart.                                                                     |
| Runtime update              | A running session stays with the immutable runtime version that owns it.                                              |
| Hmux host crash             | The live process and PTY do not survive.                                                                              |
| Machine reboot              | Processes do not survive; saved recipes can be recreated on new PTYs.                                                 |
| SSH disconnect              | SSH projects reconnect, but remote Hmux parity is not the default path yet.                                           |
| Plain terminal launches     | The provider and its activity are recognized automatically, but the session is not automatically promoted to managed. |

## SSH

Dure supports SSH projects, remote folders, remote worktrees, provider commands,
reconnection, and several authentication methods. Remote provider sessions still
use a legacy path unless explicitly provisioned through the current canary
workflow. Do not assume the local Hmux process-survival contract applies to a
remote agent yet.

## Platform and distribution

* macOS on Apple silicon only
* unsigned public alpha build
* current public artifact retains the legacy `Hebbian` bundle identity
* Windows, Linux, and Intel Mac builds are not published
* product license terms are not finalized; the Hmux subtree has its own license

## Isolation

Git worktrees isolate files, branches, and indexes. They do not provide
container, virtual-machine, filesystem-permission, credential, port, or network
isolation.

## Orchestration

The orchestration mailbox is currently local to one Dure app channel. Agents on
a remote SSH host do not directly join that local mailbox. Messages are
persisted locally, but this is not a hosted queue or a cross-device service.

Use explicit recipients when a particular agent must act. `@all` is useful for
announcements and shared history, but it does not yet track a separate delivery
acknowledgement for every recipient.

## Recovery is not always survival

Reattaching to a running Hmux host preserves the live process. Restarting a
provider from a recorded conversation ID and restoring a shell recipe both
create new processes. Dure reports these as different operations so a successful
recovery is not mistaken for uninterrupted execution.

Return to the [quickstart](/en/quickstart) or read the
[session model](/en/session-model) and
[orchestration guide](/en/orchestration).