Examples

Copy Markdown View Source

These examples cover two surfaces:

  • three provider-agnostic live examples on ASM's common API
  • one offline inference-endpoint publication proof
  • four provider-specific examples that intentionally cross into one provider's SDK-native surface

Nothing runs by default. The live CLI examples require --provider.

Included Examples

Default Behavior

If you omit --provider, the live CLI examples print usage and exit without touching a live CLI.

That is deliberate. The live examples never silently pick a provider for you.

inference_endpoint_http.exs is the exception. It defaults to the Gemini provider profile and runs against a local fake backend so the publication seam stays deterministic and offline.

Permission Defaults

All ASM examples in this directory default to permission_mode: :bypass unless you override it with --permission-mode or ASM_PERMISSION_MODE.

--danger-full-access is the example-level alias for --permission-mode bypass. It keeps the public ASM contract normalized as permission_mode while exposing an obvious remote-tooling knob for hosts where provider-native sandboxed shell execution is not usable.

At startup, each example prints:

  • the normalized ASM permission mode
  • the provider-native permission term
  • the provider-native CLI flag, when one exists

Examples:

  • Claude: :bypass -> :bypass_permissions -> --permission-mode bypassPermissions
  • Gemini: :bypass -> :yolo -> --yolo
  • Codex: :bypass -> :yolo -> --dangerously-bypass-approvals-and-sandbox
  • Amp: :bypass -> :dangerously_allow_all -> --dangerously-allow-all

Common Ollama Surface

The ASM common Ollama flags are available on the example CLI:

  • --ollama
  • --ollama-model <name>
  • --ollama-base-url <url>
  • --ollama-http
  • --ollama-timeout-ms <ms>

That surface is intentionally partial.

Supported:

  • Claude
  • Codex

Unsupported:

  • Gemini
  • Amp

run_all.sh rejects --ollama* flags immediately for unsupported providers.

Provider semantics differ slightly:

  • Claude keeps the canonical Claude model slot. Use --model for the Claude family name such as haiku, and --ollama-model for the actual Ollama model id.
  • Codex uses the direct Ollama model id. --ollama-model is the effective model selection knob for the common Ollama surface.

For Codex, gpt-oss:20b remains the default validated Ollama example model, but the common surface also accepts other installed Ollama models such as llama3.2. Those non-default models may run with upstream fallback metadata and can behave less reliably under the full Codex agent prompt/tool stack. The common prompt-based smoke examples only enforce exact sentinel assertions for validated-default Codex/Ollama targets, so non-default Codex/Ollama models remain accepted routes but are reported as exploratory rather than guaranteed smoke-test targets.

Run One Example

mix run --no-start examples/live_query.exs -- --provider claude
mix run --no-start examples/live_stream.exs -- --provider gemini
mix run --no-start examples/live_session_lifecycle.exs -- --provider codex --model gpt-5.4
mix run --no-start examples/inference_endpoint_http.exs -- --provider gemini --stream
mix run --no-start examples/live_query.exs -- --provider claude --ollama --model haiku --ollama-model llama3.2
mix run --no-start examples/live_query.exs -- --provider codex --ollama --ollama-model gpt-oss:20b
mix run --no-start examples/live_query.exs -- --provider amp --lane sdk --sdk-root ../amp_sdk
mix run --no-start examples/live_query.exs -- --provider codex --ssh-host example.internal
mix run --no-start examples/live_query.exs -- --provider codex --ssh-host example.internal --danger-full-access
mix run --no-start examples/live_query.exs -- --provider claude --ssh-host builder@example.internal --ssh-port 2222
mix run --no-start examples/provider_codex_app_server.exs -- --provider codex --ollama --ollama-model gpt-oss:20b

Shared flags:

  • --lane <core|auto|sdk> for common-surface examples
  • --prompt <text>
  • --model <name>
  • --stream for inference_endpoint_http.exs
  • --cli-path <path|command>
  • --permission-mode <mode>
  • --danger-full-access
  • --cwd <path>
  • --sdk-root <path>
  • --ssh-host <host>
  • --ssh-user <user>
  • --ssh-port <port>
  • --ssh-identity-file <path>

When you pass --ssh-host, the examples also add noninteractive SSH transport defaults (BatchMode=yes, ConnectTimeout=10) so unattended runs fail fast instead of blocking on password or connection prompts.

Run All Examples

./examples/run_all.sh --provider claude
./examples/run_all.sh --provider codex --model gpt-5.4
./examples/run_all.sh --provider claude --ollama --model haiku --ollama-model llama3.2
./examples/run_all.sh --provider codex --ollama --ollama-model gpt-oss:20b
./examples/run_all.sh --provider claude --provider codex --ollama --ollama-model llama3.2
./examples/run_all.sh --provider amp --lane sdk --sdk-root ../amp_sdk
./examples/run_all.sh --provider codex --ssh-host example.internal
./examples/run_all.sh --provider codex --ssh-host example.internal --danger-full-access
./examples/run_all.sh --provider claude --provider codex --ssh-host builder@example.internal --ssh-port 2222

run_all.sh forwards extra flags to every selected example.

When you pass --ssh-host, the examples switch to execution_surface: :ssh_exec for the selected provider while keeping the default local subprocess route unchanged when you omit the SSH flags.

When you also pass --danger-full-access, the examples keep the same transport surface and switch only the normalized ASM permission mode to :bypass. ASM then projects the provider-native permissive runtime flag for the selected provider.

These example execution_surface and execution_environment forms are the current ASM-facing mapped carriers around the frozen Wave 1 lower packet, especially ProcessExecutionIntent.v1, JsonRpcExecutionIntent.v1, and AttachGrant.v1. Their detailed minimal-lane payload interiors remain provisional until Wave 3 prove-out.

See guides/execution-plane-alignment.md for the ownership and carriage rule.

If gpt-oss:20b is installed locally in Ollama, the Codex examples above are the primary validated route. You can still substitute another installed model such as llama3.2, but that path is less tightly validated by the example smoke checks and now skips exact-output assertions on the Codex side by default.

The three common examples are self-checking:

  • live_query.exs must return exactly LIVE_QUERY_OK
  • live_stream.exs must return exactly LIVE_STREAM_OK
  • live_session_lifecycle.exs must return exactly LIVE_SESSION_STREAM_OK and LIVE_SESSION_QUERY_OK

Provider-native examples validate their own provider-specific success conditions as well.

Environment

  • CLAUDE_CLI_PATH, ASM_CLAUDE_MODEL
  • GEMINI_CLI_PATH, ASM_GEMINI_MODEL
  • CODEX_PATH, ASM_CODEX_MODEL
  • AMP_CLI_PATH, ASM_AMP_MODEL
  • ASM_PERMISSION_MODE
  • CLAUDE_AGENT_SDK_ROOT, CODEX_SDK_ROOT, GEMINI_CLI_SDK_ROOT, AMP_SDK_ROOT

The examples preflight the selected CLI before they start a session and print an install hint if it is missing.

Recovery-Oriented Examples

The standard example runner already includes the session-focused paths relevant to the emergency hardening work:

  • examples/live_session_lifecycle.exs
  • examples/provider_gemini_session_resume.exs

Those examples exercise the same provider-session history and resume seams now exposed through ASM.SessionControl.