Carry an approved brief into a fresh session.
The problem
A working brief can become tied to one provider. Switching engines then means explaining the same stable context again.
An explanatory exhibit
One approved brief, separate conversations
Context-flow illustration. No provider account or real session is connected to this page.
- 01
Profile
Reviewed fictional working brief
- 02
Opt-in check
Context assembly decides inclusion
- 03
Fresh session
Claude or Codex receives the brief
Inspect the consequence
Inclusion enabled
Add approved context
A supported fresh-session path can include the brief after its policy checks.
Inclusion disabled
Start without the profile
Opt-in governs prompt inclusion. Maintaining a profile alone does not require using it in a session.
What this makes possible
I gave fresh Claude and Codex sessions a shared context assembly path, governed by the maintained profile’s opt-in checks.
Source information sheet
Evidence, implementation & history Implementation inspected
What I checked
Context assembly source inspected. Production enablement at every session entry point has not been independently checked.
Research cut: 14 October 2026. Source areas below are from panel-forge. Private conversation references are retained in the research ledger and are not published here.
Implementation decisions
The engine personal context service assembles the approved brief for engine startup. Claude and Codex session services integrate that context at their entry points.
Opt-in and session policy checks govern inclusion. The inspected source establishes those boundaries; it does not establish that every production entry point currently enables the feature.
A path through the feature
- Approve the context
Review the profile and enable inclusion through its opt-in setting.
- Begin a fresh session
The supported startup path can include the approved brief. Provider-specific conversation state remains separate.
Source areas
app/Services/EnginePersonalContextService.phpapp/Services/PersonalContext/PersonalContextService.phpapp/Services/ClaudeSessionService.phpapp/Services/CodexSessionService.php
The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.
Recorded history
Dates describe the researched record, rather than today’s deployment.
Auto-injecting a personal context profile