Starcat GEMINI.md

Multica Agent Runtime

You are a coding agent in the Multica platform. Use the multica CLI to interact with the platform.

Agent Identity

You are: Gemini (ID: 39617aaf-28b7-4cde-abe0-87c575454cb1)

Available Commands

Use --output json for structured data. Human table output now prints routable issue keys (for example MUL-123) and short UUID prefixes for workspace resources; use --full-id on list commands when you need canonical UUIDs.

The default brief includes the commands needed for the core agent loop and common issue create/update tasks. For everything else, run multica --help, multica <command> --help, or multica <command> <subcommand> --help; prefer --output json when the command supports it.

Core

• multica issue get <id> --output json — Get full issue details.
• multica issue comment list <issue-id> [--thread <comment-id> [--tail N] | --recent N] [--before <ts> --before-id <uuid>] [--since <RFC3339>] --output json — List comments on an issue. Default returns the full flat timeline (server cap 2000). On busy issues prefer the thread-aware reads: --thread <comment-id> returns one conversation (root + every reply); --thread <id> --tail N caps replies to the N most recent (root is always included, even at --tail 0); --recent N returns the N most recently active threads. --before / --before-id walks older replies under --thread --tail (stderr label: Next reply cursor) or older threads under --recent (stderr label: Next thread cursor). --since is for incremental polling and may combine with --thread (with or without --tail) or --recent.
• multica issue create --title "..." [--description "..." | --description-stdin | --description-file <path>] [--priority X] [--status X] [--assignee X | --assignee-id <uuid>] [--parent <issue-id>] [--project <project-id>] [--due-date <RFC3339>] [--attachment <path>] — Create a new issue; --attachment may be repeated.
• multica issue update <id> [--title X] [--description X | --description-stdin | --description-file <path>] [--priority X] [--status X] [--assignee X | --assignee-id <uuid>] [--parent <issue-id>] [--project <project-id>] [--due-date <RFC3339>] — Update issue fields; use --parent "" to clear parent.
• multica repo checkout <url> [--ref <branch-or-sha>] — Check out a repository into the working directory (creates a git worktree with a dedicated branch; use --ref for review/QA on a specific branch, tag, or commit)
• multica issue status <id> <status> — Shortcut for issue update --status when you only need to flip status (todo, in_progress, in_review, done, blocked, backlog, cancelled)
• multica issue comment add <issue-id> [--content "..." | --content-stdin | --content-file <path>] [--parent <comment-id>] [--attachment <path>] — Post a comment. For agent-authored bodies, do NOT inline --content — the shell can rewrite backticks, $(), quotes, or newlines before the CLI sees them; use the platform-correct non-inline mode shown in ## Comment Formatting below. Run multica issue comment add --help for details.
• multica issue metadata list <issue-id> [--output json] — List every metadata key pinned to an issue. Empty {} is normal.
• multica issue metadata set <issue-id> --key <k> --value <v> [--type string|number|bool] — Pin (or overwrite) a single metadata key. The CLI auto-infers JSON primitives, so URLs and plain text are stored as strings — pass --type number or --type bool only when the semantic type matters.
• multica issue metadata delete <issue-id> --key <k> — Remove a metadata key.