Skip to content

docs(profile): front-load search keywords + add TL;DR for org-page discoverability #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
amavashev merged 1 commit into from
Apr 30, 2026
Merged

docs(profile): front-load search keywords + add TL;DR for org-page discoverability #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 7 additions & 15 deletions profile/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,22 +1,14 @@
# Runcycles — Rein in autonomous chaos ⚡️
# Runcycles — Runtime budget and action authority for AI agents

**The production runtime for the Cycles protocol.**
**Open-source enforcement layer for AI agent governance: hard limits on cost, risk, and tool actions before LLM agents execute.** Multi-tenant, concurrency-safe, and self-hostable. SDKs for Python, TypeScript, Rust, and Spring Boot; MCP server for Claude Desktop, Cursor, and Windsurf.

**Cycles** defines how agents reserve budget, commit spend, and release unused reservations.
- **What** — a protocol-level runtime that enforces `reserve → execute → commit / release` on every AI agent call, preventing runaway spend, unauthorized tool actions, and tenant boundary violations before they happen.
- **Who** — AI platform teams, agent framework builders, and SaaS operators running autonomous LLM agents in production. Production-grade for OpenAI, Anthropic, MCP, OpenAI Agents SDK, LangChain, and CrewAI workloads.
- **Why** — rate limits and dashboards observe failure after the fact. Cycles prevents it — by making cost and action authority a property of the runtime, not the application.

**Runcycles** enforces those rules in production — atomically, under concurrency, across retries.
👉 **Start with [Cycles Docs](https://runcycles.io)** · **[Protocol Spec](https://github.com/runcycles/cycles-protocol)** · **[Reference Server](https://github.com/runcycles/cycles-server)** · **[Runaway Demo](https://github.com/runcycles/cycles-runaway-demo)**

>Think: **Cycles** is an open protocol. **Runcycles** is your server.

Runcycles enforces one rule:

**reserve exposure before execution, then commit actual usage or release the remainder afterward.**

👉 **Start with [Cycles Docs](https://runcycles.github.io/docs)**
👉 **Experience Cycles with [Runaway Demo](https://github.com/runcycles/cycles-runaway-demo)**

👉 **Read the [Protocol](https://github.com/runcycles/cycles-protocol)**
👉 **Deploy the [Reference Server](https://github.com/runcycles/cycles-server)**
---

## Start here

Expand Down
Loading