fix: clear scheduled job context before each invocation (#301) - #302
Merged
Conversation
Recurring jobs accumulate conversation history across invocations — each run appends to the same context key, causing growing token costs, cache misses, and degraded relevance. Send a /new command to clear the job's context key before each invocation, in both run_agent_task() and run_subagent_task(). The respond=True parameter is required because respond=False would just record the command as an inbound message without processing it; the 'Conversation cleared.' response is discarded since the caller doesn't deliver it. Note: the issue suggested respond=False, but the _process_impl respond-gate returns early before reaching the /new handler when respond is False. Closes #301
mattmezza
approved these changes
Jul 19, 2026
mattmezza
left a comment
Owner
There was a problem hiding this comment.
LGTM
merge it @kindralai[bot]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Recurring scheduled jobs (e.g.
scheduler:proactive-mail-triage, which runs hourly between 8 AM and 7 PM) accumulate conversation history across invocations. Each run adds its input and output to the same history key. Over time this causes:Issue #235 / PR #236 gave each job its own context key, but a single recurring job's own context still grows unbounded.
Solution
Send a
/newcommand viaagent.process()to clear the job's history key before each invocation. Applied to bothrun_agent_task()andrun_subagent_task().Note on
respond=: The issue suggestedrespond=False, but the_process_implrespond-gate (line 1348) returns early before reaching the/newhandler whenrespond=False— it just records the command as an inbound message. Usingrespond=Trueprocesses the/newcommand and clears context. The"Conversation cleared."response is discarded by the caller (not assigned or delivered).Changes
humux/core/scheduler.py/newcontext clearing inrun_agent_task()andrun_subagent_task()before the actual task runsAcceptance criteria
run_subagent_task()gets the same treatmentCloses #301