stakwork / stakwork/hive

Chat: Sending Message causes two workflow triggers

Open
#41 0 comments 0 reactions 1 assignee View on GitHub

@Evanfeenstra is already working on this.

Since Jul 22, 2025.

bug
Dominant language
TypeScript
Stars
5
Forks
17
Avg merge
3h 45m
Merged PRs (30d)
220

Description

Task

The workflow dictates next actions.

We need to either think of a queuing messages mechanism (and also a way to handle that in stakwork).

For v1:

  • Starting a conversation triggers a stakwork workflow (project_id)
  • A user shouldn't be able to send another message until prompted via an artifact to ensure we always send to the workflow

Acceptance Criteria

  • One Task -> One workflow
  • Sending message one triggers a workflow
  • It should not be possible to send another message (until prompted by workflow/agent)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.