Comment on feedback
loopback_add_commentAppend comments to feedback items for investigation notes, follow-up questions, or preserving reasoning.
Instructions
Append a comment to a feedback item's discussion trail. Use for investigation notes, questions back to the reporter, or reasoning worth preserving.
Args: id, author, body (markdown ok).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Feedback id, e.g. 'fb_mabc12_3f9a1c' | |
| body | Yes | Comment text (markdown ok) | |
| author | Yes | Comment author, e.g. 'claude-code' or 'dj' |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Feedback id, e.g. 'fb_mabc12_3f9a1c' | |
| url | No | ||
| body | Yes | ||
| type | Yes | ||
| extra | Yes | Free-form captured context. Read `extra.failed_responses` for failing requests with up to 2KB of response body, and `extra.context` for LLM/automation run metadata (run_id, model, trace_url). | |
| links | Yes | Repo/branch/commit/PR of the fix | |
| route | No | ||
| title | Yes | ||
| source | Yes | ||
| status | Yes | ||
| console | Yes | Console lines captured at report time | |
| network | Yes | Network calls captured at report time | |
| project | Yes | ||
| comments | No | Full audit trail | |
| reporter | Yes | ||
| severity | Yes | ||
| created_at | Yes | ||
| replay_url | No | ||
| resolution | No | ||
| updated_at | Yes | ||
| attachments | No | Files attached to this item. `intent` decides what you do with each: 'reference' is context for the fix and never ships; 'asset' is a deliverable — copy it from `path` to `target_path` in the repo, commit it, and record that with loopback_link_change. Read files from `path` directly rather than fetching `url`. | |
| repro_steps | Yes | ||
| dom_selector | No | ||
| assignee_agent | No | Agent currently holding the claim | |
| screenshot_path | No |