HTTP API
The default integration path for products, backends, and workflow engines that need the hosted control plane without a local mount.
Platform
Model the hosted workspace explicitly.
AetherFS is the hosted service behind the public API and the Aether CLI experience. Users connect to the service through HTTP, gRPC, or Aether, and the session remains the main unit of work across all three.
Client surfaces
The hosted service is one thing. The client entry points are another.
gRPC services
Use the hosted gRPC services when your client wants direct service contracts, richer streaming, or a protocol-first integration path.
Aether CLI
The easiest migration path when users or agents still need local filesystem semantics for editors, shells, builds, or tests.
Core concepts
The terms that matter on the public surface.
Session
The isolated working environment. Most workflows and most API calls should be scoped here.
Source
The known baseline a session starts from, such as a repository, snapshot, template, or another content root.
Fork
A clean split from an existing session when proposals or actors need to diverge safely.
Checkpoint
A recoverable saved state for milestones that matter but are not yet the final durable outcome.
Approval
An explicit review gate for workflow transitions that should not happen automatically.
Commit
A durable outcome that records work beyond the temporary live session.
Manifest
A structured view of filesystem state used to inspect metadata and trees without fetching every file.
Session model
Keep the hosted workflow and the working copy aligned.
The strongest AetherFS products are clear about which surface the user should use, where the source comes from, what the session is allowed to do, and when a checkpoint or commit should happen.
- Sessions are the primary unit of work.
- A session can start from a source or a blank state.
- HTTP and gRPC are the hosted integration surfaces.
- Aether is the local client when users need filesystem semantics.
- Most integrations should expose the session ID clearly.
User-facing capabilities
Everything the public hosted product surface is actually trying to solve.
Session lifecycle
Create, inspect, list, fork, checkpoint, restore, archive, and delete workspaces with the session as the clear user-facing boundary.
Filesystem service
Browse trees, retrieve manifests and metadata, read files, patch content, rename paths, manage directories, and use richer file routes when the workflow needs them.
Collaboration and review
Attach annotations, request approvals, publish session-scoped messages, and store structured knowledge without hiding workflow state inside ordinary files.
Persistence and delivery
Use checkpoints for recoverability, commits for durable outcomes, and imports or exports when a result has to cross the service boundary.
Health and reporting
Expose health, usage, analytics, and other non-file signals as first-class service data for support, workflow logic, and reporting.
Aether CLI
Give users a local mount for a remote session, plus cache controls, runtime diagnostics, logs, and metrics on a machine they control.
Next