multica-projects-and-resources

To bind a GitHub repository, you attach it as a durable resource to a project. This establishes consistent context for future tasks by recording the binding in the project's persistent state, ensuring agents work against the same codebase across runs.

Durable project resources are linked assets like local directories or GitHub repositories that carry context across agent tasks. You need them when task briefs must stay consistent across runs, enabling persistent collaboration between human and agent work without manual context repetition.

Yes, you can use a local directory as a persistent resource. The system binds local directories to projects, writes changes to a persistent state file, and affects future task briefs and agent behavior for ongoing collaboration.

The best way to manage project context is using durable project containers that carry context across tasks. By binding resources like GitHub repositories to a project, task briefs stay consistent and changes propagate through persistent state files.

Project resource bindings are stored in a persistent state file at .multica/project/resources.json. Changes to resources are written to this file and affect future task briefs and agent behavior, ensuring graceful resource merging and clear context propagation.