Skip to content

Bug: Linear issue is spammed with comments #31

@ankhzet

Description

@ankhzet

Whenever internal state changes, app spams connected linear issue with state updates, i.e.

<!-- stokowski:gate {"state": "research-review", "status": "waiting", "run": 1, "timestamp": "2026-06-01T12:11:43.593597+00:00"} -->

[Stokowski] Awaiting human review: research-review
  1. The "comment" part is still rendered and clutters the output. Maybe can be hidden/badged by a custom plugin?
  2. If state machine enters a loop of errors (i.e. i had claude not configured), the issue got spammed by hundreds of theese "state change" messages, turning the issue into a dumpster and making navigation it a pain.

Suggestions:

  1. When app updates state - ammend the latest message from itself, instead of creating new. For example, the state descriptor json can be supplied with "transitions" field or similar, and then the transitions summary can be rendered.
  2. When app posts a state change with essentialy same contents as previous (just timestamp different), it should just update the timestamp and add a "times" modifier on the reported state (i.e. "x 12")

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions