/plan). Approve the
plan when prompted (y, yes, or approve) to execute immediately — no
separate /run is required. Use /run <goal> to re-execute the last approved
plan or run a goal without planning first. /plan calls the LLM in plan-only
mode and prints a structured plan (summary, files, steps) without making
changes. When the LLM is unavailable, Arka falls back to a local
repository-aware plan.
Test commands
/test runs the repo-appropriate test command deterministically (pytest, npm
test, cargo test, etc., detected via repo health). Optional path scopes the run,
e.g. /test tests/test_foo.py. Output is labeled Test run (read-only).
When failures are detected, Arka prints how many failed and runs Fix pass
1/1 — one writable goal-agent pass — then re-runs tests read-only to show the
result. Use /test --no-fix to skip the automatic repair attempt.
/run tests lets the readonly goal agent pick a strategy — full pytest, a
focused module, arka ci --changed, or a repo_health-detected runner — with
the same one auto-fix pass after readonly failures. Add --no-fix to disable
auto-repair, or --fix to allow the agent to edit files from the start (for
another explicit fix round after a failed auto-fix, or multi-pass repair).
Example flow after /test with one failing test:
3D scaffold
/scaffold 3d writes a React + Vite + Three.js space scene in an empty project.
Arka then runs npm install automatically for this trusted template only
(pinned packages from the scaffold manifest — not arbitrary shell from the goal
agent). Add --run to start the Vite dev server after install, or answer y when
prompted.
/plan use the same scaffold path and post-install
steps. If the network is offline, scaffold files are still created and Arka prints
an honest failure message with manual next steps.
/status shows the current branch, dirty file count, and whether the code
project is initialized. /ci runs fast changed-only gates; /review summarizes
staged changes. /history lists commands from the current session; /clear
clears the screen and resets session state.
The coding agent prints a completion/failure summary after execution and suggests
arka ci --changed for incremental verification.
Coding requests are language-agnostic: mention the language, framework, or file
extension in your request and Arka will use the repository’s existing toolchain.
Voice input and output can also use any Edge TTS-supported BCP-47 language: