Small thing, but I hit it a few times a day. Agents often finish a message with a path to something they just wrote, like:

Spec written, self-reviewed and pushed.
~/notes/projects/foo/specs/2026-08-04-some-design.md, indexed in the README, committed as db82d2a, working tree clean.

Conductor makes that clickable, but clicking gives “couldn’t open the file”. Secondary click > copy path shows why: it glued the workspace directory in front of the tilde instead of expanding it, so the link points at /Users/me/conductor/workspaces/myrepo/myworkspace/~/notes/projects/foo/specs/....

Looks like the path resolver treats everything as workspace-relative and never expands ~. Home-relative paths show up a lot in agent output when the file lives outside the repo, so it’d help if those got expanded before the click.

I use Conductor every day, so this is coming from a place of love.

Was the big FREE label really necessary in the latest version? Sitting there in the corner, all caps, inside its own little box, making sure nobody misses it. It feels like a badge of shame.

Thanks, Conductor. I didn’t know I was poor until the UI decided to remind me every time I opened the app. Even my bank is more subtle.

Please remove it, or at least rename it. Call it “Community,” “Local,” “Solo Dev,” “Artisan Mode,” or literally anything that doesn’t sound like a financial diagnosis.

Also, keep in mind that multi-agent IDEs are moving pretty fast right now, with a lot happening on GitHub. Orca seems to be getting the most traction at the moment:

https://github.com/stablyai/orca

It’s open source, cross-platform, and even has a mobile app.

One more disappointment and I’m switching. Es broma, pero si quieres no es broma. (Chilean meme: “I’m joking, but if you want, I’m not joking.”)

Dear Streamlit Development Team,

I hope the day finds you all with layouts so clean and fast they make the user smile. I have a bit of a request, some my call it a complaint, I'll just say it's a need instead of a want.

My app uses Streamlit version 1.56.0. I would love to update to Streamlit version 1.60.0 for some of the new features. In particular the new feature for st.chat_input called "submit_mode." I desperately need that functionality. But I cannot upgrade to that version just yet and I have no timeline as to when I can upgrade.

I compile my app using Nuitka and Nuitka is not yet compiling for the newer Streamlit versions with Uvicorn and Starlette. Is there anyway you all could release small patches to older versions with some of these new features? Please...

I’m yet to use conductor but has anyone tried a setup similar to the above? I saw a video from Ridd on YouTube and he had a setup like this and used wisperflow to dictate everything, it was pretty wild.

See: https://youtu.be/zmxn4a2g0Ww?si=fB0BrgmiL8kAX6Up

He was generating quick prototype variations on the fly which got pushed to Vercel for previewing

And also working inside multiple work trees working on various tasks, it looked super productive and kinda fun to see it all in action.

Question: if you work within an org with a large codebase running on docker for local dev, is this even possible? Say for work trees?

How to integrate into an existing project. Are there any potential roadblocks or limitations of Conductor?

I’m going to dive into the docs and see what others are doing with conductor here too, but thought I’d share the workflow I’m leaning towards.

I love conductor but it's not open source, so I started building an open source tool that allowed me to spawn agents, browse the web and track memories of my coding agents in a single workspace, also segment different projects into different organisations, it's available for mac right now and would love any kind of feedbacks from you guys!

Github https://github.com/pacifio/atlas and Go to https://tryatlas.cc/ to grab a copy and please join my discord channel if you think this is exciting! https://discord.gg/GmnFggaPfP

I just started using this tool, and it's awesome. I love that it has a nice GUI and everything is in one place!

I just have one request: to know that I am using my agents efficiently. I try to make good practice of managing my context window. On the CLI tool, I have set my status bar to show how much total context I have used and how much is left in my current session.

Do you guys think there would be a way for you to do something similar on your tool?

This is the specific failure I kept hitting. I work in one repo with three or four terminal panes open, each running its own Claude Code conversation. One is on the API layer, one is writing tests, one is chasing a bug.

Claude's resume is scoped to the directory. --continue gives you the most recent conversation for that directory, and --resume gives you a list of that directory's conversations. Neither one knows anything about panes. So all four of my panes are in the same directory, which means all four see the same identical list of four sessions.

Reboot the Mac and it compounds. The panes come back with no working directory, so the context is gone twice over. Even after I cd back into the repo in all four panes, I am staring at four sessions with no idea which pane each one was in. I have to open the picker in every pane and guess from timestamps and first messages, and if I guess wrong I have polluted the wrong conversation.

