Using flamel

Sessions

A session is one provider-backed agent process with its own working directory, context, and history. You can run Claude Code, Codex, and other supported CLIs in parallel.

What's in a session

Each session has a name, a working directory on the server, a provider, and a selected model. When you open it, flamel spawns the selected provider CLI pointed at that directory. Everything the agent reads, writes, and executes happens relative to that path.

Sessions are isolated from each other — separate processes, separate context windows, no shared state. Running four sessions on four different repos is the same cost as running one.

History

Every message is stored in SQLite on your server. Close the browser, come back later, and the conversation is exactly where you left it. History is scoped per session and never leaves your server.

Parallel sessions

Open multiple sessions from the tab bar. Each runs independently. Useful for working across repos, running long tasks in the background while working on something else, or comparing approaches side-by-side.

Stopping a session

Closing the browser tab doesn't kill the session — it keeps running on the server. Use the stop button in the UI to actually terminate the provider process. History is retained either way.