Rexa DocsReference
Data and logs
Where Rexa keeps settings, state and logs, and how to collect logs for a bug report.
Folders
| Folder | Holds |
|---|---|
~/.config/rexa/ |
Files you edit: settings.json, keymap.json, extension switches, installed extensions. |
~/Library/Application Support/rexa/ |
State Rexa manages: open projects and layout, caches, downloads, the background terminal socket. |
~/Library/Logs/rexa/ |
rexa.log, and one log per language server in lsp/. |
~/Library/Caches/deno |
Language servers and tools Rexa runs through its bundled Deno. |
~/.local/bin/rexa |
The rexa command, linked into the app. |
/Applications/Rexa.app |
The app. Updates leave the previous version as Rexa.app.backup. |
Files under ~/Library/Application Support/rexa/ open read-only in Rexa’s editor. Deleting that folder while Rexa is closed resets your projects and layout; your settings and keymap stay.
Rexa also writes hooks and skill links into each agent’s config folder. Supported agents lists them.
Logs
The main log is ~/Library/Logs/rexa/rexa.log. The app, the rexa command and the background terminal process all write to it. Open it in Console.app, or follow it:
tail -f ~/Library/Logs/rexa/rexa.logThe log records paths but not prompts, terminal contents or tokens. It is not rotated; delete it to start fresh.
More detail
Quit Rexa, then start it with a log level:
RUST_LOG=debug /Applications/Rexa.app/Contents/MacOS/rexaLevels are error, warn, info, debug and trace. Per-module filters are not supported. REXA_LSP_TRACE=1 adds every language server message.
For git and GitHub calls, run rexa: open git log stream from the palette.
Report a bug
Include:
- The output of
rexa version. ~/Library/Logs/rexa/rexa.log, pluslsp/*.logfor language server problems.- For agent problems,
rexa extension logs --level warn --count 500.