Skip to main content

Aether CLI rollout starter kit

This page is for product teams shipping Aether CLI as the local user experience.

Product goal​

Let users:

  • receive or select a session
  • mount it locally with Aether CLI
  • work with familiar editors and shell tools
  • rely on the hosted product for review, approval, and persistence

Minimum rollout package​

You need:

  • install instructions
  • endpoint guidance
  • auth guidance
  • one good mount example
  • one good troubleshooting path

User-facing baseline​

At minimum, document:

  • AFS_AETHER_SERVER_ENDPOINT
  • [bridge].server_endpoint
  • how to run aether mount
  • when to use aether doctor
  • how to stop or unmount
  1. your product creates or selects a session
  2. your product exposes the session ID clearly
  3. the user mounts with Aether CLI
  4. the product still owns review, approval, and persistence

This keeps the local experience and the hosted workflow cleanly separated.

When a user reports a problem, capture:

  • aether version
  • endpoint in use
  • relevant env var overrides
  • aether doctor
  • aether logs tail
  • aether status --session-id ... if the runtime is active

Rollout checklists​

Install readiness​

  • users can get the binary
  • platform-specific prerequisites are known
  • install path is documented

Connectivity readiness​

  • endpoint is documented
  • auth expectations are documented
  • environment wrappers exist if multiple environments matter

Mount readiness​

  • example mount command exists
  • session handoff flow exists
  • cache guidance exists

Support readiness​

  • troubleshooting page exists
  • support knows what diagnostics to collect
  • users know the difference between doctor and status
  • one wrapper per environment
  • one cache root per environment
  • explicit logging format only when support needs it

What not to do​

Avoid:

  • making users guess the endpoint
  • forcing users to learn the raw API just to mount
  • mixing environments into one cache root
  • treating Aether CLI as if it replaces the hosted workflow controls

First release checklist​

  • users can install aether
  • users can configure the endpoint
  • users can mount a session
  • users can get basic troubleshooting help
  • support can diagnose common failures