Suggested-task chip: add a "Create ticket" action alongside "Send to cloud"

Resolved 💬 1 comment Opened Jul 8, 2026 by johangace Closed Jul 8, 2026

Context

The "Suggested task" chip (shown after a session surfaces a follow-up, with a "Send to cloud" button + dropdown) is great for spinning work off into its own session. But teams that track all work in an external issue tracker (GitHub Issues, Linear, Jira, etc.) currently have no first-class way to turn a suggested task into a ticket — it's chip-only, and chips are session-local and don't persist into the team's real backlog.

Request

Add a "Create ticket" option to the chip (either as a second button, or as an item in the existing dropdown next to "Send to cloud"). Ideally:

  • Configurable target (GitHub repo, or whatever issue tracker the user has connected)
  • Uses the suggested task's title + description as the issue title/body
  • Dismisses or marks the chip as "filed" once the ticket is created, so it's clear the task has a durable home

Why this matters

For teams running multiple parallel Claude Code sessions, suggested-task chips are a great signal but a poor system of record — they die with the session. A one-click "file this as a ticket" action would let the suggestion flow straight into the team's actual backlog instead of relying on a human (or another agent) to manually re-type it into an issue tracker.

Reported via a live session that hit this gap directly.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