Skip to content

Conversation

@theomonnom
Copy link
Member

No description provided.

task_ids.discard(active_task_id)
task_repr = {f.id: f.description for f in self._registered_factories if f.id in task_ids}

description = (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this description seems very specific to the style of agent where it's modifying information in another task.. is it robust enough for other use cases as a task?

should we also allow users to skip around? currently it's only allowing you to go back to previous tasks. I'm wondering if this should be specified on each task itself either:

  • can be revisited
  • can be skipped ahead

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think in future versions of TaskGroup, we can allow additional parameters to tasks for those:

mutable: bool will determine whether or not a task can be revisited
global: bool will determine if a task can be called regardless of whether it was visited or not

(Open to other name suggestions)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@davidzhao Do you have any examples or scenarios where you’d want a task that can be skipped ahead?

is it robust enough for other use cases as a task?

For now we're mostly focused on input collection, do you have other use cases in mind?

@theomonnom theomonnom merged commit 7bc1bfe into theo/v1.3 Oct 20, 2025
1 check passed
@theomonnom theomonnom deleted the theo/task-group branch October 20, 2025 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants