
Preloop
io.github.preloop由 GitHub 账号 preloop 发布v0.17.1更新于 Oct 31, 2026
Open-source AI agent control plane and software factory: govern every tool and model call.
概览
Preloop 是一个远程 MCP 端点,接入开源 AI 智能体控制平面,对每次工具调用和模型调用进行治理、归因与预算控制。
- 可以做什么
- 把智能体接入受治理的 MCP 入口,工具调用可被允许、拒绝或挂起等待人工审批
- 以 YAML 和 CEL 编写策略即代码,设置理由说明要求与审批流程
- 让模型调用经过网关,按模型、智能体、会话、API 密钥和流程统计并限制花费
- 由 GitHub、GitLab、Bitbucket、Jira、Webhook 或 CI 触发流程启动智能体,内置 PR 审查、议题实现、安全审计等预设
- 查看统一会话时间线,涵盖工具调用、模型调用、策略决定、审批、花费与结果
- 搜索会话、导出审计记录及 DORA 或 OTLP 数据,并用操作员备注引导运行中的智能体
- 适用场景
- 适合平台、安全和工程团队在智能体接触生产系统之前加以治理,并掌握成本与审计轨迹。也适合把工单或 CI 事件转化为有边界、可由人工以拉取请求形式审阅的智能体工作。
- 运行要求
- 需要访问 preloop.ai 上的远程 streamable HTTP 端点,路径为 /mcp。OAuth 为必需;支持 OAuth 的客户端可省略 Authorization 头,否则需以 Bearer 令牌形式提供 Preloop 访问令牌。还需要 Preloop Cloud 账户或自建控制平面,以及用于注册、登录和接入智能体的 Preloop CLI。
安装
在 SourceWeft 中
- 打开 控制台中的 Preloop,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.preloop%2Fpreloop/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"mcpServers": {
"preloop": {
"type": "http",
"url": "https://preloop.ai/mcp/v1"
}
}
}README
[Preloop Logo] Preloop
[CI] [Release] [PyPI] [Python 3.11+] [License] [OpenSSF Best Practices] [OpenSSF Scorecard]
The open-source AI agent control plane and software factory.
Preloop is one self-hostable service that sits between your AI agents and everything they reach, and runs agents for you when work arrives. Every tool call and every model call is governed, attributed and visible, whether a person started the agent or a ticket did. You see gateway spend by model, agent, session, API key and flow, and cap it with budgets. Imported Copilot usage is displayed separately as vendor-reported data.
It has two halves, and the same policies, budgets and session timeline apply to both:
- Control plane. An MCP firewall that allows, denies or holds any tool call for human approval; an AI model gateway with budgets and attribution; policy-as-code in YAML and CEL; one runtime timeline per session.
- Software factory. Flows run agents, in hosted containers or on your own runners, when GitHub, GitLab, Bitbucket Cloud, Jira, a webhook or a CI job fires. Presets review pull requests, implement issues, triage tickets, scan for vulnerabilities and collect evidence packs. A human can steer a running agent from the console, phone or watch, and the work lands as pull requests you can review.
Both halves are multi-user: invite colleagues and organize teams in Preloop (OSS). Each user can connect devices, runners and agents. Preloop (OSS) has no roles or access controls between users of an account; those are in Preloop Cloud and Preloop Enterprise.
Who it is for:
- Platform and security teams that need agents governed before they reach production systems.
- Engineering teams running coding agents that want to see the cost and keep an audit trail.
- Teams that want tickets and events turned into bounded agent work they can review.
MCP clients connect to /mcp; existing /mcp/v1 configurations remain compatible.
See the tested MCP protocol matrix
for modern discovery, legacy initialization, and SDK migration details.
Works with OpenClaw, Claude Code, Codex CLI, Cursor, Gemini CLI, Hermes, OpenCode, Devin, Copilot CLI, and any MCP-compatible agent.
Your first five minutes
preloop agents discover finds local agent configs and reports what each adapter supports. preloop agents onboard configures them: calls routed through the managed MCP entry reach the MCP Firewall, supported model routes use the Gateway. To talk to a running agent, install the runtime plugin with preloop agents install-plugin (or preloop claude for Claude Code). Full walkthrough: onboard local agents.
[Preloop onboarding local agents into the control plane]
Watch it work
Onboarding, the MCP firewall, human approvals, and cutting session cost. Recorded against a real stack, no slideware.
[Preloop video series: see them, govern them, cut their cost]
What you get
Jobs teams otherwise buy from several vendors, in one Apache 2.0 stack:
The software factory
One loop, end to end: an issue event arrives from GitHub, GitLab, Bitbucket Cloud or Jira. A flow starts an agent in a hosted container or on your own runner. Every tool call it makes passes the same firewall and approvals as your own agents, and every model call is charged to the flow's budget. The agent opens a pull request; the Pull Request Reviewer reviews it; review or CI feedback resumes the implementation on the same branch, and the result is a pull request you can review. You can steer the run with an operator note at any point, and the whole run is one timeline.
21 presets ship in this repository, including:
- Issue Triage Assistant and issue refinement
- Pull Request Reviewer
- Delivery Report: a weekly report with proposals for human decisions and project reruns. See what landed, what the available evidence supports against stated criteria, and which gaps deserve investigation
- Automated issue implementation
- Security audit presets: SBOM verify, exploit check, release audit. They collect machine evidence for CRA- and EU AI Act-style reviews. That is not a conformity assessment, certification, or legal advice.
- Observe / Eval
- Component due diligence, architecture and strategy review, repo code health review
- Standards compliance walk, release backport, weekly model price review
Or write your own. Trigger from CI with the run-flow GitHub Action; run agents on private runners; let a flow start child flows with flow delegation. Tracker setup: Bitbucket and Jira quickstart; Bitbucket Data Center is available as an opt-in provider.
Policy-as-code
Check a sample call before saving with Test this rule or Simulate in the console. Ship it with preloop policy apply <file> (validate / diff / export also exist).
[Preloop dashboard with live agent and gateway usage]
More capabilities
- Model providers: OpenAI, Anthropic, Google, Amazon Bedrock, Azure OpenAI, Alibaba Cloud Model Studio, DeepSeek, Mistral, Moonshot, Z.ai, OpenRouter, any OpenAI-compatible endpoint, and runner-proxied local models. Reviewed model pricing; unpriced models stay visibly unpriced.
- Restricted CI identity: a machine identity bound to one project and one flow for CI jobs, with an optional read-only native GitHub App clone mode and separate result publication. Guide.
- Account kill switch: blocks gateway and tool traffic and stops managed flow runs, with audited recovery. Guide.
- Durable audit delivery: opt-in transactional intents for approvals, policy decisions and tool outcomes, with restart replay and backlog alerts. Operations guide.
- Session search: keyword search by default, semantic as an opt-in, every search audited. Saved searches.
- DORA exports: the AI-agent slice of the ICT inventory and incident record. Guide.
- OTLP export: off by default; emits OpenTelemetry GenAI spans. Guide.
- Chat: Slack, Mattermost, and Discord for questions, approval votes and operator notes. Chat connections.
- Event-driven employees: managed agents doing bounded tasks from tracker and error events. Guide.
- Remote sessions and deployment: remote sessions, SSH and GCP agent deployment, environments and recovery.
- Runtime plugins: Pi and DeepSeek Harness, Nanobot, OpenClaw, Hermes, runtime adapters.
Everything else: docs.preloop.ai.
Getting started
The CLI is a client. It talks to a control plane: Preloop Cloud or a stack you run.
Cloud (fastest)
Self-host (Docker Compose, data stays on your machine)
Console: http://localhost:3000. CLI login commands: CLI authentication. TLS, SMTP, upgrades and Kubernetes: Install the OSS stack, Helm chart helm/preloop, compatibility policy. Docker Compose and Helm are the supported install surfaces; this repository does not ship Terraform modules. The local upgrade acceptance harness verifies release-to-candidate migrations, data and credentials in disposable Compose and kind stacks.
Credential storage upgrades keep the existing encryption key and run as a normal rolling upgrade; read the credential storage upgrade guide before upgrading an existing installation.
Production self-host: SECRET_KEY is required or the app refuses to start, and the Helm chart refuses to install while environment.jwtSecret is empty or a placeholder (see helm/preloop/README.md). The development docker-compose.yml ships development-only credential defaults; override them with a .env file (start from .env.example). Telemetry is a daily pseudonymous version check-in; set PRELOOP_DISABLE_TELEMETRY=true to disable. Event list: SECURITY.md.
Open-source alternative to AWS Bedrock AgentCore
Same core jobs (runtime, gateway, identity, observability, policy), vendor-neutral and self-hostable. Full comparison: preloop.ai/vs/aws-agentcore.
Also compare: LiteLLM, Portkey, Helicone, MintMCP, Lunar, Runlayer, Zenity.
Editions
Unqualified Preloop is this repository (Apache 2.0, self-hosted). Preloop Cloud is the hosted service at preloop.ai. Preloop Enterprise is the commercial self-hosted edition. Cloud and Enterprise include support plans. Cloud billing owners can compare usage from the previous three completed months in Account settings before requesting a plan-change quote.
Your data: self-hosted, nothing leaves your network except the optional daily version check. On Preloop Cloud, sessions are stored only to give you search, audit trails, cost reports and policy enforcement; they are not used to train models and are not sold or shared. Details: Security & Privacy.
Governance itself is open source: every model provider, flows, private runners, session search, operator notes, the audit trail, single-approver workflows and budgets scoped to the account, a flow, an API key or a managed agent. What is commercial is the organizational layer on top:
Preloop (OSS) supports multiple users on one account, with no access controls between them: every user of an account can do everything in that account, including inviting and removing colleagues and managing teams. Accounts stay isolated from each other. Public signup, if enabled, creates a separate account. All access control (roles, owner protection, RBAC/ABAC) is in Preloop Cloud and Preloop Enterprise.
Working in this repository
Community
Discord for help, feedback, and the founder's build log.
Contributing
See CONTRIBUTING.md. Maintainers: follow the protected-branch release process.
License
Apache License 2.0. Copyright (c) 2026 Spacecode AI Inc.
Release assets carry signed Sigstore build provenance and checksums (verification). The release SBOM audit gate checks both architectures of every release image and the tag's security workflows. Windows CLI notes: windows-cli.md, code signing policy. Free code signing provided by SignPath.io, certificate by SignPath Foundation.
来源:README.md,提交 2edd413
工具
0版本历史
1- v0.17.1最新Oct 24, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分