multica

mirror of https://github.com/multica-ai/multica.git synced 2026-06-17 03:38:32 +02:00

Files

LinYushen 5e1a6c4853 fix(cli): degrade 'issue metadata list' to {} on /metadata 404 (#3757 )

Self-hosted backends without the per-issue metadata route (older builds,
unapplied 105_issue_metadata migration, or proxy/ingress misroutes) reply
404 to GET /api/issues/:id/metadata. The agent runtime bootstrap calls
'multica issue metadata list <issue> --output json' best-effort, but a
non-zero exit was being escalated by Hermes into a failed agent run even
when the rest of the work succeeded.

This makes only the 'list' verb best-effort: a 404 from /metadata now
prints {} (or an empty table) and exits 0. Other status codes (401, 500,
etc.) keep real error semantics, and 'metadata get / set / delete' are
unaffected — those represent explicit caller intent.

To support the status-code check without changing the user-facing error
string, GetJSON now returns *cli.HTTPError on HTTP failures (the format
'GET <path> returned <code>: <body>' is preserved by HTTPError.Error()).

Refs GitHub issue #3711.

Co-authored-by: multica-agent <github@multica.ai>

2026-06-04 16:13:27 +08:00

client_test.go

feat(cli): add agent avatar upload command (#1760 )

2026-05-03 10:49:02 +08:00

client.go

fix(cli): degrade 'issue metadata list' to {} on /metadata 404 (#3757 )

2026-06-04 16:13:27 +08:00

config.go

refactor(daemon): remove watch/unwatch workspace logic, default to all workspaces (#1003 )

2026-04-15 11:24:15 +08:00

flags.go

refactor(cli): unify daemon into multica-cli binary with cobra subcommands