Skip to content

feat: add max_wait_time parameter to job_output tool - #1496

Closed
heimoshuiyu wants to merge 1 commit into
charmbracelet:mainfrom
heimoshuiyu:wait-job-output
Closed

heimoshuiyu wants to merge 1 commit into
charmbracelet:mainfrom
heimoshuiyu:wait-job-output

Conversation

@heimoshuiyu

@heimoshuiyu heimoshuiyu commented Nov 22, 2025 •

Copy link
Copy Markdown

Allow job_output tool to wait for job completion with configurable timeout. The tool now supports a max_wait_time parameter that enables monitoring long-running tasks without continuous polling. When the timeout is reached, it provides helpful feedback suggesting a longer wait time.

  • I have read CONTRIBUTING.md.
  • I have created a discussion that was approved by a maintainer (for new features).

This should not be considered a feature, but rather a fix. It prevents the crush from repeatedly calling job_output within a short period to check if the task is completed.

In YOLO mode, the crush sent over 20 requests in one minute to check if the compilation task was finished, and the repeated tool calls quickly exceeded the model's context limit. This is a serious issue.

Adding a maximum wait time parameter can resolve this problem.

Allow job_output tool to wait for job completion with configurable timeout.
The tool now supports a max_wait_time parameter that enables monitoring
long-running tasks without continuous polling. When the timeout is reached,
it provides helpful feedback suggesting a longer wait time.
@heimoshuiyu
heimoshuiyu requested a review from a team as a code owner November 22, 2025 05:15
@heimoshuiyu
heimoshuiyu requested review from aymanbagabas and meowgorithm and removed request for a team November 22, 2025 05:15
@charmcli

charmcli commented Nov 22, 2025 •

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@heimoshuiyu

Copy link
Copy Markdown
Author

I have read the Contributor License Agreement (CLA) and hereby sign the CLA.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We recently released a complete UI rewrite to improve performance and maintainability.

The new code is on internal/ui as opposed to internal/tui. So you'll need to undo these changes and reimplement this part on internal/ui.

@andrinoff

andrinoff commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Thank you for your contribution! This pull request has merge conflicts and has had no activity for over 2 months, so we are closing it to keep the queue manageable. If you would still like to get this merged, please rebase onto the latest main branch and reopen it.

@andrinoff andrinoff closed this Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants