原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Oars

作者:manyoars版本 0.5.5i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.manyoars/oars

安装方法

What it does

Recall from your own past coding agent sessions, kept on your machine.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 开发者工具

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

作者:morluto★ 467,2351 个 skill

Skill · 操作手册

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

作者:multica-ai★ 234,1251 个 skill

Skill · 操作手册未注明许可证

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

作者:Graphify-Labs★ 149,8731 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度18/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分30/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 30 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Oars。按照 https://mcp.popnx.com/i/manyoars-oars.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

让 AI 帮你安装

把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Claude 安装 MCP server Oars,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "oars": { "command": "npx", "args": [ "-y", "@manyoars/oars", "sessions", "recall" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Oars 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 打开电脑版 Claude 应用的设置文件

    SettingsDeveloperEdit Config

  3. 粘贴这些设置并保存文件

    {
      "mcpServers": {
        "oars": {
          "command": "npx",
          "args": [
            "-y",
            "@manyoars/oars",
            "sessions",
            "recall"
          ]
        }
      }
    }
  4. 退出 Claude 再重新打开

  5. 试一试

    用 Oars 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Oars,或回答中出现 Oars 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Oars

Oars 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Oars 的应用

  • 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
  • 需要先在电脑上安装 Node.js(只需一次)
  • 需要先在电脑上安装 Node.js(只需一次)
  • 需要先在电脑上安装 Node.js(只需一次)

B · 开发者工具 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Claude Code 安装 MCP server Oars,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user oars -- npx -y @manyoars/oars sessions recall 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Oars 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --scope user oars -- npx -y @manyoars/oars sessions recall
  4. 在 Claude Code 中输入 /mcp

    应能看到 Oars 在列表中并显示已连接

  5. 试一试

    用 Oars 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Oars,或回答中出现 Oars 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Cursor 安装 MCP server Oars,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "oars": { "command": "npx", "args": [ "-y", "@manyoars/oars", "sessions", "recall" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Oars 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 在 Cursor 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 Oars 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Oars,或回答中出现 Oars 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 VS Code 安装 MCP server Oars,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "oars": { "type": "stdio", "command": "npx", "args": [ "-y", "@manyoars/oars", "sessions", "recall" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Oars 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 在 VS Code 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 Oars 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Oars,或回答中出现 Oars 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Oars 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

安装在电脑上

Claude Code

claude mcp add --scope user oars -- npx -y @manyoars/oars sessions recall

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "oars": {
      "command": "npx",
      "args": [
        "-y",
        "@manyoars/oars",
        "sessions",
        "recall"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "oars": {
      "command": "npx",
      "args": [
        "-y",
        "@manyoars/oars",
        "sessions",
        "recall"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "oars": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@manyoars/oars",
        "sessions",
        "recall"
      ]
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
603/周
许可证i
Apache-2.0
连接方式
在你的电脑上运行
最新版本i
0.5.5
发布到注册中心i
2026年11月14日
代码最后更新i
2026年11月18日
作者
manyoars
软件包
npm: @manyoars/oars
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 manyoars 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

OSV.dev 中没有 @manyoars/oars@0.5.5 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/manyoars-oars.svg)](https://mcp.popnx.com/en/servers/manyoars-oars)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 6136 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 6136 个服务器的 88% 更新
  • 基础检查结果等于或优于此分类中其他 6136 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Oars 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.5.5)于5天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

作者:ahmedkhaleel2004广泛使用★ 1.9万2个月前更新

在云端运行✓ 服务方 · gitdiagram.comPopNx 团队已实际试用

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

作者:Appllama广泛使用★ 52303个月前更新

在云端运行✓ 服务方 · appllama.io

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

作者:omnara-ai广泛使用★ 34172个月前更新

在云端运行✓ 服务方 · omnara.com

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

作者:repowise-dev广泛使用↓ 6506/周★ 8180 整个仓库的星标6天前更新

电脑或云端✓ 服务方 · repowise.dev
与相似项目对比
本项
Oars
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查3/34/44/44/44/45/5
许可证Apache-2.0MITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@manyoars/oars

oars keeps a local, searchable record of your coding agent sessions, across Claude Code, Cursor, Codex, and other harnesses. Ask it about an error and it shows how many past sessions hit it, when, and which tools came next. More at manyoars.com.

Install

npm install --global @manyoars/oars

Node 22.23.4 or later. ESM only. Local recall needs no account.

Or run it once without installing:

npx @manyoars/oars sessions try

Sample output (made-up sessions, from oars sessions try):

$ oars sessions recall --error "unexpected EOF while looking for matching quote"

Bash | bash: -c: line : unexpected EOF while looking for matching quote 3 sessions, 3 errors, first 2026-10-06T10:00:15.000Z, last 2026-10-20T10:00:27.000Z harness 2.1.300; followed by Bash x2, Read x1, Write x1; an edit followed 1 times

$ oars sessions recall --context --cwd C:\work\demo oars recall: errors that recur in this repository's earlier sessions. Check these before retrying:

  • Bash | bash: -c: line : unexpected EOF while looking for matching quote (3 sessions in the last 300; next: Bash, Read, Write)
  • Write | File has not been read yet. Read it first before writing to it. (2 sessions in the last 300; next: Read, Bash, Write)

No coding-agent history yet? oars sessions try runs recall, books, and the hook line over made-up sessions in a throwaway store under your temp folder, labeled synthetic and deleted on exit, and never touches your own store.

Commands

oars --help lists the commands below (oars help shows one command's flags). oars --version prints the version.

These flags work on every command:

  • --json prints one JSON document on stdout instead of text (see below).
  • --api-url sets the platform API. The default is OARS_API_URL, else https://api.manyoars.com.
  • --idempotency-key is the base of the idempotency key (default: a fresh UUID). Rerun a failed command with the same key to replay it.
login

Signs in with your browser (RFC 8628 device flow) and stores the login.

Accounts are not open yet: oars login uses the Many Oars issuer by default, and until Many Oars sign-in at login.manyoars.com is deployed it exits 2 with an error that names login.manyoars.com.

  • --no-browser prints the link and code without opening a browser.
  • --issuer-url is the Keycloak realm URL. The default is OARS_ISSUER_URL. With neither, login uses the built-in Many Oars issuer, https://login.manyoars.com/realms/aor; nothing has to be switched on first. When the built-in issuer does not answer discovery (it may not be deployed yet), with no --issuer-url or OARS_ISSUER_URL, the command prints "Cannot reach Many Oars sign-in at login.manyoars.com (it may not be deployed yet). Pass --issuer-url or set OARS_ISSUER_URL to use another issuer." and exits 2.
logout

Revokes the stored login and deletes it.

keys

oars keys manages the API keys of your account.

  • oars keys create --name creates a key and prints its secret once; the platform keeps no copy. The default authorities are AGENT_OPERATE and AGENT_READ; --authority (repeatable) sets others, and --expires-in-days sets an expiry. --expires-in-days takes 1 to 365; without it the platform sets the expiry, and oars keys list shows it. Replace a key before it expires.
  • --workload limits the key to one workload you created. Such a key may carry only AGENT_OPERATE and AGENT_READ (more is a 400, API_KEY_WORKLOAD_SCOPE_EXCEEDS_CAP), and it works on that workload only.
  • A retry with the same --idempotency-key returns no secret: the command exits 5 and names the key, and you revoke it and create another.
  • Creating or revoking a key needs a signed-in person. With OARS_API_KEY set, any API key gets 403 HUMAN_SESSION_REQUIRED (exit 3) and logging in again does not help: unset it and use the oars login session.
  • oars keys list lists the keys with their prefix, scope, and expiry. A secret never comes back.
  • oars keys revoke ends a key at once. There is no rotate: revoke the key and create another.
telemetry
  • On by default: each command leaves an event in a local spool under /oars/telemetry/, with counts, sizes, and closed words. It never holds session content, prompt text, a file path, a URL, or an argument.
  • oars sends the events in batches, at most once a day, to the pool server in OARS_POOL_URL if you set one, else to the Many Oars pool (https://pool.manyoars.com), which is live. A per-install random id is in each event. Telemetry is off, with no prompt, on a machine whose time zone is in the EU, the EEA, or the UK (no switch overrides that); everywhere else, Many Oars Co. may license Usage Data, the events oars sends, as the first-run notice states.
  • oars telemetry status says whether it is on and why; oars telemetry show prints the spool as stored; oars telemetry report prints your own numbers from it.
  • oars telemetry off stops recording and sending; oars telemetry on resumes it. OARS_TELEMETRY=0 or DO_NOT_TRACK=1 turns it off for the process and wins over on.
  • Every event type and field, with an example, is in docs/telemetry.md.
card
oars card --text                 # your week as a table, sized for a screenshot

oars card --month # the last 30 days as a picture: oars-card-month.png and .svg in this folder oars card --year --out me.png # the last 365 days, saved as me.png and me.svg oars card --week --text # a short plain-text receipt of your last 7 local days, to paste

oars card makes a share-ready card of your own week (the default, the last 7 days), month, or year across every harness, read from the local session store only. It shows your sessions and active days, the harnesses and models you used, tokens by model, tool calls, failed calls and how many were followed by a different next step, how often an edit was verified, commits and how many survived, and cost only where the harness recorded one. A count under the same floor oars sessions books uses prints too few. The depositor row reads ashore: run oars pool join until you sign in; signed in, it reads the number of weeks in which this machine sent a deposit, from the local sent record, and says it is this machine's.

Once a week, the first command you run in a terminal on or after Friday prints one line to stderr, Your week: N sessions, M strokes. \oars card --text\ for the table., never with --json, from a hook, from the MCP server, from a recall, from oars sessions try, or from oars card itself, and only when the week has a session. About one install in ten never sees it; card-line.json in the session store folder records the week and whether it was shown, held, or not_due, and card-line-id holds the id the holdback hashes, copied once from the telemetry install id when there is one, else random, so the arm never changes.

Nothing is uploaded and nothing is sent anywhere: the command makes no network call and prints one prefilled x.com link whose text is the card's own numbers, for you to post if you choose. The card carries no folder name, path, prompt or response text, repository name, or long-tail tool or model name, and posting it unlocks nothing. The picture is a byte-stable SVG and a PNG drawn from it with a built-in font; --text prints the table and writes nothing. --no-cost leaves the cost row out of the picture, the table, and --json.

oars card --week --text (both flags together, with no --month, --year, or --out) prints a different, shorter thing: a receipt of your last seven local days, at most twelve lines of plain text, none over 80 columns with no color. It shows the window's dates, sessions and active days, the harnesses, and two outcome counts only where the store can back them: failed tool calls (counted once per call, so a replayed result is not counted twice), and passing runs, the share of edited prompts with a runner recorded whose last build or test runner passed (only prompts whose verify is passed, failed, or masked are in the count; verify none and na are left out). Codex sessions are left out of both outcome counts, because the Codex reader loses shell outcomes on Codex 0.166 and later, and the receipt says so (a week of only Codex sessions prints outcomes Codex sessions not counted). It carries no path, repository, prompt text, tool or model name, cost, rank, or account row, and an empty week prints a one-line empty receipt and exits 0. Nothing is uploaded; you copy the text yourself.

oars sessions receipt [--out ] prints a Markdown review receipt for one session you choose: the verification commands it ran (tests, builds, linters, and type and format checks, matched against a fixed list in VERIFICATION_FAMILIES), in order, with the result each showed (exit 0, exit , failed, or not recorded), and a count of the other commands, which are not listed. These are commands the session ran and the results it observed on the author's machine; it is not proof the change is correct, and it maps to no pull request. It reads the local store only and sends nothing; it carries no prompt or assistant text, command output, or path (a home or absolute path prints as , and a command is cut to its first line). Commands run in a subagent are left out, and a Codex session's results print not recorded. With no id it lists your five most recent session ids and their dates. You copy the receipt yourself.

statusline
oars statusline            # one line: oars 7d: 12 sessions, 4 active days

oars statusline --color # the same line with the identifier in bold

oars statusline prints one short line of your own last seven local days, for a terminal status line. It reads the local session store only, ignores stdin, makes no network call, sends no telemetry event, and writes nothing. It never edits your settings: you paste the snippet yourself. If the store cannot be read, it prints the identifier alone and exits 0.

To show it in Claude Code, add this to ~/.claude/settings.json (see the Claude Code status line docs):

{

"statusLine": { "type": "command", "command": "oars statusline" } }

Sample output:

oars 7d: 12 sessions, 4 active days
  • oars is the identifier.
  • 7d means the window is your last seven local days, today included.
  • 12 sessions is the sessions with a prompt in that window.
  • 4 active days is the distinct local dates with a prompt in that window.

The line has no path, repository, prompt text, model or tool name, or cost. These are the same counts, with the same rules, as oars card --week --text; its definitions are the ones to read.

sessions

oars sessions keeps a local, deterministic memory of your own coding-agent sessions. The session commands make no model call and no network call, except gold arms, which sends redacted text through your own Claude subscription. oars also records telemetry events (a command's path, its flag names, how long it took, its exit code, and its error class, with a random install id, the oars version, the OS, and the time; never session content, prompts, paths, URLs, or argument values), which oars sends in batches to the pool server in OARS_POOL_URL, else to the Many Oars pool (live) (what telemetry records and how to turn it off).

What it captures: by default, the sessions of every Claude Code project folder and the sessions of Cursor, Codex, Copilot CLI, Gemini CLI, Grok Build, OpenCode, Pi, and VS Code Copilot Chat, plus OpenTelemetry GenAI agent traces (OTLP JSON files) fro

只显示了开头部分;其余内容请在仓库中阅读