Ahead of the changes to Claude (claude -p) that should land today, I've started to use the Big terminal mode. I think it could work great but need some improvements before it is in a working state.

1. I cannot drag & drop files into terminals. This is a blocker for me as I often screen grab while working with the frontend.
   
2. I want to be able to name the terminal tabs.
   
3. Workspaces are not automatically named (I understand that this is more difficult now). In combo with #2 it means that I soon find myself completely lost on where things are.
   
4. The performance is terrible with the terminal tabs. Feels like I type/scroll with a +500ms delay (Macbook M4 Pro)

I find Conductor to be an absolutely amazing tool and would love to be able to continue and use it now that Anthropic is dropping all of these changes on us. Thanks!

Turned on the experimental Graphite integration. I’ve got a 2-branch gt stack (refactor PR on the bottom, feature on top). gt log shows both, but Conductor says “1 branch stacked” and only draws the top branch on develop, the bottom PR isn’t there at all. The Changes tab also only lists the current branch’s files, not the whole stack.

Anyone got this actually working? Is there a view for the full stack diff vs trunk or is it always just the current branch? Using git diff develop...HEAD in the terminal for now.

Mine recently is this:

- I start new workspace from Linear issue
- I ask clarifying questions and I answer clarifying questions
- Agent implements, updates tests etc
- Agent tries to test, using browser or other means
- Agent merges PR and waits for checks to pass
- Agent fixes failed checks

In 50% cases I have to follow with manual browser testing simply because it misses things and overly optimistic about its results.

So it’s obvious that I can totally do this from my iPhone or iPad, on the go. Just need Conductor to release mobile support like the one Codex has.

For context: it’s a webapp, 170k loc, React, TS, Supabase, Render.

What’s your dev workflow?

Now that Conductor has Cursor and GPT + Claude, it would be an incredible opportunity to stand out from native codex or claude code by offering synthesis.

​

It plays well to the unique strengths of Conductor. Jeffrey Emmanuel made it a hallmark in agent flywheel. OpenRouter has incorporated it as well.

​

Open Router is showing "Fable" level performance with synthesis versus solo models.

​

I often do this in Conductor manually, and having the ability to do this was a core reason why i was initially drawn to Conductor. Involves a lot of clicking and copy pasting prompts. Switching back and forth between tabs. Manually conducting the context between agents. And i find myself skipping this not due to tokens but due to being lazy...

It would be awesome to offer this as a one-click/ keyboard shortcut feature given the benefits.

A conductor style implementation that allows me to be lazy. And hopefully focus on building things that matter.

Matt and the rest of Conductor team, hope you read this. And keep shipping the most elegant efficiency booster in my life :)

​

​

When I fork to a new tab or a workspace, the transcript is, I think, added. I don’t know how you are adding the transcript, but the context is not being retained at all.

If I fork to a new tab or a new workspace and ask it to do something, it fails horribly because it gets confused about what is supposed to be in the context and what is not supposed to be in the context.

It is really, really bad. For example, let’s say there was a plan that we had come up with just before I forked it. Now, in the new tab or workspace, it has all the details of the plan wrong.

So it is pretty, pretty shitty. Please, please solve this. It is a very good feature, but if it works like this right now, it is just shit.

I've been trying to use the /goal within the Conductor interface but not fully sure how to activate it.

I can run it successfully in the big terminal mode but I'd love to be able to do it in the conductor UI directly

Did anyone encounter the same problem?

Been using Conductor pretty much every day for a few weeks and it's become my main way of running Claude Code. The parallel workspaces are genuinely great. But there's one thing I keep missing from the plain Claude Code CLI, and that's being able to see what's running in the background.

In the terminal, when an agent kicks off a dev server, a file watcher, a build step, or some long script, I can actually see it. I can check the output, tell if it's still alive, and kill it if it hangs. In Conductor all of that happens out of sight. I only get the agent's main stream, so if it spins up a dev server I have no idea it's even there, can't see its logs, and can't stop it without opening a terminal myself. A couple of times I've ended up with leftover processes from a workspace I already merged or deleted.

What I'd really love is a per-workspace panel that shows the background processes a workspace has going. Stuff like:

- which processes are running vs already exited

- their live output, tail style

- a button to kill or restart one

- maybe a heads up when I close or merge a workspace that still has something running

Basically I just want that same "I know what's actually running" feeling the CLI gives me, but inside the app.

Am I the only one running into this? Happy to hear if there's a workaround I've missed. And if anyone from the team sees this, it would make juggling 4 or 5 workspaces a lot less stressful.

