This is a confirmed bug — each send() on a local agent starts a fresh run without loading prior conversation state. Cloud agents handle this server-side and work correctly.
I’m merging this into an existing thread where the same issue was reported and acknowledged:
The bug is tracked internally. Your workaround of injecting history into the prompt is the right approach for now. The alternative is switching to cloud: { repos } mode if your use case allows it.