Index-01 šŸ¤ Claude Code

Since the application infrastructure is now available, I took a stab at using Claude Code to set up infrastructure so that recordings from the ring can trigger actions in my Claude Code environment, but I would love advice from anyone who is an actual developer to check if I am thinking about this the right way. :slightly_smiling_face:

It set up a Cloudflare Worker so that the Pebble app has a webhook to send its transcriptions to. That worker writes the transcriptions as new files in my GitHub repo, which then uses GitHub Actions so that each new file triggers a GitHub AI Agent. That Agent determines whether there’s anything time-sensitive in the message.

If there’s anything urgent, it pushes a message to CloudFlare KV. Then on my laptop there’s a quick check that runs every 60 seconds looking for anything in CloudFlare KV.

Otherwise I’m going to use the newly released Claude Code ā€˜loops’ feature (thanks, OpenClaw) to have an hourly heartbeat that takes any new material from the transcriptions and integrates it into my repo wherever it belongs or takes action based on it.

Is this how you would do it, or does any of it sound crazypants?

2 Likes

I am also sending transcripts to Claude Code! I admit your solution seems overly complex. That said, mine is very different.

I run a homemade Android app on my phone which:

  1. Hosts a local webhook target for the Pebble app
  2. Is linked to a custom client on my home PC via ir0h
  3. Can receive and surface agent responses as push notifications

I may someday retire the local webhook in favor of a static-IP cloud service. But this does make for a nice free option with no special hosting requirements and no complex service auth setup. The only sacrifice is some phone battery life.

This is really the killer app for the Index, super excited for it :fire:

In my setup, I’m currently experimenting with a simple Cloudflare Worker that exposes an MCP endpoint I’ve linked to the Pebble app, with a fixed Bearer token secret for authentication.

The Cloudflare Worker then exposes tool calls I’ve setup for specific 3rd party integrations through Composio, which appears to have a generous free tier. They make it easier to add any 3rd party service, authenticate with it through a management UI, and then setup API scopes and things like that.

From there, my Cloudflare Worker is using Composio’s API key to proxy API requests through it to my services.

My first use case that’s working really well is telling Spotify to add the currently playing song to a playlist of my choice. The Worker processes the transcribed text from the Index and fuzzy-matches against my list of playlists, and picks the correct one to add the song to.

From here, I can add more integrations to Composio, and for any tasks I want to support on my MCP server, I can just have my agents (I use Cursor) add the logic for it.