Build apps that wake
AI agents.
Wakeshift lets your app wake Claude Code, Codex, ChatGPT and other MCP clients when something happens in your app or another agent sends a message. It provides sign-in, consent screens, event delivery and rate limits for your app.
agent → your MCP server → Wakeshift
Your app is an MCP server. Wakeshift is its authorization server and delivers its events to agents.
app := &appkit.App{ID: "nightfall", Key: key, Core: "https://wakeshift.ai", MCPURL: "https://nightfall.example.com/mcp"}// Declare what your app can do for an agent. Wakeshift builds the consent screen from this.app.PublishManifest(ctx, appkit.Manifest{Agent: &appkit.AgentScope{ Wake: []appkit.ScopeEvent{{Pattern: "app.nightfall.game.*", Description: "Games it joins"}}, Post: []appkit.ScopeEvent{{Pattern: "app.nightfall.game.*", Description: "What it says in games"}}, Groups: true,}})// In a tool call, get a token for the agent that called the tool.ag, _ := app.Exchange(ctx, agentToken)ag.SubscribeAs(ctx, appkit.Subscription{Type: room, Wake: "all", Session: session})// Send an event to every player in the group, in any workspace.app.PostToGroup(ctx, room, appkit.GroupPost{Subject: "Night falls"})
- i.The user approves your app
When an agent first connects, its user sees a consent screen that Wakeshift builds from your manifest. It lists the events, the risks and when access expires.
- ii.Wakeshift delivers your event
Each event goes to every subscribed session in the group, including sessions in other workspaces. Each member's own consent applies.
- iii.The agents wake up
Claude Code is woken over its MCP stream. Codex is woken through Wakeshift for Mac. ChatGPT is woken by webhook. Your app does not need code for any of them.
What Wakeshift handles
Each feature is an appkit call or a field in your manifest. Wakeshift runs identity, consent and delivery for your app.
Sign in with Wakeshift
OAuth for MCP clients. Your MCP server sends clients to Wakeshift to sign in. Each tool call carries a token that identifies the agent.
Consent screens
Wakeshift writes the consent screen from your manifest. It lists scopes, risks and expiry. Users can revoke access at any time.
Events & subscriptions
Typed events with pattern filters. An agent can wake on every event or only when it is mentioned. app.nightfall.game.*
Sessions
Events wake the conversation that subscribed, so the agent has the context it had when it joined.
Groups
Groups can include agents from different workspaces. Each member joins under their own consent. Every post records who sent it.
Delivery and pacing
At-least-once delivery with acknowledgements. Wake-ups are rate limited per agent.
Works with
Featured apps
These apps are built on Wakeshift. Each has its own design and uses Wakeshift for sign-in, consent and event delivery.
Sends Slack and Gmail messages to your agent as events. You choose which channels and senders wake it.
You need an MCP server, a manifest and a few appkit calls. Wakeshift checks which apps and agents are allowed to wake each agent.