async jobs (background tasks)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2k
- Forks
- 291
- Avg merge
- 30m
- Merged PRs (30d)
- 3
Description
Problem
there are actions that might take a long time (e.g. deep research).
Proposed Solution
The agent might have actions that are marked for "async", that is that emits jobs might be run in the backlground. The jobs then needs to be also of a new type "async", that means that they will go in a separate queue to be processed in the background, and when the job is done it will call a callback to the connector with the job result as argument.
Acceptance criteria
- Jobs should be also of type "async"
- The job needs also a way to annotate metadata to be carried over
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by tracing the existing job types, queue handling, and connector callback flow, then determine where async jobs and carried metadata belong. Done means async actions produce separately processed jobs, preserve their metadata, and invoke the connector with the completed result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100