You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AGENT_PERSONA is already read in one place (tui/src/pets/talking_signal.rs:66) but only to write the talking-file PID signal. It is not used as a first-class identity selector.
Meanwhile, conversation histories (thread-store, message-history) are keyed by thread ID and are not strongly bound to a persona name. A user running AGENT_PERSONA=pilgrim clanker and later AGENT_PERSONA=hai clanker in different directories should get separate, persona-scoped history — not directory-scoped or thread-ID-only history.
What is needed
AGENT_PERSONA as identity input. When set, this envvar should determine which persona is active for the session — selecting the character manifest, history partition, and TUI identity. It should be the canonical way for a launcher script or wrapper to tell clanker "you are X."
Directory-agnostic history selection by name. Histories must not be scoped to the working directory. A persona's conversation history should follow the persona name, not the $PWD. If I run AGENT_PERSONA=pilgrim clanker from /home/me/project-a and then from /home/me/project-b, I should see the same persona history (or at least have the option to).
Context
AGENT_PERSONAis already read in one place (tui/src/pets/talking_signal.rs:66) but only to write the talking-file PID signal. It is not used as a first-class identity selector.Meanwhile, conversation histories (thread-store, message-history) are keyed by thread ID and are not strongly bound to a persona name. A user running
AGENT_PERSONA=pilgrim clankerand laterAGENT_PERSONA=hai clankerin different directories should get separate, persona-scoped history — not directory-scoped or thread-ID-only history.What is needed
AGENT_PERSONAas identity input. When set, this envvar should determine which persona is active for the session — selecting the character manifest, history partition, and TUI identity. It should be the canonical way for a launcher script or wrapper to tell clanker "you are X."Directory-agnostic history selection by name. Histories must not be scoped to the working directory. A persona's conversation history should follow the persona name, not the
$PWD. If I runAGENT_PERSONA=pilgrim clankerfrom/home/me/project-aand then from/home/me/project-b, I should see the same persona history (or at least have the option to).CLI integration. The existing
--nameflag andAGENT_PERSONAenvvar should converge on a single identity-resolution path:--name>AGENT_PERSONA> last-active (from CC-01 remainder: persisted clanker_id and bare last-active-character continuation #32) > default.Relationship to existing issues
clanker_id) covers the persistence of which character was last active. This issue covers the input mechanism (AGENT_PERSONAenvvar) and the history partitioning by name rather than directory.Acceptance criteria
AGENT_PERSONA=<name> clankerselects the named persona (manifest, avatar, history)--name <name>takes precedence overAGENT_PERSONAAGENT_PERSONAset