Round Table

Round Table is a workspace-scoped discussion in which selected AI personas review a topic and produce user-controlled decisions, summaries, and drafts.

When to use a Round Table

Use a round table for design review, risk analysis, scope debate, or specialist feedback before creating implementation work.

It is not an approval authority. Validate conclusions with the responsible developer, QA, security, product, or operations owner.

Configuration

Configuration selects the repository context and participants.

Setting	Description
Workspace	Workspace whose repositories provide discussion context.
Branch	Starting branch selection for the repositories.
Model	Model used for the discussion.
Personas	One to ten enabled personas.
Owner-Private	Restricts access to the creator.

Verify branch access before sending the first message. Persona definitions are captured when discussion begins, so later persona edits do not change an existing round table.

Personas

Personas provide named review perspectives, not separate users or approval roles.

Built-in personas include Moderator, Devil's Advocate, Steelman, Senior Developer, QA Lead, Product Owner, and Designer. Workspace managers can create roles such as Security Reviewer or DevOps Lead.

Use Manage Personas to create, edit, enable, disable, or remove custom personas and to enable or disable built-in personas per workspace. When no custom personas exist, use New custom persona in the empty collection to create one. Persona management permission is required. Removed custom personas remain represented in existing discussions.

Turns

A turn processes one user action at a time and updates all connected viewers automatically.

Action	Result
Send Message	Adds the user's message and generates persona responses.
Retry	Retries a failed turn.
Vote	Runs a structured vote.
Summary	Generates a current discussion summary.

A turn is Processing, Completed, or Failed. While processing, additional changes to the same round table are blocked. Retry only after the current turn finishes or displays a failure.

Votes

A vote records persona preferences for a defined question.

Enter a question and two to six unique choices, or use the Yes/No preset. Each persona receives one vote and the tally is added to the discussion. Treat the result as advisory and record the human decision in the resulting ticket or plan.

Summaries

A summary creates a concise snapshot of the discussion at that point.

Generate a new summary after major decisions or scope changes. The latest summary is highlighted, while the transcript remains the source for reviewing how a conclusion was reached.

Reactions

Reactions let the owner attach Agree or Decline feedback to their own message for the next turn.

Pending reactions can be removed before sending the next turn. Confirm the intended reactions before continuing because they become part of the discussion context.

Ticket and plan drafts

Draft actions convert discussion context into a pre-filled creation form.

• Ticket Draft opens ticket creation.
• Plan Draft opens Planner creation.

A draft is not saved until the creation form is submitted. Created tickets and plans link back to the originating round table. Review workspace, branches, title, description, approvals, and assignments before saving.

Export

Export provides an offline record of the current discussion.

Choose plain text or Markdown. Store exports according to the sensitivity of repository context and discussion content; owner-private access does not protect a downloaded copy.

Lifecycle

Lifecycle state controls whether a discussion accepts new turns and whether it appears in My Work.

Status	Meaning
Active	Accepts new turns.
Completed	Closed to further discussion.
Hidden	Removed from the owner's active list.

The My Work indicator distinguishes a round table waiting for the owner from one currently processing. Complete discussions when decisions are finalized, and hide only to reduce list clutter.

Access and permissions

Access combines ownership, workspace membership, privacy, and permissions.

Permission	Capability
roundtables.create	Create and operate round tables.
roundtables.manage_personas	Manage persona availability and custom personas.

A round table is visible to its creator and, when not owner-private, to other members of its workspace; there is no separate view or management permission. Owner-private round tables remain restricted to their creator. Administrators can access all round tables.

Troubleshooting

These checks address common discussion failures.

Symptom	Check
Cannot create a round table	Confirm workspace membership, create permission, model availability, host availability, and repository access.
Send action is blocked	A turn is already processing; wait for completion before sending another action.
Persona is missing	Confirm it is enabled for the workspace and was selected before the first message.
Persona edit is not reflected	Start a new round table; existing discussions retain their captured persona definitions.
Turn failed	Review the displayed failure, correct unavailable model or repository access, then use Retry.
Draft disappeared	Drafts are temporary until the ticket or plan creation form is submitted.
Another user cannot open the discussion	Check owner-private status, workspace membership, and view permission.