PocketPi

The agent-native runtime on embedded devices

PocketPi runs the full Pi Agent core harness on-device, where it can operate, build and evolve the Apps that make up the product.

Loading S3 simulator frames

The agent is not added to the product, it's part of the runtime.

Human and Pi Agent are independent actors. Both meet at the same App boundary.

Humanoutside the device runtime
PocketPi runtimeresident on the device
Appshared product boundary
Viewhuman projectionActionsbounded operationsDatadurable truth
resident system guestPi Agentfull core harness
ToolsContextModel loop

PocketJS is the runtime substrate.

PocketJS provides the one QuickJS execution platform, native rendering core and bounded host modules. PocketPi adds the resident Agent, App lifecycle and product model above it.

The shared substrate keeps performance predictable as multiple Apps stay resident and multiple Actions run, without duplicating rendering or lifecycle control.

Read the layer boundaries →
Validated ESP32-S3 release footprintWaveshare ESP32-S3-WROOM-1-N16R8
Less than 35% used in every measured capacity
18.3%used

PSRAM

1.46 MiB fixed scanout of 8 MiB

81.7% remains
30.0%used

IRAM

100.0 KiB image of 333.75 KiB

70.0% remains
34.9%used

Flash

5.59 MiB executable image of 16 MiB

65.1% remains
Inside this footprint

Pi Agent core harness, PocketJS, App runtime, View SDK, SQLite, networking and touch UI.

Flash and IRAM come from the current release ELF. PSRAM shows the fixed two-framebuffer floor. Dynamic Agent heaps and worker stacks are excluded.

Apps are the unit the agent and human can both understand and act on.

Different actor surfaces converge on the same Actions and the same durable product truth.

Human View and Pi Agent Tools invoke the same App Actions over one App-owned SQLite database
App=
Data

App-owned SQLite and files.

+
Actions

Operations shared by UI and Agent.

+
View

The human-facing projection.

Read the complete App contract →

The Agent develops the product it lives on.

This is a vision of the full agent-native development environment on an embedded device.

One App revision
  1. Request

    Describe the change

    The human explains what the App should do differently.

  2. Activate

    Confirm on device

    The approved release keeps the existing App Data.

Move over Checkout, Modify or Review to inspect that moment.

PocketPi-ready devices

The runtime and App contract have been implemented and physically validated on two resource-constrained Waveshare boards.

Back of the Waveshare ESP32-P4-WIFI6-Touch-LCD-5 board showing the P4 module, connectors and PCB traces

Waveshare ESP32-P4-WIFI6-Touch-LCD-5

ESP32-P4NRW32 / 32 MB PSRAM / 5-inch 720 × 1280 touch display

Back of the Waveshare ESP32-S3-Touch-LCD-4.3 board showing the S3 module, ribbon connector and edge ports

Waveshare ESP32-S3-Touch-LCD-4.3

ESP32-S3-WROOM-1-N16R8 / 8 MB PSRAM / 4.3-inch 800 × 480 touch display