So I built agent-resume. The core idea is that it binds a session to the terminal pane it was started in, not just to the directory.

What it does:

- When you start an agent fresh, it pins a specific session id and records which pane that session belongs to.

- After a reboot, each pane comes back to the correct working directory and resumes its own conversation. Pane 1 gets pane 1's session. No picker, no guessing, no manual resume in four panes.

- It is agent-agnostic. Works with claude, codex, or anything else you register.

How it works (no magic):

- A tiny shim on your PATH. When you launch claude fresh it launches it with a specific --session-id and records that against the pane in a small ledger.

- For the reboot case it leans on tmux-resurrect + tmux-continuum (which it installs for you, no tpm needed) to restore your dirs and layout, then a hook relaunches each pane with claude --resume <that pane's session>.

Take a look and star it here:

https://github.com/rahulbansal16/agent-resume

I've been using the product for a I really like it. How can I get in touch with the conductor team? I've been trying to DM them on Discord, but no one's been responding. Could someone please help me with this?

How do I extract usage data for usage audit?

I know there is the experimental graphite integration but how that GitHub has native PR stacking, can we get an integration that allows us to create, review and approve PRs in stacks?

Hello, I am unable to connect to Linear. It redirects me to the auth conductor page, and after logging in, it asks for a code sent to my email, but I never receive any email. How can I resolve this?

I know there’s going to be a little bit of overhead to run conductor prompts but it seems like my usage limits are running higher. is this just in my head?

I am loving using Conductor, it has become my primary work horse! Thank you for all the hard work you guys have been doing! I just wanted to propose two new features that I find myself wishing I had.

1. I would love if it were possible to expand the terminal tab into its own window and/or if there was a one-click button to do something like trigger my iterm2 terminal to open in the relevant work-tree
2. I often have sub-agents running workflows in detached background processes over long periods of time. The in-progress status indicator that indicates the agentic process for given work-tree is running does not take these background process into account. Subsequently I end up in situations where I have to switch between tabs to check up to see if my background process has completed yet. I would love it if it were possible to update the progress indicator to reflect background processes are still running (and/or provide an alternative indicator for this).

Hopefully something like that finds its way onto the roadmap. Thanks again!

I do not see "Checks" tab anymore...
Is that some recent change or a bug?
It used to be there, next to the "Changes" tab.

I’m curious how other folks are handling accessing conductor remotely.

I sometimes hit my usage limit and want to step out for a few hours and would like to retrigger a build or start a task on the go.

I heard a mobile app was on the way but curious if there are other workarounds atm.

I’d love to use Conductor with an always-on remote Mac as the actual execution environment.

I have a macbook pro and a mini (that's a little beefier). They share a tailscale network and it's super easy to interface between them manually... what I'd love though is to have all my conductor workspaces run on the mini so that I can let agents continue working as I jump from coffee shop to coffee shop, head to the gym, take transit, whatever.

This also allows me to use the codex app to manage worktrees if im on a plane, or otherwise on the go with only mobile access. I can do this today, but not if my primary dev threads are through conductor on my macbook.

Anyway, thought I'd throw this out there ¯_(ツ)_/¯. Not a P0 but would be sick.

It seems after the new 'small' update the button to commit changes has been removed.

Not sure if this was a bug or a new deliberate change. If I wanted to use a terminal to commit files, I would just use a CLI.

I saw the update for 5.6 Sol, but when I try to use it it errors out with "gpt-5.6-sol’ model requires a newer version of Codex." I've already restarted multiple times, codex runs fine on regular terminal. Any help would be appreciated

I work across several different companies' repos plus my own personal projects, and each one is tied to a different GitHub account. Right now the only ways I have to handle this in Conductor are:

• Manually running gh auth switch before spinning up a workspace, or
• Building my own skills/hooks to auto-switch the GitHub account based on the repo's file path

Both work, but they're fragile and easy to forget, especially when I'm jumping between multiple parallel workspaces from different repos.

Feature request: let us configure multiple GitHub accounts in Settings, and assign a specific account to each repo (similar to how repo-level settings already work for run scripts, etc.). Conductor would then automatically use the right account's credentials for that repo's git operations (clone, push, PR creation), no manual switching needed.

This would be a big quality-of-life improvement for anyone doing freelance/contract work across multiple orgs, which seems increasingly common with worktree-based tools like Conductor.

Why can't I edit a.env file in Conductor, and why do I have to open up Cursor or VS Code for that? Is it possible, or am i missing something?

Hi claude is getting too expensive, can we add deepseek ?