
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 分