Personal Workspace Configuration

Personal Workspace Configuration

Configure the smallest surface that improves your daily work. Personal settings should remain portable, reviewable, and easy to reverse.

A useful order

1. Confirm hooks and one provider work with defaults.
2. Set display preferences such as theme, locale, and default filters.
3. Add pricing overrides only when the built-in mapping does not match your use.
4. Configure alerts after you understand normal activity.
5. Add remote sources, MCP, plugins, or config tooling one at a time.

Changing several layers at once makes it hard to identify which setting caused a regression.

Locale and display settings

Choose a supported locale in the UI and verify the navigation, settings, dialogs, alerts, and configuration explorer. A missing translation should fall back safely, but report the exact screen and key so parity can be corrected.

Display filters do not delete data. If sessions seem missing, clear the date, project, provider, source, and status filters before changing ingestion.

Project identity

Projects can appear different when paths differ across hosts, containers, WSL, or symbolic links. Use consistent working directories where possible and include the source filter when comparing machines.

Secrets and local files

• Prefer file-backed secret variables where supported.
• Never commit .env, tokens, SQLite databases, transcripts, or provider credentials.
• Restrict permissions on configuration and backup files.
• Treat transcript contents as sensitive project data.

Before experimenting

Export or copy a verified backup, note the current version, and make one reversible change. For settings that can mutate provider configuration, follow Safe Config Explorer Usage.

For the full configuration reference, use the repository README.