[emmanuelmathot]

Stacked on #164.

What

Since #156, a processing error is often shown on a map tile, not for the run. The user could not ask the assistant about it, except by copying the error into the chat.

• The tile alert gets Ask the assistant, when an agent is configured.
• The tile error of the current view goes to the agent as diagnostics.tiles (code, message, failed, at). The contract (1.1) also gets the trigger kind map.tileError. The schema is generated again.
• The map panel writes the tile error to the editor store. A new view or a new project clears it.
• A question from an error, in the editor or on the map, goes through the assistant store (ask). The workspace opens the Assistant tab, and the tab sends the question once.

The toolset reads diagnostics.tiles in developmentseed/openeo-studio-assistant#3.

Test

pnpm build, pnpm lint and pnpm test pass. New tests: the store (tileError, ask), the state document, and the tile alert's button. Not tried in the browser with an agent.

🤖 Generated with Claude Code

[claude]

Claude finished @emmanuelmathot's task in 21s —— View job

---

✅ No blocking issues — safe to merge.

I read the full app/ diff. I did not run the build or tests, and the PR says it was not tried in a browser with an agent.

• Tile error reaches the agent. assistant-tab.tsx:179 spreads the editor store into studioDocument, so tileError arrives as diagnostics.tiles with no extra wiring.
• Stale errors are cleared. use-map-tile-status restarts the status on a new view, and results-panel.tsx:62 resets it to idle when no services remain. The effect at line 73 then writes null to the store. The three project resets in the store also clear it.
• The question handoff holds up. ask sets the question, the workspace effect switches to the Assistant tab, and AssistantTab takes the question once. It waits while busy is true and drops the question if the thread changed. After takeQuestion sets question to null, the workspace effect runs again and does nothing, so there is no tab-switch loop.

Simplify (ponytail)

• app/utils/agent.ts:186: the inline tileError?: {code; message; failed; at?} type repeats TileError from editor-store.ts. Use tileError?: TileError | null, or Pick<EditorState, 'tileError'>.
• app/types/agent.ts StudioDiagnostics.tiles?: TileDiagnostic | null: the field is both optional and nullable. studioDocument always sets it, so keep only | null. The ? is only needed if old producers must still type-check.
• app/stores/assistant-store.ts question and takeQuestion: the tab reads question and then calls takeQuestion(), which reads it again. Read question from the store once. Make the action clearQuestion, or have the effect call set({question: null}) after sending.

---

💰 Estimated review cost: $0.15 · 0m21s · 9 turns

[github-actions]

🐳 Docker image built for this PR:

docker pull ghcr.io/developmentseed/openeo-studio:pr-166