@gitroll/tacitt-cli

中文文档
0.6.18发布于 2026/11/16UNLICENSEDES Module近 30 天下载 4818

Private local session review and export for coding agents

原始使用文档

Tacitt CLI

Local session review, privacy decisions and reviewed export/Send for coding agents. Requires Node.js >=24.19.0 <25 and npm. Package acquisition does not need an npm login or organization membership.

npx --yes @gitroll/tacitt-cli@latest skill.install

Then use $tacitt in a fresh Codex conversation or /tacitt in Claude Code. Select one client with --agent codex or --agent claude; use --scope project for a workspace-local installation. The installer pairs the Skill with this exact CLI version, preserves verified previous release assets for existing tasks, and reports unmanaged-file collisions. Installation alone starts no scan and resets no source logs, state or existing exports.

Tacitt has three surfaces: the Skill, the Skill panel that the Skill opens, and the CLI commands the Skill runs (tacitt --help lists them). Running tacitt with no command prints how to start the Skill.

For a local export without Send, run these CLI commands in order. tacitt stands for npx --yes @gitroll/tacitt-cli@latest. Each command prints JSON. Take runId, revision, settingsVersion and dictionaryRevision from the previous command's output, because each step raises the revision. slots picks workspace ZIPs by position. The echo ... | tacitt ... --input - form works in sh and PowerShell; in cmd.exe, save the JSON to a file and pass --input FILE. Manual upload to Passport from the CLI is not available yet.

tacitt workflow.startDiscovery            # operationId
tacitt operation.wait <operationId>
tacitt workflow.getCurrent                # runId, revision
echo '{"protocolVersion":1,"runId":"<runId>","expectedRevision":<revision>}' | tacitt workflow.chooseMethod --input -
echo '{"protocolVersion":1,"runId":"<runId>","expectedRevision":<revision>,"expectedSettingsVersion":<settingsVersion>,"mode":"configured","changes":[]}' | tacitt processing.batch --input -
echo '{"protocolVersion":1,"runId":"<runId>","expectedRevision":<revision>}' | tacitt workflow.reviewPending --input -
echo '{"protocolVersion":1,"runId":"<runId>","expectedRevision":<revision>,"expectedDictionaryRevision":"<dictionaryRevision>"}' | tacitt workflow.package --input - --async
tacitt operation.wait <operationId>
tacitt delivery.list                      # result id
echo '{"resultId":"<id>","slots":[0],"artifact":"primary","output":"export.zip"}' | tacitt delivery.issue --input -

The processing.batch step applies the configured cleanup and redaction. Without it, the export is the original session content with no redaction or anonymization.

Global sensitive terms and the bundle library are set through the CLI only. sensitiveTerms.replace replaces the whole list; take revision from sensitiveTerms.get ("empty" before the first save). bundleLibrary.save takes effect at the next CLI start.

tacitt sensitiveTerms.get
echo '{"expectedRevision":"<revision>","terms":["Acme Corp","project-x"]}' | tacitt sensitiveTerms.replace --input -
tacitt bundleLibrary.get
echo '{"directory":"/absolute/path/to/bundles"}' | tacitt bundleLibrary.save --input -

The echo '...' | lines work in sh and PowerShell. In cmd.exe, drop the single quotes and put | right after the JSON:

echo {"expectedRevision":"<revision>","terms":["Acme Corp","project-x"]}| tacitt sensitiveTerms.replace --input -

The native Skill presents decisions in a focused panel. Source consent precedes classification and privacy analysis. The current model provider receives frozen original main conversations and retained tool results before privacy masking; this workflow is not local-only. Send separately authorizes packaging/upload of the selected reviewed material to the signed-in Tacitt account. Keep session data and panel capability URLs private.

State from incompatible previews is not silently migrated. Keep the pinned CLI for old tasks and use a separate state directory when required; installing the Skill does not erase private payload files or import them into a fresh store. Windows verification remains partly advisory; prefer macOS or Linux and review reported platform limitations.

Tacitt retains UNLICENSED package metadata. Bundled Web dependency notices are in dist/web/THIRD_PARTY_LICENSES.md. Source and current guidance are maintained at gitroll-dev/tacitt-cli. The repository contains proprietary source; public visibility does not grant an open-source license. All rights are reserved; reuse requires separate permission from the rights holders.

For a custom Passport deployment, set SESS_PILOT_PASSPORT_WEB_ORIGIN to its trusted profile website origin alongside the custom API origin. The published-ID lookup uses the declared web origins for the standard production and development APIs.

版本与发布记录

@gitroll/tacitt-cli 共发布 27 个版本,首次发布于 2026/10/29;过去 12 个月发布了 27 个版本。

版本发布日期距今
0.6.18latest2026/11/16今天
0.6.172026/11/16今天
0.6.162026/11/151 天前
0.6.152026/11/151 天前
0.6.142026/11/151 天前
0.6.132026/11/151 天前

关于 @gitroll/tacitt-cli 的常见问题

@gitroll/tacitt-cli 是什么?

Private local session review and export for coding agents

如何安装 @gitroll/tacitt-cli?

在项目目录运行 npm install @gitroll/tacitt-cli,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 tacitt,可以用 npx tacitt 直接运行。

@gitroll/tacitt-cli 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/gitroll__tacitt-cli 是否存在。

@gitroll/tacitt-cli 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@gitroll/tacitt-cli 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=24.19.0 <25。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@gitroll/tacitt-cli 可以商用吗?

@gitroll/tacitt-cli 使用 UNLICENSED 许可。作者声明为 UNLICENSED,即不授予公开使用许可(与公共领域的 Unlicense 不同)。使用前需获得作者授权。以上为概括,不构成法律意见,请以许可原文为准。

@gitroll/tacitt-cli 的下载量有多少?

根据 npm 官方下载统计,@gitroll/tacitt-cli 在 2026/10/17 – 2026/11/15 这 30 天内被下载 4,818 次,日均约 161 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@gitroll/tacitt-cli 还在维护吗?

最新版本 0.6.18 发布于 2026/11/16(今天);至今共发布 27 个版本,其中过去 12 个月发布了 27 个;首次发布于 2026/10/29。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。