Get started

On-ramp for people extending Cadence. Linux is first. The product you hatch is a local assistant you name. There is no Aevum Cloud signup in 0.1.

Who this is for

• Contributors working on the assistant runtime, Linux desktop, gateway, or CLI.
• Integrators writing skills or automations against a hatched assistant.
• Advanced users who want to script the assistant.

The two paths

Most work is against a local install on this machine. The assistant, gateway, credential service, and workspace stay on disk. Remote hatch (cadence hatch --remote) and a hosted Cadence Cloud are not offered in 0.1. See Cloud hosting.

The repos

• github.com/Aevum-Project/cadence-assistant (MIT ship tree)
• assistant/ runtime, gateway/ ingress, cli/, clients/linux/, skills/

Talk to the assistant

• CLI: assistant / cadence over the local socket. User-facing copy says assistant.
• HTTP: local runtime routes, usually reached through the gateway. JWT scopes apply. See API.

Next: Architecture, Contributing, Your first skill.