aXism

Agent Interactive Session Manager. Browse, open, and clean up the chat sessions your coding agents keep on disk, across every project on your machine.

aXism, a tool by aXistem, is a terminal app plus a command-line tool. It finds every session from Claude Code, Cursor, Hermes, and OpenCode, groups them by project, and lets you open, stop, rename, move, or delete them without digging through hidden folders. It runs on Linux and macOS.

Why use it

• See everything in one place. Every project and session, with title, size, last update, and whether it is running right now.
• Clean up safely. Deleting a session removes all of its files (transcripts, caches, job records) and nothing else. Credentials, settings, skills, plugins, and project memory are never touched. Every delete asks first.
• Keep sessions with their project. Renamed or moved a project folder? Move its sessions to the new path so your agent finds them again.
• Jump back in. Open any session in its own agent with one key.

Install

Needs Python 3.12 or newer.

uv tool install axism
# or
pipx install axism

Make sure ~/.local/bin is on your PATH, then check it works with axism --version.

To upgrade, run uv tool upgrade axism or pipx upgrade axism. If the version does not change, the tool was installed from a pinned file instead of PyPI; reinstall with uv tool install --force axism.

First steps

axism            # open the app
axism list       # print every session, grouped by project
axism providers  # show which agents are enabled and where aXism looks for them

The app has three panes: projects, sessions, and details. Move with the arrow keys or vim keys, and press ? to see every key.

Using the app

Capital letters do the same as lowercase, except G (last row) and T (next theme). The footer follows the pane you are in: keys that do not apply there are dimmed, and pressing one tells you why it does nothing.

The details pane shows the session's facts first, then its last prompt and last reply. Enter on the details pane opens the reader with the full conversation (text turns only); Esc or q returns. Dialogs fit small terminals and scroll when the text is longer than the window.

Terminals narrower than 70 columns hide the details pane so projects and sessions both fit. Keys act on the pane you are in. For example, d in the projects pane deletes whole projects, while d in the sessions pane deletes sessions. If items are marked, the action applies to all of them. If an agent cannot do something, aXism tells you instead of doing half the job.

Moving. Press m, then pick an existing project or type a folder path. Within the same agent, aXism moves the session files and updates their recorded paths. It creates the destination folder if needed, but it never moves your source code. Stop running sessions before moving them. Moving a session into another agent's project copies the conversation text and keeps the original.

Settings. Press , to choose which agents to include (Space), set the default agent for CLI commands (* makes the highlighted one the default, Enter saves), and point an agent at a custom config folder. Each agent shows its status (sessions found, folder missing or unreadable, or no sessions and its command not on PATH), worked out in the background so Settings opens at once; saving warns about a configured folder that does not exist (y saves anyway, n cancels). Enabling an agent never changes the default, and a folder you type is stored as an absolute path. When the run was started with --provider or --config-dir, Settings says so in one line. On first launch aXism switches on the agents it finds on the machine (a data folder with content, or the agent's command on your PATH); agents added by a later update are detected once, and your own choices are kept. Settings are saved in ~/.config/axism/settings.json (or under $AXISM_CONFIG_DIR); a settings file that cannot be read, or whose providers entry has the wrong shape, is left untouched (Settings shows why and saves nothing until it is fixed or removed and aXism restarted), and the detected agents are used for that run only.

Command line

Everything the app does is also available as a command, which is handy for scripts. Run axism <command> --help for all options.

A few things worth knowing:

• Session IDs can be shortened to any unique prefix.
• delete, delete-project, purge-project, and stop only show a preview until you add --yes. delete and delete-project exit 1 after that bare preview, 0 after an explicit --dry-run or a --yes run that completed, 1 as well when a --yes run reported an aborted, refused or failed step, and 2 whenever the plan is blocked (not found, or a live session without --force). move and export take --dry-run to preview; move refuses sessions that are running unless you pass --force.
• axism providers marks the CLI default agent with * and prints a legend line below the list.
• list covers every enabled agent. Other commands use the default agent (Claude Code unless you change it), so add --provider cursor, --provider hermes, or --provider opencode to work on those sessions.

axism list --project /home/alice/src/demo
axism delete 3f2a9c1e --dry-run
axism delete 3f2a9c1e --yes
axism move --project /home/alice/src/demo --to /home/alice/src/demo-v2
axism --provider hermes show <session-id>

Supported agents

You can also set a folder per agent in Settings, or pass --config-dir on the command line. A custom OpenCode data folder must be named opencode; aXism lists any folder, but changes to sessions in a folder with another name are refused.

All four agents support open, stop, rename, and delete. Differences:

• Stop on Claude Code applies to background jobs (via claude stop). On Cursor and Hermes it ends the agent process. On OpenCode it interrupts the running session and closes any OpenCode window that has it open; OpenCode's background service itself is never stopped.
• Move works for Claude Code, Cursor, and OpenCode. Moving OpenCode sessions needs OpenCode's background service running on the default data folder (opencode service start); without it, or with a custom data folder, the move is refused before anything is stopped or changed. Hermes sessions can be copied to another agent but not moved.
• Project memory merge is Claude Code only: moving a project into another one also merges its memory/ folder.
• Project purge (purge-project) is Claude Code only.
• Hermes changes go through the hermes command, and only regular chat sessions are listed. Profiles, kanban boards, project workspaces, messaging, and cron sessions are left alone.
• Cursor desktop Composer history is not managed.
• OpenCode keeps its sessions in one database, opencode.db, owned by OpenCode's server. aXism reads that database for listing (without starting anything) and makes every change through OpenCode itself: the background service when it is running, otherwise a private OpenCode server for that one command. Sub-agent sessions are not listed on their own: they count toward their parent session's size, move and delete with it, and make it count as running while one of them is running or open; stopping the parent interrupts the whole family. Copying a session into OpenCode uses opencode session import and creates a session with a new id. Only OpenCode 2 is supported; for any other database layout axism providers shows one line saying so and nothing is listed.

What is never deleted

Deleting a session never removes credentials (auth.json, .credentials.json, .env), agent config (settings.json, config.yaml, cli-config.json), skills, plugins, daemon keys, project memory/, or an agent's whole database (such as Hermes state.db or OpenCode opencode.db).

Deleting a project removes every session in it along with the agent's folder for that project. For Claude Code that includes the project's memory/ unless you pass --keep-memory; in the app, the project delete dialog states what happens to memory/ and m toggles keeping it (off by default).

Development

From a clone of this repository:

uv sync --extra dev
uv run pytest
./scripts/install.sh   # install your local checkout as the axism command

See AGENTS.md for contributor rules and the release process, and CHANGELOG.md for what changed in each version.

License

MIT © aXistem