#1469 feature request: Whiteboard

Clear and concise description of the problem

The whiteboard feature is partially implemented in a dedicated package, but wiring it still touches several shared areas of the monorepo (shared chat/LLM paths, multiple apps, i18n, build config, and similar). For a single feature like whiteboard, that spread feels disproportionate and sets a heavy pattern for the next similar addition.

This issue asks how the maintainers would like to approach whiteboard (and comparable features): evolve first-party extension hooks in core, move toward the plugin system and UI contribution model described in existing proposals, or another path—so integration does not have to fan out across the tree in the same way.

Context

The existing plugin direction (viewer UI contributions, extensibility without mapping the whole repo) is a good fit in principle for what whiteboard needs, but today’s plugin-sdk emphasis (host lifecycle, permissions, etc.) does not yet replace “mount UI in Stage Web / Pocket + hook xsai tools into the chat path” for this use case. I’ll leave the precise gap analysis to maintainers.

Problem

Whiteboard is logically self-contained (UI + tools tied to chat), but integration currently spans many packages and apps. That makes the change set large for reviewers and for anyone trying to follow “how to add a feature like this.”

Questions

Is wide cross-package integration acceptable for a feature like whiteboard, or should the project move toward fewer touchpoints—whether through generic extension hooks in core, alignment with what #255 and the architecture docs describe for the plugin and UI registration model (chat-adjacent UI and tools), or something else?

Alternative

—

Additional context

Related background

Current exploratory implementation: lulu0119/airi @ feat/airi-whiteboard
Issue #255 — Plugin system & Plugin API
Issue #520 — Structure, Client, and plugin-related UI/widgets discussion
PR #1423 — plugin-sdk refactor and permission model

Validations

Follow our Code of Conduct
Read the Contributing Guide.
Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

feature request: Whiteboard