fix(hosting): wire the session history flags into compose and the env examples - #5488
Conversation
… examples The runner service deliberately has no env_file, so AGENTA_SESSIONS_RECONSTRUCT and AGENTA_RECORDS_DURABLE were unreachable in every edition and could not be turned on outside a unit test. List them alongside the other runner variables and document all four flags in the env examples. Claude-Session: https://claude.ai/code/session_01KM69J7uHafgciiN5zfG7qR
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…st.ts Three unformatted lines in this test (added upstream in fix/transcript-hygiene) fail both the format and lint CI jobs, and that red is inherited by every PR stacked on top, including this one. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… nullability Two build-breaking type errors left over from the storage rework's schema change (fetchState now hits the stream endpoint, not the old session_state one): - StatesTab read sandbox_id/data off the stream row. Both moved: sandbox_id now lives on the latest session_turns row (session_states no longer exists), so fetch it from there instead. - The local sessionStreamSchema required a non-null id, but the backend's Identifier mixin has always declared id as Optional[UUID]. That made the Fern-generated type unassignable where StreamsTab's deriveStreamNest call expected the local schema's type. Loosened to match backend reality. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Railway Preview Environment
Updated at 2026-07-27T17:46:12.366Z |
The problem
The runner service deliberately has no
env_file, so it only receives the environment variables compose lists by name.AGENTA_SESSIONS_RECONSTRUCTandAGENTA_RECORDS_DURABLEwere not listed in any of the four compose files.The practical effect is that the feature this stack sits on could not be turned on anywhere. Not in the dev stack, not in a self-hosted deployment. The only place the flags took effect was a unit test that sets them in-process. I found this while trying to stand up a deployment to QA #5486, which could not be done until this was fixed.
The fix
List both flags on the runner service in all four compose files (EE and OSS, dev and gh), and document all four session flags together in the env examples, including the constraint that the runner flag and the web flag have to be flipped together.
Testing
Deployed an EE dev stack from this branch and confirmed both variables arrive inside the runner container. All the QA in this stack depends on it.
Base of the fix stack for #5486.