What would you like to be added?
introducing a group concept, so that each group gets its own directory under ~/.augment/groups/<group-name>/ containing symlinks to the real repositories, preserving the org/repo directory structure. Auggie is launched with --workspace-root pointing at the group directory.
Why is this needed?
When working across many repositories, Auggie indexes everything in the workspace. There is no built-in
way to define subsets of "related" repos and scope Auggie's context to only those repos. Repos may belong to multiple groups.
Possible solution or alternatives
auggie-group-spec-public.pdf
Additional context
The key ask is a --group flag and repoGroups config to scope context to a subset of repos, with support for overlapping membership and concurrent sessions.
The example solution is an attempt to use a script to do the same - but would be nice Auggie has it built-in.
What would you like to be added?
introducing a group concept, so that each group gets its own directory under
~/.augment/groups/<group-name>/containing symlinks to the real repositories, preserving theorg/repodirectory structure. Auggie is launched with--workspace-rootpointing at the group directory.Why is this needed?
When working across many repositories, Auggie indexes everything in the workspace. There is no built-in
way to define subsets of "related" repos and scope Auggie's context to only those repos. Repos may belong to multiple groups.
Possible solution or alternatives
auggie-group-spec-public.pdf
Additional context
The key ask is a
--groupflag andrepoGroupsconfig to scope context to a subset of repos, with support for overlapping membership and concurrent sessions.The example solution is an attempt to use a script to do the same - but would be nice Auggie has it built-in.