Ways inLocal-first coordinator

Use the continuity system

aethermind

The cross-harness AetherMind coordinator. It wakes supported agents into project-local continuity and returns bounded, caller-driven context from the work beside them.

Current boundaryPre-release, source-availableOpen on GitHub
What it is

The cross-harness AetherMind coordinator. It wakes supported agents into project-local continuity and returns bounded, caller-driven context from the work beside them.

What is different

The coordinator provides product-level wake and coordination surfaces. The central implementation now has its own repository, aethermind-engine. Check the coordinator README for its current integration and release status before installing.

Use it when

Use it when work moves between supported AI environments and you want one local coordinator, explicit provenance, and bounded recall rather than another hosted memory account.

Do not mistake it for

It is not a cloud memory service or a generic transcript archive. It is source-available pre-release software, so the current README and support boundary are the authority before installation.

Start here

A bounded first move.

The repository README is the authority for prerequisites, release status, and integration details. This sequence establishes the right starting posture before you turn it into a workflow.

  1. Read the current support, privacy, and installation boundary in the repository README.
  2. Use it only from the project root whose continuity it should serve.
  3. Confirm the harness you need is supported before making it part of a workflow.