Skip to main content

Common use cases

Remote development workspace​

A product creates a session for a user from a known source. The user mounts the session locally with Aether CLI, edits files with familiar tools, and persists results when the task is complete.

Agent-assisted change proposal​

An automation system creates a session, performs analysis, writes candidate changes, and stores supporting context in annotations or the knowledge cache. A human reviews the result, approves it, and the system commits or exports the outcome.

Review sandbox​

A baseline session is forked into several candidate sessions, one per proposed approach. Reviewers inspect each one independently, choose the best result, and only then promote it.

Temporary analysis workspace​

A session is created for exploration or diagnostics. Tools read manifests, inspect files, and record findings through annotations or knowledge entries. The session is later deleted because only the findings need to remain.

Controlled content transformation​

A workflow imports or stages content into a session, applies transformations, validates the result, and exports the transformed content when it is approved.

Training, demos, and reproducible environments​

A session source provides a consistent starting point for each user or run. Every participant gets an isolated copy that can be safely modified without disturbing the shared baseline.

When AetherFS is a strong fit​

AetherFS is a strong fit when you need:

  • Isolation by session.
  • Durable but optional persistence.
  • Both API-driven and local-tool workflows.
  • Human review mixed with automation.
  • File trees as the primary unit of work.