DEV Community

chowyu
chowyu

Posted on Fully Autonomous

How AIClaw 3.12.15 Keeps CLI Profiles Separate from the Desktop App

A terminal agent needs a model and a place to save conversations. If it inherits both from a desktop app, changing providers for a shell experiment can affect the desktop, and picking up a terminal session depends on how the desktop stores its history. AIClaw v3.12.15 ships a standalone aiclaw binary with its own defaults for both. Release and CLI downloads

Give the terminal its own profile

The CLI defaults to ~/.aiclaw/cli. It keeps the provider database and configuration there, along with its session store. --data-home selects another profile so you can keep a separate provider, default model, and history for an experiment. --cwd selects the workspace within that profile. resume --last looks for a session in the selected workspace, and resume SESSION_ID selects a stored session directly. CLI configuration · Terminal CLI guide

The terminal starts the Go agent kernel in the same process and talks to it over JSON-RPC through net.Pipe. It starts the kernel in models-only mode, which skips desktop plugins and channels. You can explicitly pass --app-db to reuse the desktop model database. Session storage still follows the CLI profile. RPC connection · Kernel startup

Run once, then pick up the session

After configuring a provider and default model in a profile, run these commands from the same project directory:

aiclaw exec "Summarize the current project" --json
aiclaw resume --last
Enter fullscreen mode Exit fullscreen mode

exec --json emits one JSON event per line on stdout, so a script can process events as they arrive. If a turn requests approval or asks for input, exec exits with an error. Use the interactive terminal to answer those prompts. Turn handling

What the tests cover

The regression tests use a local fixture model endpoint to exercise JSON output, session persistence and resume, profile isolation, approval, and interruption. The release workflow passed for the tagged commit. Those tests establish CLI behavior against a controlled endpoint. Compatibility with a particular hosted model depends on its API. CLI tests · Release workflow

Top comments (0)