Skip to main content
Collaboration

Discussion

Clarify engineering questions with teammates and specialist agents, review options, and record actionable decisions.

Availability: Business plans (Teams and Enterprise). Not yet available on individual plans.
Discussions let you work with teammates and specialist agents to clarify requirements, review technical proposals, or investigate defects. Add context, reply to specific questions, and use @ to ask an agent to analyze information or compare options. Mark agreed conclusions as key messages so participants can find and follow up on them. For a payment idempotency review, invite backend teammates to explain the current implementation, test teammates to add failure cases, and an agent to compare designs. After the review, record the chosen approach, open questions, and owners of the follow-up work.

Start a discussion

State what needs deciding and what result you need. This helps participants focus their contributions and recognize when the question has been answered. If an issue already exists, open it in a project and start a discussion with its title and description prefilled. For a proposal or topic without an issue, create a standalone discussion with the following steps.
  1. Open Discussion in the main sidebar and choose New discussion.
  2. Enter a title in the top input field to state the question to discuss.
  3. In the Add description... area below the title, enter the background, open questions, and expected outcome.
  4. To select existing project members, choose Project first, then Member. Use Agent to select agents and Attachment to add files as needed. You can also create the discussion first and invite people with a sharing link.
  5. Choose Create to open the discussion.
For example: 
Topic: Review payment request idempotency.
Context: A client retry after a timeout may produce duplicate requests.
Backend teammates: explain the current constraints. Test teammates: identify failure cases.
Participating agents: compare the options using the supplied design material.
Expected output: tradeoffs, risks, regression tests, and owners of next steps.
The project lead confirms the decision. Analyze only; do not change code or deploy.

Invite participants

When creating a discussion, select a project to choose existing project members. After creation, you can search for organization members by name or invite them through a link.
  1. In Details → Members on the right, open the add menu and choose Add members.
  2. Search by name or nickname and select the people needed for the discussion.
  3. Review the selection and complete the offered action. Direct addition depends on each person’s collaboration preference. If it is unavailable, copy an invitation link so they can join themselves.
  4. Check the member list. Members can change whether they allow direct addition in collaboration settings.
You can also open Share, check Allow joining by link, and copy an invitation link. Turn the option off when no longer needed. Member search does not expand account access to projects or discussions.

Add context and reply to messages

Add design documents, screenshots, and other context and reply to specific points so participants can check feedback against the same context. Write in the input box and choose Send message. To add design material, choose Add attachment, select a file, and send the message. The file appears with the sent message. To respond to a specific point, choose Reply on the message, write in the input box with the quoted context, and send. Choose Go to quoted message on the reply to return to the original message. Type @ to select a person or agent to mention.

Ask agents for help

Ask your own agents to compare options, analyze risks, or suggest test cases. Use their responses as review input: ask for supporting reasoning, add missing constraints, and have participants confirm the chosen approach. You can choose agents when creating a discussion. After creation, open Share > Add Agent / Agent Team to add your own agents. To configure an agent’s model, instructions, or other settings, open Settings > Agent before adding it to a discussion. For details, see Agent.
  1. Search for and select the agents you want to include.
  2. Choose Add selected Agents.
  3. Back in the discussion, type @, switch to the Agent tab, select an agent, describe the request, and choose Send message.
If an agent is unavailable, read the reason beside it and use View settings to check its configuration. Give the agent a clear result, source material, and action boundary. For example: “Compare these two idempotency designs using the supplied material and list failure cases. Analyze only; do not modify code.” After sending an @Agent request to a local Agent, choose Open execution chat to inspect the record, response, and status. The completed response also appears in the discussion, where you can ask follow-up questions or mark important content as a key message.
In a discussion, only an agent’s owner can invoke it with @. You can only @ your own agents, not another member’s agents.

Start or compact a discussion context

When a discussion contains a single Agent you own and no task is currently running, use the available /new entry to start a fresh conversation context or /compact to compress the current context. Retain key requirements before proceeding. These actions may be unavailable when ownership, execution state, or team structure does not meet the conditions. Projects and discussions retain their existing account-access scope.

Record decisions and next steps

A useful review ends with a chosen approach, its rationale, and owners for the next steps. Recording these gives teammates a reference during implementation and acceptance. Mark a message as a key message when it records a decision, delivery requirement, or important reference:
  1. Choose Mark as key message on the message.
  2. Open the Key messages tab on the right to review marked content.
  3. Choose Go to original message when you need context. Choose Unmark key message to remove the mark.
Once a proposal is agreed, post a summary with the chosen approach, rationale, open questions, and owners of next steps. Mark it as a key message so participants can find the decision later. If the discussion started from an issue, manually record the remaining work in that issue and update its status. For example, record how to handle the same request ID with a different payload as an open question, and add the corresponding test case to the regression-test issue.

Find discussion content

During implementation or acceptance, return to the discussion when you need to check an earlier constraint, decision, or contribution.
  • Use Search messages at the top of a discussion.
  • Choose Pin to sidebar for quick access to a frequently used discussion.
  • Use Details on the right to review its description and participants.