Feature Request: Ability to change working directory during Claude session

[CharlonTank]

Feature Description

I would like the ability to change the working directory during an active Claude session. Currently, Claude is bound to the directory where it was initially spawned, which limits flexibility when working across multiple projects.

Use Case

Here's a common workflow where this would be helpful:

1. I clone a repository to understand how to use it
2. I launch Claude in that cloned repo to understand the project context
3. After understanding the project, I want to switch to my own project to apply what I've learned
4. Currently, I'm limited to either:
   • Making remote modifications using relative paths (e.g., ../my-project/file.js)
   • Creating a context file in the cloned repo, then starting a new Claude session in my project to read that file

Proposed Solution

Add a command or feature that allows changing the working directory within an active Claude session, similar to cd in a shell. This would allow users to:

• Maintain context from one project while working in another
• Navigate between related projects without losing conversation history
• Avoid the overhead of starting new sessions or using workarounds

Benefits

• Improved workflow flexibility
• Better context preservation across projects
• Reduced need for workarounds like context files or relative path modifications
• More natural navigation similar to traditional terminal usage

This feature would make Claude Code more versatile for developers who frequently work across multiple related projects or need to reference one codebase while working in another.

[ashwins01]

why not start the claude session from a parent directory which will contain both your project repo's ? im assuming your request was not developed so claude wouldn't go rogue and make changes outside its working directory when its least expected to.

[CharlonTank]

why not start the claude session from a parent directory which will contain both your project repo's ? im assuming your request was not developed so claude wouldn't go rogue and make changes outside its working directory when its least expected to.

I'm working on a compiler that has to live in ~/dev/projects
Sometime I want to go into a real app using my compiler.
The apps I develop are not in ~/dev/projects.

Sometime I'm working on something and I was not really aware it could benefit another project for example.

[danrasmuson]

It would be a great convenience to be able to run /cd as a claude command and change the working directory. Its fine if another permission screen comes up. I use claude code for a lot of none pwd related tasks and so when I do require a specific pwd it would be great to have this convenience.

[mohhef]

actually what i recently needed is -

i moved my current project to another directory and was no longer able to continue the session because it seems sessions operate on specific paths.

is there a way to link a session i had to the new directory

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[danrasmuson]

Commenting here to keep the issue open.

[kaxing]

bumping this issue; and jfyi, the moving steps of this script works pretty well: https://github.com/skydiver/claude-code-project-mover

[tremo1]

bump, would be a nice feature to avoid restarting session to move to another dir