deepset-ai / deepset-ai/haystack
Active Human Involvement in AI Application
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26.6k
- Forks
- 3.2k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 194
Description
This is probably a bit too early for a feature request, but might still worth discussing.
In some AI applications like Cursor and Claude Code (and maybe some other vibe coding products), users can provide extra inputs while the agent/application is running, without interrupting the execution flow. The agent/application is not explicitly waiting for human response (as compared to standard human-in-the-loop design), but takes the input into the current architecture in a natural way.
My questions are as follows:
(1) Are there any other AI applications that have this feature right now, and what purpose do they serve?
(2) What’s the recommended way to achieve that in Haystack? My reflection is that this might be tricky in haysatck, since the execution loop is rather pre-determined, (compared to pure agent/multi-a setup) and there is less room to backstep and fix the error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Haystack's pipeline execution and agent workflow entry points, focusing on how execution state and external input are handled while a run is active. Compare those paths with the issue's Cursor and Claude Code examples, then define a concrete proposal and acceptance criteria for incorporating live human input without interrupting execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100