Sections
On this page
Team work
Who sees conversations with the agent, who can rename, delete or stop a session, and whose credits are spent.
A conversation with the agent is part of the project, like comments on tasks. That's why all agent sessions are shared among project members: a colleague can open your conversation, read why the agent broke a feature down the way it did, and continue from the same point.
Who can do what
| Action | Session author | Other project member |
|---|---|---|
| See the session and the whole conversation | Yes | Yes |
| Write to the session | Yes | Yes |
| Rename, archive | Yes | Yes |
| Delete the session | Yes | No |
| Answer the agent's questions and confirm actions | Only whoever sent the message in that turn | No — sees "Waiting for {name} to answer" |
| Stop a reply in progress | Yes | Yes |
Other people's sessions in the list and their messages in the feed show the author.
Whose credits are spent
Credits are charged to whoever sent the message. If you continued a colleague's session, you pay for your turn and they pay for their earlier turns. The credit limit is personal and applies across all your organizations — see Credits and limits.
Working at the same time
Only one reply runs in a session at any moment. If a colleague is already waiting for the agent's reply, your message won't go through: "The agent is still replying. Wait for the turn to end." You can work in different sessions in parallel — within your plan's number of concurrent turns.
How long conversations are kept
Messages stay in a session until its author deletes the session. Archiving doesn't erase anything; it only removes the session from the list.