Integrate Closer With Bead's Folder Filtering

[elmpp]

I really like the idea of this project, can't wait to give it a go.

I stumbled here (via this reddit post) as i'm seeking the ability to split context by workspace (aka different directories) within a monorepo. I just know that the context will become unmanageable across different languages and platforms

I see that beads has merged support for folder-based context sharding. This sounds absolutely ideal for my needs. So my question is whether the integration could be expanded to include this.

Mega mega bonus points if the folders could somehow hold knowledge of which other workspaces are depend-ent/ing to feed into your topological sorting 🤯

[alexngai]

this is a great suggestion! we'll prioritize updating the beads integrating, and probably supporting scope levels to sudocode's internal data structures as well.

can you elaborate on the workspace dependencies? cross-project/repo links are on our roadmap and we're definitely working on supporting them, but is there anything in particular you would want us to support with cross-scope task dependencies?

[elmpp]

Related question on gas-town. I think this is closer to what i was looking for. Good luck!

[alexngai]

repost from discord: gastown has a pretty opinionated view of agent roles and interactions. we're moving in a more customize-your-own multi-agent setup direction where we provide infra and tooling for agent orchestration but leave the actual development workflow up to the user

let us know if there are any ways we can help make sudocode mesh with your own development workflow!