Codex Triggers

Inspiration

With the release of recent 5.6 models, i genuinely belived that codex can literally do any task. I have been prompting it all day and it has been crushing all tasks. I have started feeling that i am the bottleneck now. Like how much can i even prompt. I looked up the recent ideas like "loops" and recently "graphs". Thinking about them made me realised, everything are just events.

Like if i could make a system that manages triggers and events and runs Codex based on events, i can create loops, i can create graphs, anything. Think of this example - if you have a bug tracker, lets say adding a entry could be a trigger and you could set codex to run on that trigger to try to recreate the bug and update the tracker with re-creation steps. That could be event for another agent that could fix the bug and create a pr. Creating PR could trigeer a codex session for PR review.

As i thought more deeply about this i understood how powerful is this idea. So i built it.

What it does

Codex Triggers is a macOs (for now) application turns any event into a Codex task.

Any event in, public webhook URLs (GitHub, Stripe, iPhone Shortcuts…), cron or one-time schedules, and persistent "Service Triggers" that can watch files, Wi-Fi changes, or anything else Node can listen to.
Codex out, every event becomes a templated Codex task with your chosen project, model, and reasoning effort. Finished tasks land in the Codex sidebar; macOS notifications deep-link straight back to them.
Created by conversation, the app bundles a skill that teaches Codex to operate its local API. You press "Ask Codex," describe the automation in plain language, and Codex writes the Trigger code, configures the delivery, registers the webhook, and runs a test. It even writes the iPhone Shortcut setup steps when the trigger starts on your phone.

How we built it

It's a TypeScript monorepo with a node based hono server and an electron desktop app.

Challenges we ran into

The most tedious thing was macOS notifications. Codex had to spend an hour fixing it :) Another big thing was handling tunneling. We used tailscale for it.

Accomplishments that we're proud of

This application enabled so many use cases that i couln't even have thought before.

Codex running automatically anytime something happens on your mac
Codex running when a webhook sends an event. This integrates with Apple shortcuts and enables so much cool stuff.

What we learned

The biggest shift i am adapting is to geeting myself out of the loop and have intelligence run for every so many new aspects of my day and life. Its non intuitive and i am still learning new use cases every day.

What's next for Codex Triggers

There is so much more. A whole new area unlocks called environments. Creating enviroments where codex will run autonomously on events. Right now, these are in my mac, but they can be any cloud, any machine. Creating good env, so codex does its job, verify work. Troggers + Environments + Agents are converging towards creating Agent Factories.