Config – CaseMgr

Configuration

Workareas is configured through environment variables, making it easy to customize per-machine.

Environment Variables

Variable	Description	Default
`WORKAREAS_DIR`	Base directory for Workareas data	`~/.workareas`
`WORKAREAS_WORKSPACE_DIR`	Directory for VS Code workspace files	`{WORKAREAS_DIR}/workspaces`
`CASEMGR_URL`	CaseMgr MCP server URL	`http://167.99.111.159:4000/mcp`
`CASEMGR_FALLBACK`	Set to `cubdb` to use local storage	(not set = use CaseMgr)

Configuration Commands

# View current configuration
wa ls cfg

# Output:
# Configuration (derived from environment):
#   WORKAREAS_DIR:           /home/user/.workareas
#   WORKAREAS_WORKSPACE_DIR: /home/user/.workareas/workspaces

Backend Selection

Workareas uses CaseMgr by default. To use local CubDB storage instead:

# Use CubDB for this command
CASEMGR_FALLBACK=cubdb wa ls

# Or set permanently in .bashrc
export CASEMGR_FALLBACK=cubdb

Custom CaseMgr Server

To use a local or custom CaseMgr server:

# Use local development server
export CASEMGR_URL=http://localhost:4000/mcp

# Or use a custom deployment
export CASEMGR_URL=https://your-server.com/mcp

Data Migration

To migrate data between backends or machines:

# Export from CubDB
CASEMGR_FALLBACK=cubdb wa export wa > workareas.json

# Import to CaseMgr
wa import wa --file=workareas.json

# Export from CaseMgr (all machines)
wa export wa --all > full_backup.json

Directory Structure

~/.workareas/
├── workspaces/              # VS Code workspace files
│   ├── project-a.code-workspace
│   ├── project-b.code-workspace
│   └── ...
└── workareas.cubdb/         # CubDB database (if using fallback)
    └── ...