Connect either provider or both in Settings → Connections. Lunavect checks each provider separately: finding the client, confirming sign-in, configuring local events and receiving fresh usage data are different steps.
The guide reuses an existing installation and sign-in. If a step is already complete, it moves to the next one.
/hooks in Codex and approve the Lunavect commands when requested. A configuration file alone does not prove that events have arrived./usage launch completed. Run a task to check session events and compare available quotas with the official client.The guide checks progress while open. If an external window was closed or setup did not finish, retry the incomplete step. It does not need to replace a working sign-in or reinstall existing handlers just because a quota request failed.
| Provider | Usage limits | Session state and titles |
|---|---|---|
| Claude Code | The official CLI’s /usage output and rate_limits delivered to the status-line command |
Local lifecycle hooks, available client session information and title metadata |
| Codex | account/rateLimits/read through the local Codex app-server |
Available runtime state, lifecycle hooks and local session metadata; log-based fallback where needed |
Claude status-line quotas have a receipt time but no server observation timestamp. They remain marked as saved observations; recent /usage results take precedence. Recognized repeated status-line payloads do not advance their receipt time, and a lower value for the same limit window from another session (an idle session’s older response, re-sent when Claude re-runs its status line) does not replace a newer observation. Automatic refreshes after wake or network recovery reuse a current verified cache, while an explicit refresh can request new data.
Local catalog entries and titles are not evidence that a session is working. Fallback readers depend on client file formats, so a client update can affect detection. See sessions for state handling and navigation limits.
Default client configuration files are ~/.claude/settings.json and ~/.codex/hooks.json. Lunavect respects CLAUDE_CONFIG_DIR and CODEX_HOME when set in the app’s environment. Advanced connection settings provide a manual Codex executable path when automatic discovery is insufficient.
Hooks invoke the bundled LunavectHook helper. It keeps session identity, project, client, state, tool name and timestamps, not the prompt or tool arguments. The Claude status-line handler stores quota values rather than the full input payload. Setup launchers contain commands and paths, not copied authentication tokens.
For all storage paths, backups, permissions and network behavior, see Privacy and permissions.
Disconnect a provider in Settings → Connections before removing Lunavect. This removes its event handlers and restores the saved previous Claude status line when applicable. Unrelated client settings and handlers remain in place.
If cleanup fails, the app reports the error; resolve it before deleting the app. Disconnecting does not sign you out of the official client, delete its conversations or erase Lunavect’s existing history. Removing only the app does not undo handler configuration. See uninstalling.
These references describe the clients’ interfaces, not a certification or endorsement of Lunavect. Current installation and compatibility evidence is recorded in verification.
Lunavect 0.2.3 includes local companions for VS Code and JetBrains 2026.2. Install the companion from Settings → Connections → Sessions in editors to select the existing Claude or Codex terminal tab. See IDE session setup and compatibility, including the separate limits for provider panels and remote workspaces.