Skip to content

Workspace & Configuration

This guide explains how Seev stores data, how to configure tracked emails, and which environment variables and paths control behavior.

Defaults at a glance

  • Workspace directory: you choose (e.g., ~/seev-workspace)
  • Worklog file: WORKLOG.md in your workspace
  • Database: db.sqlite3 (or seev.sqlite3) in your workspace
  • Config file: ~/.config/seev/seev.toml

Tracked emails (who you are in git)

Seev needs your git author emails to filter commits. Resolution order:

  1. SEEV_TRACK_EMAILS environment variable (comma-separated)
  2. seev.toml at one of:
  3. ./seev.toml
  4. ~/.config/seev/seev.toml
  5. ~/.seev.toml
  6. Git fallback: git config --get user.email then git config --get user.name

Precedence gotcha

The environment variable takes precedence over the config file for the current process. If values look wrong, check SEEV_TRACK_EMAILS first, then your seev.toml.

Configure via environment

export SEEV_TRACK_EMAILS="[email protected],[email protected],[email protected]"

Create or edit ~/.config/seev/seev.toml:

# Seev Configuration
track_emails = [
  "[email protected]",
  "[email protected]",
  "[email protected]",
]

Tip

You can point your MCP session at specific emails by setting the env var in your shell before launching the client.

Workspace paths and env vars

The installer creates sensible defaults, but you can override at runtime:

  • SEEV_MD_PATH — path to your worklog Markdown (default: <workspace>/WORKLOG.md)
  • SEEV_DB_PATH — path to the sqlite database (default: <workspace>/db.sqlite3)
  • SEEV_TRACK_EMAILS — comma-separated emails (overrides file config for the process)

Example:

export SEEV_MD_PATH=~/seev-workspace/WORKLOG.md
export SEEV_DB_PATH=~/seev-workspace/db.sqlite3
export SEEV_TRACK_EMAILS="[email protected],[email protected]"

Verifying configuration with MCP tools

From your assistant, ask it to call these tools:

/get_tracked_email_config

Expected: a snapshot of where emails were resolved from and the current values.

/configure_tracked_emails method="env" emails=["[email protected]","[email protected]"]

Expected: the process env is updated for the MCP server.

Notes for deterministic tests

When writing tests or debugging:

  • Unset the env var to exercise file/git fallbacks
  • Prefer patching config helpers over invoking git directly
  • Use a temporary directory for any file outputs