---
title: "Scheduled agent automations, linked billing with Claude Platform"
date: 2026-11-20T18:38:00.000Z
number: 0317
url: https://railway.com/changelog/2026-11-20-scheduled-agent-automations
---

# Scheduled agent automations, linked billing with Claude Platform

Your agents can get to work before you open your laptop.

This week, give your agent a recurring job and Railway starts the work on schedule. Ask for an overnight error review before standup, a dependency check every Monday, or release notes every Friday. We’re also shipping linked billing with Claude Platform, so your team can pay for Claude usage through its existing Claude Platform organization.

Let’s get into it! 🚄

# Scheduled agent automations

[Schedule an automation, run it, and inspect its latest result from your favorite coding agent](https://cms.railway.com/media/3c6dcd05-8544-4bc5-a83d-d3a6663d4f15-scheduled-agent-automations-running-4k.mp4)

Give your agent a recurring job, and Railway starts a fresh cloud agent in your project at each scheduled time.

Connect a [Railway plugin](https://docs.railway.com/ai/plugins-and-connectors) or the [Railway MCP server](https://docs.railway.com/ai/mcp-server) to the agent you already use. Give it access to the repositories or data sources the task needs, then describe the work and schedule. Here are a few ideas to try:

- “Every weekday at 8 a.m., review overnight production errors, group them by likely cause, and check recent deployments for related changes. Include links to the logs.”
- “Every morning, review yesterday’s merged changes to my API repository. Add regression tests for untested error paths, run the relevant tests, and open a pull request.”
- “Every Monday, check for patch updates to my app’s dependencies. Apply compatible updates, run the test suite, and open a pull request with the results.”
- “Every Friday, draft release notes from the week’s merged pull requests. Group them into features, improvements, and fixes, with a link to each pull request.”
- “Every Monday, query my analytics API for last week’s signup-to-checkout conversion, compare it with the previous week, and identify the biggest drop-off.”

Once your agent has set up a schedule, you can manage it from the dashboard, too. That UI is part of the new dashboard experience we’re working on. To try it, enable the **Railway Agent Dashboard** [flag in your account settings](https://railway.com/account/feature-flags), then open **Automations** in your project. You can create schedules, run them once to check the results, and pause or resume them.

Check out the [Automations guide](https://docs.railway.com/ai/automations) to get started. We’d love your feedback on scheduled automations and the new dashboard experience, so reach out on [Central Station](https://station.railway.com/new?type=feedback) or tag Railway on [X](https://x.com/Railway) or [LinkedIn](https://www.linkedin.com/company/railwayapp/).

# Linked billing with Claude Platform

![Link your Claude organization from Agents settings](https://cms.railway.com/media/c1535191-9065-4981-927d-36cdf3b1656f-65a8a42e-a759-401f-8a55-b731dca3c593-02-providers-before-linking.png)

Link your Claude Platform organization once for the whole Railway workspace. Your team can then select **Claude Platform** models in Railway Agent and cloud agents, and Anthropic bills your organization directly for that usage. There’s no organization API key to share.

Linked billing is in early access for organizations that Anthropic bills directly. Once Anthropic enables your organization, a Railway workspace admin can select the workspace in [Agents settings](https://railway.com/account/agents) and click **Link** on the **Claude Platform Organization** card. A Claude admin approves the link and can set a monthly spend cap for Railway in the Claude Console.

Model requests still run under Railway’s agreements with Anthropic. If you already use your own Anthropic API key on Railway, your usage stays on that key.

Check out the [Claude Platform setup guide](https://docs.railway.com/ai/bring-your-own-models/claude-platform) and tell us how it goes on [Central Station](https://station.railway.com/new?type=feedback).

# Fixes and improvements

- We fixed numeric log searches such as `502` sometimes crashing Deploy Logs or disappearing after a page reload
- We fixed `OR` filters showing logs from other deployments in deployment, build, and cluster log views

