Let two chats talk to each other
Bring one conversation's state into another with an @ mention, or let teammates message each other by handle.
Conversations should share what they know without you copying and pasting between them.
- ask the API chat what it decided
- the docs chat asks the tests chat for a number
- a status check across chats
Every conversation knows something the others do not. CodeAF gives you two ways to move that knowledge: a chat can read another through an @ mention, which costs one line and disturbs nobody, and teammates can message each other by handle, with every message logged.
Try it in CodeAF
- Where
In the message box of any conversation.
- Type
@chat:Then the start of the other chat's name, and press Enter on it. Then ask your question and press Enter:
@tasks What did that chat conclude about how tasks are stored?- You see
The chat answers from what the other one concluded, with no tool call.
Read another chat
The @ list has three sections, teams, conversations and files, with the words team, chat and file on its first row to narrow it. Choosing a conversation inserts its handle, or a short name from its title. When you send, the model is handed a short digest of that chat: its title, its state and an excerpt of its last reply. It never gets the whole transcript, and the other chat is not messaged and not woken. Mention a team instead (●taskboard) and the digest is its members, their states and recent Traffic.
Message a teammate
When both chats are in a team that has a manager, each member can post to the room, to the manager, or to one teammate by handle. Say Post a message to your teammate @testlead: ask how many test functions tests/test_api.py has. The post goes into the team's Traffic, and your chat's column shows you → @testlead How many test….
A post to a teammate waits: it reaches the other chat at the start of its next step, marked with your chat's handle and the post's number, such as from @api #18:, never as if you had typed it. The answer comes back the same way, as @testlead → you tests/test_api.py has 3…. When you need the answer now, ask the manager instead: its directive starts an idle member, and the member's reply wakes the manager.
Managers are teammates too. Two sub-team managers under one parent, or two top-level managers under a global manager, post to each other the same way, so leads can settle a handoff without routing it through the manager above. Posts stay inside a team: to reach another team's member, go through the managers.
Your own words in a chat always outrank a manager's directive, which outranks a teammate's message.
Things to build
- Ask without interrupting: from the docs chat, ask what the API chat decided with an
@mention, and nothing in the API chat moves. - A number from a teammate: the docs member asks the tests member for a count by post, and the answer lands in the docs member's next step.
- Leads that talk directly: two sub-team leads trade a finding by post while their manager keeps directing both.
- Teams in a chain: backend lands an endpoint, docs writes it up and qa tests it, linked by a standing rule at the global manager. Connect teams
Go further
Connect teams: One team's result wakes the next team with no message from you, and you hear once at the end.
Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.