[FEATURE] - Create a Ticket for Suggested Tasks

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

We run many parallel Claude Code sessions across a fleet of repos. When a session surfaces a follow-up task, it shows up as a "Suggested task" chip with a "Send to cloud" action. That's useful for spinning the task off immediately — but it's the only thing you can do with it in the moment.

Our team tracks all real work in GitHub Issues so it survives past any single session and shows up in triage/backlog. Suggested-task chips don't do that: they're session-local UI state. If nobody clicks "Send to cloud" right then, the task is only preserved if a human (or the agent) notices it and manually retypes it into an issue tracker later. In practice that means:

Tasks get lost when a session ends without action being taken on the chip
There's no single source of truth — some suggested tasks become tickets, some become cloud sessions, some just vanish
Converting a suggestion into a tracked issue currently requires copying title/description by hand into GitHub (or another tracker), which is friction significant enough that it doesn't reliably happen

Proposed Solution

We want every suggested task to have a one-click path into our actual backlog, not just into an ephemeral session.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

1. I'm running a Claude Code session in a workspace folder that contains many of our team's repos. Mid-session, a "Suggested task" chip appears: "Un-gate living-window desktop pane after parity review" — a real follow-up spotted from the work in progress.
2. This isn't something I want to work on myself right now, and it isn't something I want to hand to a cloud session immediately either — it needs a parity review by whoever owns that surface, on their own time. I just want it captured so it doesn't get lost.
3. With this feature, I'd click "Create ticket" on the chip. It would open a filed GitHub issue in the right repo, pre-populated with the chip's title and description, and mark the chip as "filed" so it's clear the task now has a durable home.
4. This would save me time because right now the only way to preserve a suggested task I'm not acting on immediately is to manually copy the title and description out of the chip and retype them into a new GitHub issue myself (or ask the agent to do it as a separate step). A one-click action collapses that into the same motion as dismissing the chip — so suggestions reliably end up in the backlog instead of silently disappearing when the session closes.

Additional Context

Additional context: We have a strict team rule that any task or follow-up finding must be filed as a GitHub issue so it survives past the session (chips are ephemeral UI state, not our system of record). Right now that means every suggested-task chip requires a manual, separate step to become durable — this feature would make the durable path the default path instead of an extra chore.