Internal Employee Overview

First-party Poe apps built by the team should use the same tools available to any creator. This means importing poe-apps-sdk/v1/client.js for client-side APIs and using the provided test utilities — not reaching into internal packages directly.

The goal is to dogfood the platform: if internal apps need to work around the SDK, that's a signal the SDK needs to improve, not that internal apps should get special access.

Work in Progress

This is still a WIP. Some first-party apps currently import internal packages directly (e.g. @synced-store/client, @synced-store/testing) rather than going through poe-apps-sdk. This is a known gap and is being migrated over time.

First-party apps as examples

These apps are built on the platform and serve as reference implementations:

App	Description	Package
poe-app-manager	The main manager UI — browse, publish, and open apps	poe-apps/manager
poe-app-chat	AI chat app with branching	poe-apps/chat
poe-app-todo-list	Simple todo list with Synced-Store	poe-apps/todo-list
poe-app-tiny-code	In-browser code editor	poe-apps/tiny-code
poe-app-kitchen-sink	Demonstrates various SDK features	poe-apps/kitchen-sink

What "using creator tools" means

• Import poe-apps-sdk/v1/client.js for store setup, bot streaming, and app navigation
• Use createPoeAppTestHarness from the test utilities for unit tests — see Unit Tests
• Use Playwright for e2e tests — see E2E Tests
• Avoid importing @synced-store/client, @synced-store/testing, or other internal packages directly