Skip to content

Remove single-user defaults so a fresh deploy is multi-user out of the box #4

@omarnagy91

Description

@omarnagy91

Several models and routes default to a single user (user_id="me" / "omar", agent_id="zeno"), a leftover from the original in-house stack. A new self-hoster should not inherit those names.

Acceptance: defaults are neutral or required, the README quickstart still works, and nothing hardcodes a specific user/agent id. Pure-function changes get a test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions