Multica Projects And Resources

Multica Projects and Resources

Quick start

Projects are durable context containers. Resources attached to a project can affect future agent tasks.

multica project list --output json
multica project get <project-id> --output json
multica project resource list <project-id> --output json

Project resources are mutated through project resource commands/endpoints. Issue comments do not create durable project resources.

Core model

A project groups work and carries durable resources. A resource is not just display metadata; it is context later injected into task briefs and .multica/project/resources.json.

Common resource types:

• github_repo — durable GitHub repo context, with resource_ref.url and optional default_branch_hint;
• local_directory — daemon-local path context, with resource_ref.local_path, daemon_id, and optional label.

CLI

multica project list --output json
multica project get <project-id> --output json
multica project create --title "<title>" --repo <github-url> --output json
multica project update <project-id> --title "<title>" --output json
multica project status <project-id> in_progress --output json
multica project resource list <project-id> --output json
multica project resource add <project-id> --type github_repo --url <github-url> --output json
multica project resource add <project-id> --type local_directory --local-path <abs-path> --daemon-id <daemon-id> --output json
multica project resource update <project-id> <resource-id> --url <new-github-url> --output json
multica project resource remove <project-id> <resource-id> --output json

Use --ref '<json>' only for resource types or payloads not covered by shortcuts.

When to add a resource

Add/update a project resource when the user asks for durable project context: "把这个 GitHub repo 绑到项目上", "以后都用这个 repo", "agent 总是拿不到这个项目的仓库", or "这个项目要在我的本地目录里跑".

Project resources are durable and affect future tasks. multica repo checkout is task-local checkout state.

Debugging wrong context

1. multica project get <project-id> --output json. 2. multica project resource list <project-id> --output json. 3. Check github_repo.resource_ref.url, default_branch_hint, and local_directory.resource_ref.daemon_id. 4. Updating resources is a durable mutation. After an update, listing the resource is the verification path. 5. If resources match the expected task context, inspect runtime/repo checkout path next.

Side effects

Project create/update/delete/status and project resource add/update/remove mutate durable workspace state and affect future tasks. Ask before changing local_directory unless the user explicitly requested that exact local path.

More source-backed details: references/projects-and-resources-source-map.md.

Projects and resources source map

• server/cmd/multica/cmd_project.go registers project list, get, create, update, delete, and status.
• The same file registers project resource list/add/update/remove.
• project create --repo attaches github_repo resources during project creation.
• project resource add supports shortcuts for github_repo (--url, --default-branch-hint) and local_directory (--local-path, --daemon-id, --ref-label), or generic --ref '<json>'.
• project resource update merges shortcut edits with existing resource_ref so a partial edit does not clobber required fields.
• server/cmd/server/router.go exposes /api/projects plus /api/projects/{projectId}/resources routes.
• server/pkg/db/queries/project_resource.sql is the CRUD query surface for project_resource rows.
• Project resources are written into .multica/project/resources.json for agent workdirs.