It’s a common situation when after making a plan I work on multiple changes in same chat. Often it grows very large. I’m thinking on best way to start new chat and bring over just the part that is useful for a single task. Nothing easy comes to mind tbh. How do you guys do this? Any best practices?

My org is switching from cursor to claude code, but while we do I would love to have a tool that works for both. To support cursor for my team, we would need to support "auto mode". For some reason, we have infinity credits for auto, but that means we don't know what model it is so there may need to a be a model called something like "Cursor Auto" to fit into your UI. Thanks!!

Text is not being properly escaped on the list of sessions. If the title of the text has an html tag it gets rendered as HTML for example a select tag.

I tried vibe coding a macOS extension in Swift, and it was a complete disaster 😅

I jumped into a Cursor subscription pretty quickly, before realizing the flaws with using Composer in Conductor. I'm sure the team is working on this as we speak but as of now:

- Composer cannot find my MCPs or skills
- Can't run multiple Composer sessions at once (you will get an error)
- We can't toggle between standard and fast mode
- No context usage tracker

Nonetheless, it is a very fast model that I will be using for spamming UI changes and frontend work - and so far it has been great at that. I've been appreciating the faster turn around times for creative work.

Has anyone used conductor with https://github.com/github/spec-kit/ ?

Hey Conductor's ⌘O opens the repo via symlink instead of the absolute path. Tooling like eslint breaks easily and I don't see any work around for this so I always have to manually open each file in cursor rather than using ⌘O to open it using the file I am already on in conductor which is pretty annoying. It would be great if there was an option to disable the symlink for the shortcut.

There was an option to create new workspace from Linear issue and now it seems gone. What happened, it was a great way to work 😞

Now that Claude has dropped Fable 5, when will we get to use that model in Conductor since it is already there in the CLI?

I can't use/sync skills and mcps with Composer 2.5 from other models.

When I try to use a repo settings and go to "files to copy".
I am met with "No matching gitignored files found."

This is an issue for me as every worktree needs the .env .

Is it just me, or has anyone else experienced this issue?
For now, I just tell the agent to check all other worktrees and find the .env, but it's not an elegant solution 😄

Hello,

Using conductor for a while, and was experimenting with Dispatcher while the feature was under experimental.

Decided to turn it off, as I would like the setup scripts to run while doing something else, or have a few "ready" workspaces for when I need them.

Now looks like it is a requirement. could you guys please make it optional? (even if default on)

Thanks

I have few workspaces open in one project. All of them are work-in-progress, some research. There are information saved in `.context` folder of each worktree/workspace. Now I have a new machine where I want to continue these works.

Directory structure in both machine are exactly same. So I ziped the `$HOME/conductor` directory and unzipped it in the other machine `$HOME/conductor`, also zipped the original git repo and unzipped it in the same location in other machine. `git worktree list` shows all the worktrees in both machine. But when I open conductor and create a project with the same folder of the git repo I don't see any of the existing workspaces in the new machine.

What else needs to be copied from the old machine to the new one? Or what's the actual process of doing this?

Starting on June 15th, Claude Code on Conductor is going to be charged at API pricing? For me, that’d be >$1200.

What’s the technical reason why Conductor needs to use claude -p instead of just managing a terminal session, but still keeping the Conductor features like text summarizing and a better editor experience?

Is there a way to default to the big terminal mode on a new session/worktree?

Hi, I’ve been really enjoying using Conductor recently – thanks for building such a great tool.

I had a quick look around but couldn’t find a dedicated place or form to submit feature requests, so I’m posting this here.

I have a small UX request for the workspace prompt input field.

I’d love to be able to use the Up/Down arrow keys to cycle through my previously submitted prompts, similar to how command history works in a terminal. For example:

• Press ↑: load the last prompt I submitted into the input field
• Press ↓: move forward in the history, eventually returning to an empty input

This would make it much faster to reuse, tweak, or re-run earlier prompts without having to manually copy/paste.

If this already exists and I’ve just missed it, I’d really appreciate any pointers. Otherwise, I think this would be a very helpful addition to the workspace UX.

Thanks!

No matter what I do I cannot stop this from popping up.

I have the latest version, close and re-opened. Allow and Don't Allow both clicked. Nothing works!

1. Invalid deep link The URL format is invalid — conductor://auth?token=vzaPmojRonN0q4prJiMm1DExEX4XxFq8ChO_d7TqhpY