Repository identity
Know which checkout and host a session belongs to before an agent touches the files.
Bring repositories, sessions and working context into one navigable workspace. Switch projects without losing the thread of what each agent is doing.
A repository is more than a folder path. It has conventions, active branches, ongoing sessions and a history of decisions. Qodarium groups the work around that context so switching tasks is a navigation problem, not a memory test.
The intended Community workflow lets one developer work across local and remote projects. Team builds on the same foundation with shared access, rather than creating a separate universe of team-only tasks.
Know which checkout and host a session belongs to before an agent touches the files.
Find ongoing work in the project it concerns, with enough context to decide what deserves attention.
Keep working conventions near the code and make the expected workflow explicit.
Return to past discussions and artifacts when a new task depends on an earlier decision.
Choose the machine and checkout deliberately, including the relevant branch or worktree.
Record project conventions and the outcome you want from this session.
Use meaningful task titles and review the project's open work before starting a duplicate effort.
No. Git remains the source-control system. Qodarium connects agent work to the repositories, branches and worktrees you already use.
Team access is planned with a deliberately small owner/member model. Granular enterprise permissions are outside the initial scope.
A workspace that holds the context while you focus on what comes next.