so i think the thing that everyone building these git alternatives is missing is a multi-repo story - unless the expectation is that everyone is going to start operating out of monorepos

i've settled on all of this context attached to issues in a project management system and referenced from commits

it works just fine - its not like your agent cannot read your issue tracker

I came across the conclusion here since a change sometimes spans several repos, per-repo history optimizes the wrong target.

I've built some skills to help work with multiple repos, but it's really annoying how e.g. repo-specific .claude/ configs are only read when you start the agent in the repo folder. There's a ton of low hanging fruit to improve dev experience.