Local data

The CLI keeps what it remembers in one per-user database in your operating system's application data directory. It is never stored in a workspace. Conversations are kept as append-only session files.

Find past runsCopy Anchor Link

rolit runs                       # runs in this directory
rolit runs --all                 # runs from every directory
rolit runs --kind job            # filter by kind
rolit runs search "auth since:7d"

Search matches titles, prompts, and touched files. It also supports dir:, kind:, model:, since:7d, and is:interrupted.

Manage a run with rolit runs rename, archive, unarchive, or delete. Deleting removes the run's database rows and keeps the conversation file.

In an interactive chat, /resume opens a searchable list of past conversations.

Check usageCopy Anchor Link

rolit usage --by model --since 30d

--by accepts day (default), model, dir, or purpose. This shows token usage recorded on this device. For credits, see rolit ledger and Credits.

Workspace filesCopy Anchor Link

.rolit/config.json in a workspace holds preferences and tool settings. It never holds login tokens. Share settings with your team by exporting them to .rolit/shared/:

rolit config export --shared seo

Shared files are read-only overlays and must not contain secrets.

Database maintenanceCopy Anchor Link

rolit db path      # show where the database is
rolit db check     # verify it
rolit db backup backup.db

Other subcommands include gc, vacuum, export, reindex, and rotate-key. Run rolit db --help for details.

Sign-in storageCopy Anchor Link

Access and refresh tokens are encrypted in the database, with an owner-only key file beside it. The CLI never uses your OS keychain or asks for an OS password.