SharetoBoardThe shared purpose
SharetoBoard helps Poppy users move useful material into the place where they develop it. Android is the flagship capture product. Chrome is the browser companion. Chrome Pro adds user-configured Poppy Specialist links. Tentaclaw is the MCP server and first-party skill kit for external agents.
Boundary comparison
| Surface | User gives SharetoBoard | Persistence | SharetoBoard network path | Poppy owns |
|---|---|---|---|---|
| Android | Supported user-triggered text/link capture and target choice | App settings; earlier queue rows remain frozen in current beta | Current supported online handoff to the selected Poppy workflow | Account sign-in, board service, recorder, downstream content |
| Chrome Free | Board URL and explicit selected content | Board setting; no persistent selected-content outbox | No SharetoBoard backend delivery in the free beta | Board page, content interpretation, recording |
| Chrome Pro | Validated Specialist URL, local display data, session-only selected text | Specialist settings locally; selected text in session storage | No SharetoBoard backend and no Poppy API call | Chatbot setup, sign-in, conversation, retention, access, credits |
| Tentaclaw | MCP tool inputs; local key-file path in host config | No prompt/response persistence by default; metadata-only audit events | Local MCP server sends HTTPS to the Poppy API | API authentication semantics, boards/chats, conversations, credits |
Credential ownership
- Android: the beta requires Poppy email-and-password sign-in in its supported embedded workflow; Google-only sign-in is not currently supported there.
- Chrome Free: no SharetoBoard account or API key; the user supplies a Poppy board URL.
- Chrome Pro: Poppy performs chatbot authentication inside its own origin. SharetoBoard does not request Poppy passwords, cookies, login tokens, or API keys.
- Tentaclaw: the MCP server reads the Poppy API key from a protected local file. The agent and skill must never receive it.
State-changing behavior
Product manuals must distinguish capture from persistence. Android and Chrome actions are user-triggered. Chrome Pro requires explicit copy and paste; it does not auto-submit. Tentaclaw separates one-time poppy_ask from conversation creation and continuation, with history saving disabled by default unless explicitly requested.
Security controls belong to the component that can enforce them
A skill can tell an agent to resolve an exact board and reject ambiguity. Tentaclaw must enforce configured board/chat allowlists. Chrome copy can explain that a public Specialist link may consume credits; Poppy controls whether that link is public, private, revoked, or available. Android can expose only supported capture types; Poppy controls its board and recorder behavior.
Release evidence stays separate too
An Android AAB, Chrome ZIP, Python wheel, skill directory, and website page need different validation. The ecosystem status page records exact candidate identity, tests, live integrations, package contents, signing or checksums, marketplace assets, and approval separately for each product.