fix: inject HEARTBEAT.md content into heartbeat prompt#25
Open
deathbyknowledge wants to merge 1 commit intomainfrom
Open
fix: inject HEARTBEAT.md content into heartbeat prompt#25deathbyknowledge wants to merge 1 commit intomainfrom
deathbyknowledge wants to merge 1 commit intomainfrom
Conversation
The heartbeat session is persistent, so the agent only read HEARTBEAT.md on the first run via tool call. Subsequent runs saw the stale context from the session history and never re-read the file. Now the gateway loads HEARTBEAT.md content and injects it directly into the heartbeat prompt message, ensuring the agent always sees the latest version regardless of session state.
deathbyknowledge
force-pushed
the
fix/heartbeat-inject-content
branch
from
4d1ccca to
736318b
Compare
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
1 participant
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.
The heartbeat session is persistent, so the agent only read HEARTBEAT.md on the first run via tool call. Subsequent runs saw the stale context from the session history and never re-read the file.
Now the gateway loads HEARTBEAT.md content and injects it directly into the heartbeat prompt message, ensuring the agent always sees the latest version regardless of session state.