Anesis

Command Palette

Search for a command to run...

Reference

Local state, validation rules, and schema links

Use this page as a compact operational reference for where Anesis stores files, how it validates user input, and where the backend exposes the current template schema.

~/.anesis homeSchema endpoint preview

Local Anesis state

These directories and files are created or updated by the current CLI implementation.

~/.anesis
Root home directory created by the CLI at startup.
~/.anesis/version_check.json
Cached result of the background CLI-version check, so it isn't hit on every run.
~/.anesis/cache/templates
Extracted template cache directories.
~/.anesis/cache/templates/anesis-templates.json
Template cache index with metadata and commit SHAs.
~/.anesis/cache/addons
Extracted addon cache directories.
~/.anesis/cache/addons/anesis-addons.json
Addon cache index with id, name, version, path, and commit SHA.
~/.anesis/cache/stacks
Cached stack manifests (anesis.stack.json), one file per stack id.
~/.anesis/auth.json
Local auth session returned by the browser login flow (owner-only 0600 permissions on Unix).
anesis.json
Written in the project root by `anesis new`: the template name, its commit SHA at generation time, and the list of applied addon ids.
anesis.lock
Per-project addon execution state written in the project root.

Cache and lock file fields

The CLI stores more than raw extracted files; it also writes index metadata for cache and execution state.

  • anesis-templates.json tracks template name, version, source, path, and commit_sha.
  • anesis-addons.json tracks addon id, name, version, path, commit_sha, and repo_url.
  • anesis.json tracks template_name, template_sha, and addons (ids applied via anesis new --stack).
  • anesis.lock stores, per addon: id, version, variant, commands_executed, a journal of rollback actions, and the resolved inputs used for that addon.

Validation rules at a glance

These are the local checks performed before project creation, template installation, and publish/update requests.

Project name:
- "." is allowed (scaffolds into the current directory)
- other names may use letters, numbers, -, _, .
- max 255 characters
- must not start with "."
- must not end with "." or space
- must not already exist on disk
- must not be a reserved Windows device name (CON, PRN, COM1, LPT1, ...)

Template / addon-id name:
- may use letters, numbers, -, _
- spaces, dots, slashes, and other punctuation are rejected

GitHub URL:
- host must be github.com
- path must contain at least owner/repo

Template schema endpoint

The backend exposes the current JSON Schema used by the web app and registry validation layer.

View raw schema

Schema preview is unavailable right now. The raw endpoint is still linked above.

CLI Commands