Blog

We just shipped wa 2.0 — our CLI tool for managing Git worktrees, VS Code workspaces, and CaseMgr cases from the command line. Here’s what changed and why.

What is wa?

If you juggle multiple Git branches, git worktree is powerful but hard to remember. wa wraps it into simple commands and ties worktrees to VS Code workspaces and aliases for instant navigation.

wa add --bn=feature-x --alias=fx    # Create worktree + branch + alias
cdwa fx                              # Navigate by alias
wa code                              # Open VS Code with saved state
wa upload report.pdf                 # Upload file to linked case
wa mcp cases-list status=active      # Call any MCP tool directly

What’s New in v2.0

• Monorepo migration — wa now lives inside casemgr_umbrella/wa/ alongside the Phoenix app. One repo, one deploy.
• Hyphenated tool names — cases-list instead of cases.list. Breaking change, but required for Claude.ai compatibility.
• Smaller binary — Removed unused dependencies (xlsxir, csv). Down from 2.17MB to 1.95MB.
• Shell functions split — Core functions (cdwa, home, aliases) ship separately from example project functions.

Install

curl -fsSL https://casemgr.systems/cli/install.sh | bash

Requires Erlang/OTP. Works on Linux and macOS. The installer sets up shell functions and offers to add them to your profile automatically.

Full documentation: casemgr.systems/cli

Today marks a milestone for CaseMgr — we shipped per-case context loading, a feature that lets AI agents automatically recover their working context after Claude Code’s context window compaction.

The Problem

When you’re deep in a coding session with Claude Code, the context window eventually fills up. Claude compacts it — summarizing the conversation to free space. But that summary loses the details: which tasks were active, what environment you were debugging in, the client requirements you were referencing.

Most AI memory systems (like Soul v5.0) handle this at session boundaries — loading context at start, saving at end. But they’re blind to mid-session compaction. Your AI agent suddenly doesn’t know what it was working on.

Our Solution: Context Cases

CaseMgr now lets you link cases together as “context.” When compaction happens, a PostCompact hook automatically fires and reloads:

• Your current case’s active tasks and work state
• Notes and knowledge from all linked context cases
• Case descriptions and project context

The key insight: CLAUDE.md is the bootstrap, CaseMgr is the knowledge base. Keep your instruction files small and static. Put everything dynamic into CaseMgr cases and link them as context.

What Else We Shipped This Week

• wa CLI v2.0 — Migrated into the monorepo, consolidated tool names from dots to hyphens for Claude.ai compatibility
• OAuth 2.0 for MCP — Claude.ai can now connect to CaseMgr natively via browser-based OAuth authorization
• Tool consolidation — Reduced from 222 to 184 MCP tools by merging duplicate create/list operations
• Cloudflare Turnstile — Bot protection on login and registration
• PubSub broadcasts — Real-time UI updates when MCP operations modify data
• Case Plan Models documentation — 17 public models with Mermaid diagrams on the website
• Dark theme — All documentation pages match the CLI landing page aesthetic
• Product gating — Billing tools hidden from users without the billing product
• Sticky case header — No more scrolling to see the case name and status

What’s Next

We’re working on making the dual-nav problem go away (Phoenix and WordPress currently serve separate menus), improving the case detail UI with collapsible sections and better mobile support, and expanding the public model library with more CMMN workflow templates that users can instantiate with one click.

If you’re building with AI agents and want persistent, case-driven context management, try CaseMgr — it’s free to get started.