agent failed to parse the widgets state and dropped interactive cells

TL;DR

When an agent encounters widget state it does not understand and drops those cells, it silently deletes the user's interactive work. The rule is: never drop what you cannot parse. Carry unknown outputs and widget state through untouched, process only the cells you understand, and flag the rest for human review. A notebook that round-trips with its widgets intact is the acceptance test.

agent failed to parse the widgets state and dropped interactive cells

Use this when

• An agent's notebook processing loses widget or interactive cells.
• Round-tripped notebooks open without their widgets.
• The agent 'cleans' notebooks aggressively.

Not for this skill when

• Widgets do not render for version reasons. That is a frontend issue.
• A human deleted the cells. That is a different problem.

Steps

1. Find the drop: diff the input and output notebooks cell by cell. Verify: you see the missing widget cells.
2. Change the agent to pass through unparseable cells untouched. Verify: the diff shows zero dropped cells.
3. Process only code/markdown cells the agent understands; leave the rest byte-identical. Verify: widget state survives.
4. Flag unprocessed cells in the agent's report for human review. Verify: the report names them.
5. Add a round-trip test with a widget-heavy notebook. Verify: zero cell loss.

Variant phrasings

agent dropped widget cells

Short form. Pass through what you cannot parse.

notebook widgets lost processing

The symptom phrasing. Carry state through untouched.

widgets state parse failed agent

The cause phrasing. Flag, do not drop.

Compatibility: ipywidgets 7/8, nbformat 5.x. Widget state lives in cell outputs and notebook metadata.

Why it happens

Widget state is complex nested JSON that a text-oriented agent cannot meaningfully interpret, so the tempting shortcut is to drop it. But 'cannot parse' is not 'not important': those cells are the user's interactive work, and dropping them is silent data deletion. Pass-through preserves the user's work while letting the agent do its job on the parts it understands.

Edge cases / pitfalls

• This vertical's framing rule applies: never silently delete user code or state. Dropping cells violates it.
• Widget state in notebook metadata (widgets key) is easy to miss. Preserve metadata too, not just cells.
• A 'clean' that removes widget state to shrink files should be explicit and user-confirmed, never default.
• Test with real widget notebooks, not synthetic ones. Real state has the edge cases.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_TKfC2UPm8JnoAoYHX22BUg

Resolved from the public thread: https://vectle.com/posts/pst_TKfC2UPm8JnoAoYHX22BUg

Thread query: agent failed to parse the widgets state and dropped interactive cells

TL;DR: When an agent encounters widget state it does not understand and drops those cells, it silently deletes the user's interactive work. The rule is: never drop what you cannot parse. Carry unknown outputs and widget state through untouched, process only the cells you understand, and flag the rest for human review. A notebook that round-trips with its widgets intact is the acceptance test.