figma_journal
Review local Figma bridge call history to diagnose timed-out, dropped, or late plugin responses after restarts, with filters for method, file, and unsettled outcomes.
Instructions
The bridge's own history, from a local append-only JSONL file: every call it sent to a Figma plugin — method, target, outcome, revision — and above all the ones that did not end cleanly: timeout (the caller gave up), dropped (no answer at all: may or may not have been applied) and late (the answer that arrived after the caller stopped listening). It survives bridge and plugin restarts, which is exactly where figma_ops stops helping. Read-only and entirely local: snippets, text and images are never recorded — only method names, target ids, revisions and outcomes. Lives in ~/.local/share/opencode/figma-bridge-journal/ops.jsonl (FIGMA_BRIDGE_JOURNAL_DIR moves it, FIGMA_BRIDGE_JOURNAL=0 switches recording off).
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "figma_journal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| last | No | How many matching lines to return, taken from the tail; returned oldest-first | |
| method | No | Only entries for this plugin method (e.g. use_figma) | |
| fileKey | No | Only entries for this fileKey | |
| unsettled | No | Only the calls that did not end with a clean answer: `timeout`, `dropped`, and `late` |