[FEATURE] Add support for context management

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

It is usual for developers to be working in several issues/tasks at the same time. It would be great to include some context management functionality so you can have different conversations at the same time, and switch to the conversation related with the task at hand. I asked Claude Code itself about this functionality and the proposed workaround is to have a different session for each task (meaning a different terminal window/tab for each ongoing task):

% ok, let's say I'm working on two/three different tasks at the same time, is there any way to manage context to switch to these different tasks, so I can access the history of each of them

separately?

⏺ Currently, Claude Code doesn't have built-in support for multiple parallel contexts or "workspaces" within a single session. What you can do today: 1. Run multiple Claude Code instances - Open separate terminal windows/tabs - Run claude in each one - Each instance maintains its own independent conversation history - Switch between terminals to switch tasks 2. Use the /clear command - Clears the current conversation context - Useful when switching tasks within the same terminal - Downside: you lose the previous task's context entirely 3. Summarize before switching - Before switching tasks, ask me to summarize the current state - Copy that summary somewhere (notes, a file, etc.) - When you return, paste the summary to restore context quickly Practical approach for 2-3 parallel tasks: Open 2-3 terminal windows, each running claude: Terminal 1: Ads investigation (current) Terminal 2: Feature X Terminal 3: Bug fix Y This way each conversation stays focused and retains its own history. You can even name your terminal tabs to keep track. Future possibilities You could suggest this as a feature request at https://github.com/anthropics/claude-code/issues — something like session/workspace management or named contexts would be useful for exactly your use case.

Proposed Solution

It would be great to have some command (/context, /issue or /task come to mid) that would show a list of current contexts, and let you select an existing one or create a new one, being able to name them so you can for example make a reference to a ticket/issue in your ticketing system.

Alternative Solutions

The proposed workaround by Claude itself is to use several instances, one for each ongoing tasks. I haven't tried ti yet, but I will do it as soon as I finish this feature request.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. I'm working on issue PRJ-1001
2. I send the issue to be tested by QA
3. I switch to issue PRJ-1002, starting a new conversation with Claude Code
4. QA reaches back with a detected problem
5. I switch back to the PRJ-1001 conversation, at the point I left it without losing any context

Additional Context

_No response_