Skip to content
Axocoatl

Local verification

Use this procedure to prove the local runtime and browser app are connected to the build you intend to evaluate.

Verify the installed path

Section titled “Verify the installed path”
Terminal window
which axocoatl
axocoatl --version
axocoatl --help

When working from source, build the explicit CLI package and use that binary:

Terminal window
cargo build -p axocoatl-cli
./target/debug/axocoatl --version

The root package is a benchmark placeholder; a generic root build is not the same proof as building axocoatl-cli.

Verify Ollama

Section titled “Verify Ollama”

  1. Start Ollama in another terminal:

    Terminal window
    ollama serve

  2. Pull the exact model configured for the Agent:

    Terminal window
    ollama pull llama3.2
    ollama list

  3. Validate and run doctor:

    Terminal window
    ./target/debug/axocoatl validate axocoatl.example.yaml
    ./target/debug/axocoatl doctor --config axocoatl.example.yaml

Doctor live-probes Ollama and requires every configured Ollama Agent model to be present. Hosted provider checks are not equivalent: they inspect credential presence—including OpenRouter when configured—but do not make a live model request. Doctor reports Podman ready only after the client and applicable machine state pass and a bounded podman info --format json probe returns a JSON object successfully.

Start the embedded app

Section titled “Start the embedded app”
Terminal window
AXOCOATL_DATA_DIR=/absolute/path/to/test-data \
  ./target/debug/axocoatl dev --config axocoatl.example.yaml

Open http://127.0.0.1:8080/. This / page is the product workbench. Confirm:

  1. the left rail and Session home load without a console error;
  2. a folder Session can be created with a configured Agent;
  3. the exact image and setup proposal remain visible and unchecked unless you approve them; before Ready, Send and repository tools stay gated;
  4. after an explicit setup decision, the environment reaches Ready and a read-only prompt becomes durable in History;
  5. Files, Source Control, Terminal, and Preview are reachable through that Session sandbox rather than a host fallback;
  6. Settings opens Agents, Skills, MCP servers, and Automations;
  7. light, dark, narrow, and reduced-motion states remain usable for the changed workflow.

Run repository gates

Section titled “Run repository gates”

From the source checkout:

Terminal window
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace
cargo test --doc --workspace
cargo build -p axocoatl-cli

Some ignored sandbox tests need Podman. Webhook tests bind a local port and may need to run outside a restricted test sandbox. A route/unit test does not replace verifying the actual embedded page.

Continue with Product model →