docs(chatkit): document scheduled routines

chatkit.mdx

@@ -4,11 +4,12 @@ description: "Connect conversations and external events to your agent."
 icon: "messages"
 ---
 
-ChatKit connects an agent endpoint to the places where work begins. It stores sessions and messages, delivers each turn as a signed HTTPS request, and streams the agent's response back to the channel. There are three ways to trigger an agent run through ChatKit:
+ChatKit connects an agent endpoint to the places where work begins. It stores sessions and messages, delivers each turn as a signed HTTPS request, and streams the agent's response back to the channel. There are four ways to trigger an agent run through ChatKit:
 
 1. **Chat providers**: These are first-class integrations with third-party chat providers.
 2. **Vercel AI SDK chat provider**: This managed provider exposes your agent through a Vercel AI SDK-compatible endpoint for custom clients.
 3. **Signals**: These are events from third-party providers that Tilde delivers to your agent.
+4. **Routines**: These send a saved prompt to an agent on a recurring schedule.
 
 Configure chat providers for conversations from Slack, GitHub, and other supported channels. Use signals when an external event should start or continue a session without first arriving as a chat message.
 
@@ -82,6 +83,19 @@ Use [Mission Control](https://api.trytilde.ai/mission-control) to invoke your ag
   Mission Control requires the **Vercel AI Endpoint** ChatKit provider to be enabled for your agent.
 </Info>
 
+### Schedule a routine
+
+Use a Routine when an agent should start the same kind of work on a recurring schedule, such as reviewing overnight alerts every weekday morning.
+
+1. Go to **ChatKit** → **Routines** and click **New routine**.
+2. Select the agent and enter a title and prompt.
+3. Choose a plain-English schedule or switch to raw cron syntax for a custom schedule.
+4. Save the Routine. Select it from the grid later to edit, disable, or delete it.
+
+Routine schedules use UTC and run with minute-level precision. Each run creates a Mission Control session named after the Routine and sends the saved prompt to the selected agent. The Routine page shows its next run, latest run, and latest error.
+
+Routines are included in portable workspace state. Their title, prompt, schedule, enabled state, and agent relationship are exported. Run history, generated sessions, cached next-run time, and scheduler locks are runtime state and are not exported.
+
 ### Provider-specific message metadata
 
 Supported chat providers add validated metadata to the endpoint context. Use the provider-specific property inside your `chatKitEndpoint` handler.

llms.txt

@@ -9,7 +9,7 @@ Tilde lets developers and agents configure off the shelf third-party tools, depl
 - Tools: Off the shelf integration with hundreds of providers, add your own custom tools & spin up secure MCP servers that house them
 - Memory: Create a peristent brain and personal notepad for your agent or share it across multiple agents
 - Skills: Deploy Skills registries to group skills together and make them available to agents
-- ChatKit: Integrate with third party chat providers, have external webhook events trigger agent runs or plan repeat prompts to run on schedule
+- ChatKit: Integrate with third-party chat providers, trigger agent runs from external events, or schedule recurring prompts with Routines
 
 These features are all exposed through cloud API’s that hide away the detail.
 

llms/chatkit.md

@@ -42,6 +42,12 @@ Bound tenant, target-agent, and ingress-channel fields are supplied by Tilde and
 
 Use the Vercel AI Endpoint provider when the user wants to test the agent in [Mission Control](https://api.trytilde.ai/mission-control).
 
+## Schedule recurring prompts
+
+ChatKit Routines send a saved prompt to a registered agent on a recurring UTC schedule. Configure them in **ChatKit** → **Routines**. Prefer the plain-English schedule choices; use raw cron only when the required minute-level schedule is not represented by a preset.
+
+Every run creates a Mission Control session named after the Routine. Routine configuration is portable state: title, prompt, schedule, enabled state, and the target-agent reference round-trip. Do not expect cached next-run times, run history, generated sessions, errors, or scheduler locks to survive an export and import.
+
 ## Trigger work with Signals
 
 Signals turn provider events into ChatKit messages.

llms/state.md

@@ -1,9 +1,11 @@
 # Export and import Tilde state over Global MCP
 
-Tilde resource state is portable even though Tilde does not require Terraform. Keep `tilde.state.yaml` beside a custom agent so another workspace can reproduce its agents, ChatKit providers, tools, MCP servers, skills, wikis, memory bindings, reverse proxies, and relationships.
+Tilde resource state is portable even though Tilde does not require Terraform. Keep `tilde.state.yaml` beside a custom agent so another workspace can reproduce its agents, ChatKit providers and Routines, tools, MCP servers, skills, wikis, memory bindings, reverse proxies, and relationships.
 
 State does not contain API keys, signing keys, provider credentials, conversation history, or memory content.
 
+For a ChatKit Routine, state contains the title, prompt, UTC schedule, enabled state, and target-agent reference. It excludes the cached next run, previous runs and sessions, errors, and scheduler locks.
+
 Curated hosted MCP connections export their stable catalog provider identity and declarative endpoint/authentication configuration. Dynamic OAuth client IDs, token endpoints discovered for that registration, access tokens, and refresh tokens are environment-specific and are not exported. On import, Tilde repeats discovery and dynamic client registration, then returns a one-time authorization URL. Manual OAuth configuration remains portable, while its user credential is reconnected through the normal pending-credential flow.
 
 Use `https://api.trytilde.ai/mcp`. Call `tilde_whoami`, select a workspace, and pass its `team_id` to every function below.

terraform.mdx

@@ -7,10 +7,12 @@ Well, not exactly. Tilde does not require a Terraform provider, but all Tilde re
 
 ## The `tilde.state.yaml` file
 
-`tilde.state.yaml` describes the desired configuration for resources in a workspace. It can include ChatKit agents and providers, MCP servers, tool providers, skill registries, wikis, memory-bank bindings, reverse proxies, and their relationships.
+`tilde.state.yaml` describes the desired configuration for resources in a workspace. It can include ChatKit agents, providers, and Routines, MCP servers, tool providers, skill registries, wikis, memory-bank bindings, reverse proxies, and their relationships.
 
 State files can declare variables for values that change between environments, such as an agent endpoint URL. They do not contain API keys, signing keys, third-party credentials, conversation history, or other runtime content. An import returns generated values separately and leaves credential-backed resources pending until you connect the corresponding accounts.
 
+ChatKit Routines export their title, prompt, UTC schedule, enabled state, and a portable reference to the target agent. Cached next-run times, run history, generated sessions, errors, and scheduler locks remain environment-specific runtime state.
+
 Hosted MCP provider connections preserve their catalog provider identity, endpoint configuration, authentication mode, tool provider, and MCP mappings. API keys, bearer tokens, OAuth client secrets, access tokens, and refresh tokens remain encrypted credential references rather than state values.
 
 OAuth providers that use dynamic client registration must register a new client in the destination environment because the redirect URI and client registration belong to the source environment. Import recreates the provider and returns a one-time authorization URL. Manual OAuth providers keep their pre-registered client configuration and ask you to reconnect the user credential separately.