A
ashlrai/locus
Identity plane for coding agents: wrong account, impossible
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
官方说明Identity plane for coding agents: wrong account, impossible. Multi-account MCP/CLI bindings so agents never act in the wrong tenant. Works with Phantom: phm.dev
安装与配置
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"ashlrai-locus": {
"command": "npx",
"args": ["locus-cli"]
}
}
}解析自我们于 2026-11-04 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"ashlrai-locus": {
"command": "npx",
"args": ["locus-cli"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio ashlrai-locus -- npx locus-cli
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 3 ★ · ashlrai/locus · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 3 ★ · 1 个来源 · repo
- 安装
npx locus-cli
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx locus-cli。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
ashlrai/locus;我们收录于 2026-11-05;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# Locus
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Your coding agent can't act as the wrong account.
Locus is the identity plane for coding agents. You pin one client. After that, the CLI, the MCP tools, and the local dashboard act only as that client until a person pins again.
That matters on a machine with more than one client. Ambient gh auth, a shared Supabase token, or the last Vercel team can send an agent to the wrong account. A pin makes the other account unavailable.
Agents are first-class users. Start with the commands below. Machine indexes: llms.txt, llms-full.txt, and the agent contract.
For agents ·
30-second start ·
How it works ·
Install ·
FAQ ·
Star
Latest release: v0.6.2 (2026-11-01).
npm package READMEs use version-neutral installation commands to avoid stale pinned releases.
## For agents
One command installs both binaries:
bash
npm install -g locus-cli @ashlrai/locus-mcp
Homebrew and Cargo are in Install options. At the v0.6.2 release, the live Homebrew tap installs v0.6.1, so use npm for v0.6.2.
Read state as JSON. The first key is schema. Failures on stderr use locus.error.v1. No command prints a secret.
bash
locus whoami --json
locus status --json
locus doctor --json
locus version --json
locus topic agent-contract --json
locus doctor --json can exit 0 while verdict is WARN and ok is false. Exit 0 means the findings are setup advice, not that setup is finished.
Print the MCP entries without writing a client config:
bash
locus setup --client claude --print
locus setup --client cursor --print
locus setup --client codex --print
Those entries launch locus-mcp and serve control tools only. For the pinned binding's provider tools, paste the supervised server below. Launch the client from the shell that ran locus hook and locus enter. Restart the client after a re-pin. Agents cannot pin. Ask a person.
Claude Code (.mcp.json) and Cursor (~/.cursor/mcp.json):
json
{ "mcpServers": { "locus": { "command": "locus", "args": ["mcp", "--supervised"] } } }
Codex (~/.codex/config.toml):
toml
[mcpservers.locus]
command = "locus"
args = ["mcp", "--supervised"]
Same paste, by hand, if the client CLIs are installed:
bash
claude mcp add locus -- locus mcp --supervised
codex mcp add locus -- locus mcp --supervised
More copy-paste blocks: docs/copy-paste.md. Rules for agents in this repo: AGENTS.md.
## 30-second start
Run this in one shell. It creates sample bindings, pins personal, and checks that acme is refused. LOCUSHOME keeps the trial off your real ~/.locus.
bash
export LOCUSHOME="$(mktemp -d)" # omit this line to use ~/.locus
npm install -g locus-cli @ashlrai/locus-mcp # or brew or cargo; see Install options
locus quickstart # sample bindings, pin, whoami, doctor
eval "$(locus hook zsh)" # or bash; exports the control capability
locus enter personal # pin from this shell (it supervises the pin)
locus whoami # who your agents are acting as, right now
locus exec --expect personal --no-resolve -- echo ok # runs: personal is pinned
locus exec --expect acme -- echo ok # refused, exit 1, child never starts (pinmismatch)
The echo check uses --no-resolve because it needs no credentials. quickstart does not replace bindings you already have. --no-resolve refuses bindings whose upstreams resolve credentials. For real provider work, supply credentials outside the agent and replace the sample scopes. See the sample exec walkthrough.
Locus is the identity plane for coding agents. You pin one client. After that, the CLI, the MCP tools, and the local dashboard act only as that client until a person pins again.
That matters on a machine with more than one client. Ambient gh auth, a shared Supabase token, or the last Vercel team can send an agent to the wrong account. A pin makes the other account unavailable.
Agents are first-class users. Start with the commands below. Machine indexes: llms.txt, llms-full.txt, and the agent contract.
For agents ·
30-second start ·
How it works ·
Install ·
FAQ ·
Star
Latest release: v0.6.2 (2026-11-01).
npm package READMEs use version-neutral installation commands to avoid stale pinned releases.
## For agents
One command installs both binaries:
bash
npm install -g locus-cli @ashlrai/locus-mcp
Homebrew and Cargo are in Install options. At the v0.6.2 release, the live Homebrew tap installs v0.6.1, so use npm for v0.6.2.
Read state as JSON. The first key is schema. Failures on stderr use locus.error.v1. No command prints a secret.
bash
locus whoami --json
locus status --json
locus doctor --json
locus version --json
locus topic agent-contract --json
locus doctor --json can exit 0 while verdict is WARN and ok is false. Exit 0 means the findings are setup advice, not that setup is finished.
Print the MCP entries without writing a client config:
bash
locus setup --client claude --print
locus setup --client cursor --print
locus setup --client codex --print
Those entries launch locus-mcp and serve control tools only. For the pinned binding's provider tools, paste the supervised server below. Launch the client from the shell that ran locus hook and locus enter. Restart the client after a re-pin. Agents cannot pin. Ask a person.
Claude Code (.mcp.json) and Cursor (~/.cursor/mcp.json):
json
{ "mcpServers": { "locus": { "command": "locus", "args": ["mcp", "--supervised"] } } }
Codex (~/.codex/config.toml):
toml
[mcpservers.locus]
command = "locus"
args = ["mcp", "--supervised"]
Same paste, by hand, if the client CLIs are installed:
bash
claude mcp add locus -- locus mcp --supervised
codex mcp add locus -- locus mcp --supervised
More copy-paste blocks: docs/copy-paste.md. Rules for agents in this repo: AGENTS.md.
## 30-second start
Run this in one shell. It creates sample bindings, pins personal, and checks that acme is refused. LOCUSHOME keeps the trial off your real ~/.locus.
bash
export LOCUSHOME="$(mktemp -d)" # omit this line to use ~/.locus
npm install -g locus-cli @ashlrai/locus-mcp # or brew or cargo; see Install options
locus quickstart # sample bindings, pin, whoami, doctor
eval "$(locus hook zsh)" # or bash; exports the control capability
locus enter personal # pin from this shell (it supervises the pin)
locus whoami # who your agents are acting as, right now
locus exec --expect personal --no-resolve -- echo ok # runs: personal is pinned
locus exec --expect acme -- echo ok # refused, exit 1, child never starts (pinmismatch)
The echo check uses --no-resolve because it needs no credentials. quickstart does not replace bindings you already have. --no-resolve refuses bindings whose upstreams resolve credentials. For real provider work, supply credentials outside the agent and replace the sample scopes. See the sample exec walkthrough.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/ashlrai-locus/)
- 来源
- github · https://github.com/ashlrai/locus
- 按领域浏览
- 开源项目
- Traction
- 3 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。