AgentRail AgentRail 是一个以本地为先的代理编码控制平台。它为代理提供了一个紧凑的 API,用于项目循环:接收请求、执行代理任务、处理结果并将结果返回给客户端。
AgentRail AgentRail 是一个以本地为先的代理编码控制平台。它为代理提供了一个紧凑的 API,用于项目循环:接收请求、执行代理任务、处理结果并将结果返回给客户端。
AgentRail is a local-first control plane for coding agents. It gives agents one compact API for the project loop: issue intake, routing, assigned work, PR submission, CI, review feedback, and shipping.
The source-available repo is a self-managed single-instance runtime. It is built for local evaluation and self-hosting. The planned AgentRail Cloud product is the managed team/fleet layer for hosted connectors, shared run history, routing, wakes, SSO/RBAC, audit, dashboards, and reliability.
availableActions.Prerequisites:
npm.Install the CLI:
npm install -g @agentrail-core/cliInitialize AgentRail:
agentrail initYou can also run the first command without a global install:
npx @agentrail-core/cli initThe interactive setup writes local config under ~/.agentrail, creates the
local operator bootstrap, and can create your first local agent. It does not ask
you to hand-write API keys or edit a seed task store.
Start the local API:
agentrail server startIn another terminal, verify setup:
agentrail doctor --agent-id agt_exampledoctor is the success gate. It checks the local API, agent credentials,
profile/routing state, and whether the selected agent can see assigned work.
AgentRail sends anonymous product telemetry by default to improve setup, provider reliability, and agent lifecycle behavior. Telemetry goes to PostHog EU Cloud and uses an anonymous install ID.
Telemetry does not send source code, issue text, PR diffs, prompts, terminal logs, environment variables, secrets, tokens, or raw provider payloads.
agentrail telemetry status
agentrail telemetry off
agentrail telemetry onProvider connections are optional and can be added after init.
agentrail provider connect github
agentrail provider connect circleci
# AgentRail will ask for the full CircleCI project slug, for example:
# circleci//
agentrail provider connect linearInteractive provider setup asks for secrets in hidden prompts and writes them to
local env files. Non-interactive automation can still use environment variables
such as GITHUB_TOKEN, CIRCLECI_TOKEN, LINEAR_API_KEY, and webhook secrets.
provider connect finishes by running provider readiness, applying safe local
setup fixes, and reporting any remaining account or repo settings AgentRail
cannot change for you. provider test uses the same readiness check
as provider doctor ; it is not just a token check.
GitHub setup also asks whether AgentRail should wait for code review before
shipping PRs. The default follows GitHub's own review signals, but you can
choose to always require an approval for AgentRail-created PRs or to skip
approval waits once CI is green.
CircleCI setup verifies project access, creates .circleci/config.yml when a
starter config is safe, and configures how AgentRail will obtain pipelines for
AgentRail branches. If automatic CircleCI branch builds are not available,
AgentRail uses the CircleCI pipeline-run API when the token can access a
pipeline definition.
Import a Linear issue into AgentRail after connecting Linear:
agentrail linear import ENG-123Imported provider issues go through the routing engine. If routing is not configured, AgentRail fails closed instead of silently creating unassigned work.
Create or update local agent profiles:
agentrail agent create
agentrail agent update --agent-id agt_exampleUse a built-in role template, or install your own YAML-backed role template:
agentrail agent create --role-template frontend-ui
agentrail agent create --role-template-file ./agent-roles/payments-backend.yamlCustom templates are validated and copied into
~/.agentrail/agent-role-templates/, so later agents can reuse them with
--role-template .
During agentrail init and agentrail repo add, AgentRail also creates an
editable repo map under ~/.agentrail/repo-maps/.yaml. Role templates use
repo-agnostic areas such as frontend_source, tests, and ci_configuration;
the repo map translates those areas to the actual folders in your project.
The starter map is generated deterministically. During interactive setup you can
also let a local Codex, Claude Code, or Cursor runner propose a richer map;
AgentRail validates the proposal, shows you the summary and warnings, and falls
back to the starter map if the local runner is unavailable or uncertain.
When a managed agent starts work, AgentRail combines the selected role template
with the repo map for that repository and passes a compact role brief to the
runner. The brief points the agent at relevant repo areas and validation
expectations, while AgentRail still owns lifecycle actions such as PR creation,
CI watching, review handling, and shipping. If a repo map is missing or
incomplete, AgentRail still runs the agent and includes a warning in the run
context. Run agentrail doctor to check repo-map coverage.
Inspect local config and connected repos:
agentrail config show
agentrail repo list
agentrail provider list
agentrail provider status
agentrail provider doctorRepair a task source if older imported data needs to be corrected:
agentrail task source repair --task-id tsk_... --file source-patch.jsonFor a server-only smoke run:
docker compose up --buildThe API listens on http://127.0.0.1:3000 by default. CLI-assisted onboarding
is still the recommended path for a useful local setup because it creates local
agent, routing, and provider state.
Common repo commands:
git clone https://github.com/oxnw/agentrail.git
cd agentrail
npm install
npm link
npm run typecheck
npm test
npm run lint:openapiThe package exposes the agentrail binary:
agentrail --helpAgentRail is source-available software, not open source. See LICENSE.
暂无开放 Issues,或尚未同步最近议题。