v2.0.0 - Use threads from any directory

The most requested feature since launch: you no longer have to cd into your workspace to use your threads. Resume a thread while working in any repo, and the plugin resolves your workspace automatically.

This unlocks the workflow many of you were already trying to do -- plan in a thread, then switch to a project repo to execute, without losing the context you built up. Two ways to work, one set of threads.

Example

Start in your workspace. Create a thread and think through a design:

cd ~/my-workspace
claude
> create a thread called api-redesign

Over a few sessions you brainstorm the approach, debate trade-offs, log decisions, and save your progress. The thread captures everything: goals, context, decisions made, next steps.

> let's switch from REST to GraphQL for the internal API
> log that decision
> save the thread

A few days later, you're ready to build. Open Claude in the project repo and pick up where you left off:

cd ~/my-project
claude
> resume the api-redesign thread
# → (Using threads from /Users/you/my-workspace)
# Claude now has the thread context AND your repo's code

Claude knows the decisions you made, the trade-offs you considered, and what's next. You're writing code with full context, not starting from scratch.

The first time you do this, the plugin asks where your workspace is and remembers it. That's it.

What's new

• Remote workspace resolution -- Run /ai-workspace:threads from any directory. The plugin checks for a local threads/ folder first, then falls back to your configured default workspace.
• set-workspace command -- Change your default workspace at any time with /ai-workspace:threads set-workspace <path>.
• Restructured README -- Documents two modes of working: from the workspace (brainstorming, planning, architecture) and from a repo (executing with thread context).

Under the hood

• New MCP tools: resolve_workspace and set_default_workspace
• Config persisted via ${CLAUDE_PLUGIN_DATA}
• 11 new tests (21 total)