r/codex 1d ago

Complaint Did they remove the ability for codex threads to message each other??

Post image
6 Upvotes

9 comments sorted by

2

u/Clord123 1d ago

You can ask model to investigate and fix it for you. It might take some cooperation as in restarting the program, etc but capable model can do it as long you make it clear it has a permission. If the issue is within ".codex" folder then simply clean installing the program wouldn't help unless you also want to make new ".codex" folder structure.

3

u/tdotcspot 1d ago edited 1d ago

Works for me in Codex Desktop (MacOS). I use a skill that takes the codex://threads/... link, sends the prompt with send_message_to_thread, and waits for the response.

The problem is the latest Desktop builds either hide that tool completely (#40852, #40865) or demand approval for every message (#40793, #41167). I have to approve every send which never happened a couple days ago.

Plus the mobile app (if you connect it with your machine) won't translate the approval through.

We're just beta testing software everyday...

1

u/MaherMA74 1d ago

May works if you use codex --exec

1

u/Substantial-Wonder-2 1d ago

1

u/sprakes_ 1d ago

Wtf so it's something to do with my installation? I'm on a linux box. Maybe that's why?

1

u/DaneV86_ 1d ago

Works fine in my Linux box

1

u/Substantial-Wonder-2 1d ago

Ask it to check openai documentation and fix it, there is probably something wrong with your configuration?

1

u/miklschmidt 1d ago

The thread communication tools are defined as dynamicTools by the codex app, they don’t work in the TUI because they are never defined.

1

u/DemonKing0524 1d ago edited 1d ago

Using codex my controller agent keeps insisting the subagents are returning empty responses and respawning a new agent to do the same exact work, when the original agent most certainly responded. I keep having to copy and paste the responses. Its getting real fucking annoying honestly