Your Memory, on your wrist.

What you need

The Pebble app is the wrist. Your Companion Memory is where the answers come from. Install the app from the Rebble App Store in the Pebble phone app. It is version 1.0 and has not yet been tested on a physical watch. To report what you find or follow progress, join the Discord.

Three taps to what you already know.

The watch never touches the network. It asks your phone, your phone asks your Memory, and the answer comes back to your wrist with a short buzz.

Works on five Pebble platforms.

Speak needs a microphone. Pebble Classic and Steel do not have one, so on those you pick from the listed questions.

One path. Nothing else in the loop.

The app talks to your Companion Memory and only your Companion Memory. What your Memory does with Companion Hub or its own models stays inside your machine.

1. Pebblethe watch app
2. Bluetooth
3. Your phonePebbleKit companion
4. HTTPS + key
5. Companion Memorythe Memory you host
6. Never contacted by this app: Ollama and Companion Hub.

Setup in four steps.

You need a running Companion Memory and a Pebble.

1. Create an API key

   In Companion Memory, open Settings, API keys, and create one with the memory scope. Test it from any terminal:

   curl -X POST https://your-memory.example/api/memory/recall \
     -H "x-api-key: YOUR_KEY" -H "Content-Type: application/json" \
     -d '{"query": "what happened recently?", "maxResults": 3}'

2. Install the watch app

   Open the Companion Memory listing in the Pebble phone app and install it on your watch. Prefer to build it yourself? The source is public at CI-Pebble. In CloudPebble, import the repository and press Compile. Or locally:

   uv tool install pebble-tool
   pebble sdk install latest
   npm run build

3. Try it in the emulator

   No watch to hand? Run pebble install --emulator basalt after a local build to see it first.

4. Connect your Memory

   In the Pebble phone app, open Companion Memory settings. Enter your Memory URL and the key. Save, and the app checks the connection and tells you what works.

Give the key only what it needs.

Companion Memory denies a scoped key on any route that does not name its scope. That is a good default, and it decides what each feature can do today.

The planned features below are not in v1.0. They would need a memory key with write access (Recorder) and an intents scope (Planner).

Your data. Your Memory. Nothing in between.

• Requests go from your phone straight to the Memory URL you enter. There is no relay and no account.
• The API key lives on your phone. The settings page is a local page, so the key never touches a web server.
• Location sync is off until you turn it on, and it only ever goes to your Memory.
• The app has no analytics and no third party. One exception is outside our hands: if you speak a question, Pebble Dictation is a cloud speech service, so that audio goes to the speech service your Pebble platform uses. Picking a listed question sends no audio anywhere.
• This website, not the app, uses Google Analytics and Cloudflare Web Analytics. See the Companion Intelligence privacy policy.

Planned, not in v1.0.

Companion Memory for Pebble reads your Memory today. These ideas are on the roadmap, not in the app, and nothing here is a promise of a date.

Read the roadmap in the docs.