Meeting assistant [Beta]
Invite a bot to your meetings and let an AI assistant create and link tickets from the conversation in real time.
The meeting assistant joins your video calls, listens to the conversation, and turns actionable items into tickets — all in real time. It works with Zoom, Google Meet, and Microsoft Teams.
When someone mentions a bug, requests a feature, or assigns a task, the assistant picks it up from the transcript. If a matching ticket already exists, the assistant links the meeting to it. If not, it creates a new one with a description based on what was said.
Once the meeting assistant is enabled for your project, a Meetings link appears in your project's navigation bar alongside Emails, Benchmark, and Settings.
All workspace members can view meetings and transcripts. Creating meetings and sending chat messages requires owner, admin, or developer permissions.
The meeting assistant uses Claude Code with Claude Sonnet 4.6, so you'll need a Claude API key configured for your project.
Auto-launch implementations
In Project Settings under the Meetings section, there's an optional setting: Automatically launch an implementation on created tickets. Any workspace member with project edit permissions (owner, admin, or developer) can toggle this on. When enabled, any ticket the meeting assistant creates will immediately kick off an implementation using your project's configured coding agent. This is useful if you want work to start right away without manual intervention.
This is the master switch for auto-launching — if it's off, implementations are never auto-launched from meetings regardless of per-meeting settings. During a meeting, you can temporarily pause auto-launches using the meeting-level toggle without changing this project-wide setting.
Inviting the bot to a meeting
- Go to your project's Meetings page
- Click Invite Bot to Meeting
- Paste your meeting URL (e.g.,
https://zoom.us/j/123456789) - Click Invite
The Superconductor Assistant bot joins your call and begins capturing the transcript. You'll see the meeting appear in your meetings list with a live status indicator.
Supported platforms
| Platform | Example URL |
|---|---|
| Zoom | https://zoom.us/j/123456789 |
| Google Meet | https://meet.google.com/abc-defg-hij |
| Microsoft Teams | https://teams.microsoft.com/l/meetup-join/... |
During the meeting
While the meeting is in progress, click on it from the Meetings page to see the meeting detail view, which has two panels:
- Chat — A conversation panel where you can send messages to the assistant and see its responses. The assistant responds to direct questions and proactively reports when it creates or links tickets.
- Transcript — A live, scrolling transcript of the meeting with speaker names and timestamps.
On mobile, these are shown as separate tabs. On desktop, they appear side by side.
The assistant processes transcript chunks as they arrive. Since chunk boundaries are based on timing rather than semantics, the assistant waits for enough context before acting — so there may be a short delay between when something is said and when a ticket appears.
You can also chat with the assistant directly. Type a message in the chat panel and the assistant will respond. This is useful for asking it to clarify a ticket it created, or to manually request a ticket for something it missed.
Pausing ticket creation and auto-launches
Two toggles appear in the meeting header while a meeting is in progress:
- Ticket creation — Controls whether the assistant creates new tickets from the conversation. Turn this off to pause ticket creation without removing the bot from the call.
- Auto-launch — Controls whether newly created tickets automatically kick off an implementation. This only has an effect when the project-level auto-launch setting is enabled — if that setting is off, toggling this on will not auto-launch implementations.
Both toggles default to on and take effect immediately. Turning them off can be useful when you want the bot to keep transcribing but hold off on creating tickets or launching implementations — for example, during a brainstorming section where you're not ready to commit to specific tasks.
After the meeting
When the meeting ends (either by the host or due to inactivity), the assistant processes any remaining transcript and finalizes its work.
The full transcript, chat history, and all created or linked tickets remain accessible on the meeting's detail page — click on the meeting from your project's Meetings page to review them at any time.
Deleting a meeting
From the meeting's detail page, click the Delete button in the header. This removes the meeting record, its transcript, and the associated bot. Tickets that were created or linked during the meeting are not affected.
Feedback
This feature is in beta and under active development. We'd love to hear how it's working for you — reach out to us with feedback, questions, or feature requests.