so the way hive handles cross repos, is by creating a temporary directory, with symlinks to the original worktrees. For all the model cares and knows, hes worki

so the way hive handles cross repos, is by creating a temporary directory, with symlinks to the original worktrees. For all the model cares and knows, hes working on a mono repo of x projects, and is able to navigate it the way it knows best. All edits he does - are then propagated to the original worktrees in their original folders. So you kind of get the best of both worlds (without requiring you to feed the context manually)