codeksei 0.1.0 → 0.1.1

package/README.en.md

@@ -1,56 +1,65 @@
 # Codeksei
 
 [![CI](https://github.com/Sapientropic/codeksei/actions/workflows/ci.yml/badge.svg)](https://github.com/Sapientropic/codeksei/actions/workflows/ci.yml)
+[![npm version](https://img.shields.io/npm/v/codeksei)](https://www.npmjs.com/package/codeksei)
+[![License: AGPL-3.0-only](https://img.shields.io/badge/license-AGPL--3.0--only-111111.svg)](https://github.com/Sapientropic/codeksei/blob/main/LICENSE)
 
 [中文 README](./README.md)
 
-Codeksei is a local-first life-assistant agent bridge.  
-It connects Codex runtime, WeChat messaging, timeline, diary, review, durable notes, and workspace continuity into one operational loop so the agent can keep state, reconnect context, and carry work forward instead of acting like a stateless chat shell.
+> A local-first life-assistant agent bridge that connects WeChat, Codex runtime, timeline, diary, review, durable notes, and workspace continuity into one ongoing personal workflow.
 
-This repository is no longer a lightly modified fork whose original README still applies. The current codebase has been heavily reshaped around shared app-server lifecycle management, WeChat v2 routing and delivery hardening, timeline/diary/review tooling, durable note routing, workspace bootstrap, and project radar. The documentation below describes this repository as it exists today.
+`Codeksei` is not a hosted SaaS, and it is not a stateless personality shell.  
+It is a local operational layer for keeping state, reconnecting context, and moving work forward across WeChat, terminal sessions, and workspace tools.
 
-## What It Is
+> This repository has diverged substantially from the original `cyberboss` README and usage model. Treat this repository’s `README`, `docs/`, and actual code as the current source of truth.
 
-- A personal, locally deployed life-assistant bridge, not a hosted SaaS.
-- A runtime that links WeChat conversations, Codex threads, timeline events, diaries, reviews, and lightweight project memory.
-- A system designed for real continuity and low-friction re-entry, especially when executive function is the bottleneck.
+## At a Glance
 
-## Current Capabilities
+| Item | What it means |
+| --- | --- |
+| Positioning | Local-first personal life-assistant bridge |
+| Main interfaces | WeChat + `codeksei` CLI |
+| Core value | Shared thread, shared state, low-friction re-entry |
+| Current package | `codeksei@0.1.1` |
+| Compatibility layer | `cyberboss` / `CYBERBOSS_*` / `~/.cyberboss` |
 
-- WeChat bridge: QR login, long polling, file send-back, shared thread attach
-- Codex runtime: shared `app-server`, thread/session binding, approvals, stop/resume
-- Timeline: event write, batch write, taxonomy lookup, build/serve/screenshot
-- Diary: Todo, factual timeline, fragments, supplements, summaries
-- Review: nightly / weekly / monthly, with hybrid semantic pass by default
-- Durable notes: `note:auto`, `note:maybe`, `note:sync`
-- Workspace continuity: workspace bootstrap, project radar, shared-thread recovery
+## Why It Is More Than a Chat Shell
 
-## Naming and Compatibility
+- It is designed for continuity, not one-off prompts.
+- WeChat and terminal sessions can attach to the same shared thread.
+- `timeline`, `diary`, `review`, and `note` are built-in workflows, not afterthought scripts.
+- State and tooling stay local, auditable, and modifiable.
 
-`Codeksei` is now the primary public name.
+## Who It Fits
 
-- Primary package name: `codeksei`
-- Primary CLI name: `codeksei`
-- Primary env prefix: `CODEKSEI_*`
-- Primary state directory: `~/.codeksei`
+- People who want WeChat to be the main interaction surface
+- People who need the agent to remember thread state, unfinished work, and review clues
+- People who prefer local control over hosted products
+- People who benefit from low-friction re-entry, especially when executive function is the bottleneck
 
-Compatibility is still preserved for existing local setups:
+## Current Capabilities
 
-- Legacy CLI: `cyberboss`
-- Legacy env prefix: `CYBERBOSS_*`
-- Legacy state directory: `~/.cyberboss`
+| Area | What it currently does |
+| --- | --- |
+| WeChat bridge | QR login, long polling, file send-back, shared-thread attach |
+| Codex runtime | Shared `app-server`, thread/session binding, approvals, stop/resume |
+| Timeline | Event write, batch write, taxonomy lookup, build, preview, screenshot |
+| Diary | Todo, factual timeline, fragments, supplements, summaries |
+| Review | nightly / weekly / monthly, with hybrid semantic extraction by default |
+| Durable notes | `note:auto`, `note:maybe`, `note:sync` |
+| Workspace continuity | workspace bootstrap, project radar, shared-thread recovery by workspace |
 
-Rules:
+## Quick Start
 
-- New-prefixed env vars override legacy-prefixed env vars.
-- If `~/.codeksei` does not exist but `~/.cyberboss` does, the runtime will reuse the legacy state directory.
-- Windows scheduled tasks are installed as `Codeksei Shared *` and remove legacy `Cyberboss Shared *` task names during reinstall.
+### 1. Fastest install path
 
-## Quick Start
+If you just want to install and use it:
 
-### 1. Clone and install
+```bash
+npm install -g codeksei
+```
 
-The default path is still to clone and run locally. The repository now includes GitHub Actions CI and an npm publish workflow, but until the first package release exists, clone-based local usage remains the primary install path:
+If you want source-level customization, debugging, or local script changes:
 
 ```bash
 git clone https://github.com/Sapientropic/codeksei.git
@@ -58,14 +67,19 @@ cd codeksei
 npm install
 ```
 
-### 2. Configure env vars
+### 2. Minimum env setup
 
-Recommended minimum setup:
+Runtime env lookup order:
+
+1. `.env` in the current project directory
+2. `.env` in the current state directory
+
+Recommended minimum variables:
 
 ```dotenv
 CODEKSEI_USER_NAME=YourName
 CODEKSEI_USER_GENDER=female
-CODEKSEI_ALLOWED_USER_IDS=your-wechat-user-id
+CODEKSEI_ALLOWED_USER_IDS=bridge_observed_sender_id
 CODEKSEI_WORKSPACE_ROOT=/absolute/path/to/your/workspace
 ```
 
@@ -76,15 +90,32 @@ CODEKSEI_ACCOUNT_ID=
 CODEKSEI_CODEX_ENDPOINT=ws://127.0.0.1:8765
 CODEKSEI_WEIXIN_ADAPTER=v2
 CODEKSEI_WEIXIN_REPLY_MODE=stream
+CODEKSEI_WEIXIN_ROUTE_TAG=
+CODEKSEI_WEIXIN_PROTOCOL_CLIENT_VERSION=2.1.1
+CODEKSEI_TIMEZONE=Asia/Shanghai
 CODEKSEI_DIARY_DIR=/absolute/path/to/your/vault/diary
 CODEKSEI_TIMELINE_STATE_DIR=/absolute/path/to/your/vault/.codex/timeline
 CODEKSEI_WORKSPACE_BOOTSTRAP_CONFIG=/absolute/path/to/workspace-bootstrap.json
 CODEKSEI_PROJECT_RADAR_CONFIG=/absolute/path/to/.codex/code-projects.json
 CODEKSEI_DURABLE_NOTE_SCHEMA_CONFIG=/absolute/path/to/.codex/durable-note-schema.json
 CODEKSEI_REVIEW_SCHEMA_CONFIG=/absolute/path/to/.codex/review-schema.json
+CODEKSEI_SHARED_USE_BUNDLED_CODEX_BINARY=1
+CODEKSEI_SHARED_DISABLE_PLUGINS=0
+CODEKSEI_SHARED_DISABLE_SHELL_SNAPSHOT=0
 ```
 
-Legacy `CYBERBOSS_*` variables still work, but new setups should move to `CODEKSEI_*`.
+Notes:
+
+- Legacy `CYBERBOSS_*` variables still work, but new setups should use `CODEKSEI_*`
+- `CODEKSEI_USER_NAME` is a display/persona field for chat, not a routing id
+- `CODEKSEI_ALLOWED_USER_IDS` must use the exact sender ids observed by the bridge; the easiest way to find them is `npm run accounts`
+- The first successful run will generate `weixin-instructions.md` in the state directory
+- If you use multiple workspaces in shared mode, set `CODEKSEI_WORKSPACE_ROOT` before starting
+- `CODEKSEI_TIMEZONE` is optional; when set, it becomes the single local-time contract for reminder / diary / review / timeline flows
+- If `CODEKSEI_TIMEZONE` is unset, Codeksei first reuses any non-legacy timezone already declared by the timeline state; otherwise it falls back to the system timezone
+- Legacy `Asia/Shanghai` timeline state can be auto-migrated to the unified timezone the next time you run a timeline command
+- `CODEKSEI_TIMELINE_STATE_DIR` is the timeline-for-agent state root; the current primary layout stores runtime files under `timeline/*.json`
+- Keep `.env` local; do not commit it into the repository
 
 ### 3. Login
 
@@ -100,7 +131,7 @@ Shared mode is the default operational path:
 npm run shared:start
 ```
 
-Attach your current WeChat-bound thread from the terminal:
+Attach the current WeChat-bound shared thread:
 
 ```bash
 npm run shared:open
@@ -126,7 +157,7 @@ npm run background:uninstall
 
 ## Common Commands
 
-Most frequently used local commands:
+Most frequently used terminal commands:
 
 - `npm run login`
 - `npm run accounts`
@@ -134,6 +165,8 @@ Most frequently used local commands:
 - `npm run shared:open`
 - `npm run shared:status`
 - `npm run shared:watchdog`
+- `npm run background:install`
+- `npm run background:uninstall`
 - `npm run doctor`
 - `npm run help`
 
@@ -156,15 +189,30 @@ More detailed references:
 
 - [docs/commands.md](./docs/commands.md)
 - [docs/architecture.md](./docs/architecture.md)
+- [docs/release.md](./docs/release.md)
 
-## Release and CI
+## Naming and Compatibility
 
-The repository now includes GitHub Actions CI and an npm publish workflow.  
-The canonical release instructions, required secrets, tag rules, and slug-migration constraints live in:
+`Codeksei` is now the primary public name.
 
-- [docs/release.md](./docs/release.md)
+- Primary package name: `codeksei`
+- Primary CLI name: `codeksei`
+- Primary env prefix: `CODEKSEI_*`
+- Primary state directory: `~/.codeksei`
 
-## Local State
+Compatibility is still preserved for existing local setups:
+
+- Legacy CLI: `cyberboss`
+- Legacy env prefix: `CYBERBOSS_*`
+- Legacy state directory: `~/.cyberboss`
+
+Rules:
+
+- New-prefixed env vars override legacy-prefixed env vars
+- If `~/.codeksei` does not exist but `~/.cyberboss` does, the runtime reuses the legacy state directory
+- Windows scheduled tasks are installed as `Codeksei Shared *` and remove legacy `Cyberboss Shared *` task names during reinstall
+
+## Local State and Public Boundary
 
 Primary state directory:
 
@@ -178,7 +226,7 @@ Legacy-compatible state directory:
 ~/.cyberboss
 ```
 
-Typical contents:
+Typical runtime contents:
 
 - `accounts/`
 - `sessions.json`
@@ -192,6 +240,10 @@ Typical contents:
 - `timeline/`
 - `logs/`
 
+If you set `CODEKSEI_DIARY_DIR` or `CODEKSEI_TIMELINE_STATE_DIR`, business data is stored there and the state directory keeps runtime files only.
+
+The repository and npm package are meant to contain code, scripts, templates, and docs only. Your accounts, sessions, logs, personal `.env`, and local business data should stay outside version control.
+
 ## Timeline Can Be Used Separately
 
 Codeksei builds its timeline layer on top of [`timeline-for-agent`](https://github.com/WenXiaoWendy/timeline-for-agent).  
@@ -204,10 +256,20 @@ Codeksei grew from that base, but this version has been substantially reworked.
 
 ## FAQ
 
-### Why not `npm install codeksei` directly?
+### Why not just `npm install -g codeksei`?
+
+You can. `codeksei@0.1.1` is already on npm.  
+Use npm if you only want to install it; clone the repository when you want customization, debugging, or source-level changes.
+
+### Should I use `codeksei` or `cyberboss`?
+
+New setups and current docs should use `Codeksei / codeksei / CODEKSEI_*`.  
+The old naming still exists only as a compatibility layer for existing local state and scripts.
+
+### How is shared mode different from `npm run start`?
 
-Because the primary install path is still local clone + run.  
-CI and npm trusted publishing automation are now in place, but the first public release still requires a one-time trusted publisher setup on npm plus the release/tag flow.
+`npm run start` / `npm run start:checkin` is better for minimal-path debugging.  
+Shared mode is the default for daily use, WeChat + terminal continuity, recovery, and multi-window attach.
 
 ## License
 

package/README.md

@@ -1,70 +1,65 @@
 # Codeksei
 
 [![CI](https://github.com/Sapientropic/codeksei/actions/workflows/ci.yml/badge.svg)](https://github.com/Sapientropic/codeksei/actions/workflows/ci.yml)
+[![npm version](https://img.shields.io/npm/v/codeksei)](https://www.npmjs.com/package/codeksei)
+[![License: AGPL-3.0-only](https://img.shields.io/badge/license-AGPL--3.0--only-111111.svg)](https://github.com/Sapientropic/codeksei/blob/main/LICENSE)
 
 [English README](./README.en.md)
 
-Codeksei 是一个面向个人本地部署的生活助理 Agent Bridge。  
-它把 Codex runtime、微信桥接、timeline、diary、review、durable note 这些能力接到同一条工作流里，让一个长期在线的 agent 不只是“回答问题”，而是能在真实生活与项目上下文里持续接线、记账、回看和推进。
+> 一个本地优先的生活助理 Agent Bridge，把 WeChat、Codex runtime、timeline、diary、review、durable note 和 workspace continuity 接到同一条可持续运行的个人工作流里。
 
-这个仓库已经不是对原仓 README 原样适用的轻量 fork。现在的实现包含共享 app-server 生命周期、WeChat v2 路由与回复去重、timeline/diary/review 命令链路、durable note 自动路由、workspace bootstrap、project radar 等大量改造，因此文档以当前仓库现状为准。
+`Codeksei` 不是云端 SaaS，也不是只靠提示词扮演人格的聊天外壳。  
+它更像一个本地运行的协作底座：让 agent 能持续记住线程、接住上下文、把事情往前推，并在你掉线之后还能低摩擦重新接上。
 
-## 这是什么
+> 这个仓库已经显著偏离上游 `cyberboss` 的原始 README 和使用方式。当前行为请以本仓 `README`、`docs/` 和实际代码实现为准。
 
-- 一个本地优先的个人生活助理桥接层，不是云端 SaaS。
-- 一个把微信消息、Codex 线程、时间轴、日记、复盘和轻量项目索引接起来的运行时。
-- 一个更适合“需要外部脚手架、需要被重新接住、需要低摩擦收口”的个人协作系统。
+## 一眼看懂
 
-它不是：
+| 项目 | 说明 |
+| --- | --- |
+| 定位 | 本地优先的个人生活助理桥接层 |
+| 主要入口 | WeChat + `codeksei` CLI |
+| 核心价值 | 同一条线程、同一份状态、低摩擦续接 |
+| 当前发布 | `codeksei@0.1.1` |
+| 兼容层 | `cyberboss` / `CYBERBOSS_*` / `~/.cyberboss` |
 
-- 通用聊天机器人托管平台
-- 多租户服务端产品
-- 只靠提示词演戏、没有状态与工具落盘的“人格壳”
+## 为什么它不是普通聊天壳
+
+- 持续运行，而不是每次对话都从零开始。
+- 微信和终端可以接到同一条共享线程，而不是两个互不相认的入口。
+- `timeline`、`diary`、`review`、`note` 是内建工作流，不是后贴的边缘脚本。
+- 数据与脚本本地可控、可改、可审计，更适合长期陪跑而不是一次性问答。
 
 ## 适合谁
 
-- 希望把微信当成主要交互入口，而不是再开一个新 App 的人
+- 希望把微信当成主要交互入口，而不是再开一个单独助手 App 的人
 - 需要 agent 帮自己记住线程状态、时间线、未收口事项和复盘线索的人
 - 更在意本地数据可控、可改、可审计，而不是云端托管的人
-- 有 ADHD / 执行功能摩擦，想把“重新接上”做成默认能力的人
+- 有 ADHD 或执行功能摩擦，想把“重新接上”做成默认能力的人
 
 ## 当前能力
 
-- 微信桥接：扫码登录、长轮询收发、文件发送、共享线程接管
-- Codex runtime：共享 `app-server`、thread/session 绑定、审批流、stop / resume
-- 时间轴：单条事件写入、批量写入、分类查询、构建/预览/截图
-- 日记：Todo、时间线事实、碎片、补充记录、总结
-- Review：nightly / weekly / monthly，默认 hybrid 语义提炼
-- Durable note：`note:auto` / `note:maybe` / `note:sync`
-- Workspace continuity：workspace bootstrap、project radar、共享线程按 workspace 恢复
-
-## 命名与兼容
-
-这轮开始，公共品牌以 `Codeksei` 为主。
-
-- 主名称：`Codeksei`
-- 主包名：`codeksei`
-- 主 CLI 名：`codeksei`
-- 主环境变量前缀：`CODEKSEI_*`
-- 主状态目录：`~/.codeksei`
-
-为了不打断已有本地使用，当前仍保留兼容层：
-
-- 旧 CLI：`cyberboss`
-- 旧环境变量前缀：`CYBERBOSS_*`
-- 旧状态目录：`~/.cyberboss`
+| 模块 | 当前能力 |
+| --- | --- |
+| WeChat bridge | 扫码登录、长轮询收发、文件发送、共享线程接管 |
+| Codex runtime | 共享 `app-server`、thread/session 绑定、审批流、stop/resume |
+| Timeline | 单条事件写入、批量写入、分类查询、构建、预览、截图 |
+| Diary | Todo、时间线事实、碎片、补充记录、总结 |
+| Review | nightly / weekly / monthly，默认 hybrid 语义提炼 |
+| Durable note | `note:auto`、`note:maybe`、`note:sync` |
+| Workspace continuity | workspace bootstrap、project radar、按 workspace 恢复共享线程 |
 
-兼容规则：
+## 快速开始
 
-- 新前缀优先于旧前缀
-- 如果 `~/.codeksei` 不存在但 `~/.cyberboss` 已存在，运行时会优先复用旧状态
-- Windows 后台任务会安装为 `Codeksei Shared *`，同时清理旧 `Cyberboss Shared *`
+### 1. 最短安装路径
 
-## 快速开始
+如果你只是要安装和使用：
 
-### 1. 获取源码
+```bash
+npm install -g codeksei
+```
 
-当前默认仍推荐直接拉源码使用。仓库已经补上 GitHub Actions CI 和 npm publish workflow，但在首发 npm 包之前，日常安装入口仍以 clone 仓库为主：
+如果你要改源码、调试共享脚本或做本地定制：
 
 ```bash
 git clone https://github.com/Sapientropic/codeksei.git
@@ -72,7 +67,7 @@ cd codeksei
 npm install
 ```
 
-### 2. 先配环境变量
+### 2. 最小环境变量
 
 运行时默认读取：
 
@@ -84,7 +79,7 @@ npm install
 ```dotenv
 CODEKSEI_USER_NAME=你的名字
 CODEKSEI_USER_GENDER=female
-CODEKSEI_ALLOWED_USER_IDS=你的微信 user id
+CODEKSEI_ALLOWED_USER_IDS=桥实际观测到的 sender id
 CODEKSEI_WORKSPACE_ROOT=/绝对路径/你的项目目录
 ```
 
@@ -97,6 +92,7 @@ CODEKSEI_WEIXIN_ADAPTER=v2
 CODEKSEI_WEIXIN_REPLY_MODE=stream
 CODEKSEI_WEIXIN_ROUTE_TAG=
 CODEKSEI_WEIXIN_PROTOCOL_CLIENT_VERSION=2.1.1
+CODEKSEI_TIMEZONE=Asia/Shanghai
 CODEKSEI_DIARY_DIR=/绝对路径/你的 vault/日记
 CODEKSEI_TIMELINE_STATE_DIR=/绝对路径/你的 vault/.codex/timeline
 CODEKSEI_WORKSPACE_BOOTSTRAP_CONFIG=/绝对路径/你的 workspace-bootstrap.json
@@ -111,8 +107,15 @@ CODEKSEI_SHARED_DISABLE_SHELL_SNAPSHOT=0
 说明：
 
 - 旧的 `CYBERBOSS_*` 仍可用，但新项目建议统一切到 `CODEKSEI_*`
+- `CODEKSEI_USER_NAME` 是 agent 聊天时怎么称呼你的人设字段，不参与消息路由
+- `CODEKSEI_ALLOWED_USER_IDS` 必须填写微信桥实际观测到的 sender id；最简单的做法是先跑 `npm run accounts`
 - 第一次运行任意命令时，会在状态目录生成 `weixin-instructions.md`
 - 如果你在共享模式下使用多 workspace，建议启动前就设置好 `CODEKSEI_WORKSPACE_ROOT`
+- `CODEKSEI_TIMEZONE` 可选；若显式设置，它会统一驱动 reminder / diary / review / timeline 的本地时间解释
+- 如果不设 `CODEKSEI_TIMEZONE`，Codeksei 会优先沿用 timeline state 里已声明的非 legacy timezone；否则回退到系统时区
+- 旧的 `Asia/Shanghai` legacy timeline state 在需要时会在下一次 timeline 命令时自动迁移到当前统一 timezone
+- `CODEKSEI_TIMELINE_STATE_DIR` 默认是 timeline-for-agent 的 state root；当前主布局会在它下面使用 `timeline/*.json`
+- `.env` 只应放在你的本地工作目录或状态目录里，不要提交进仓库
 
 ### 3. 扫码登录
 
@@ -142,7 +145,7 @@ npm run shared:status
 
 ### 5. Windows 后台常驻
 
-如果你希望登录后自动拉起，并在解锁/恢复睡眠后快速自愈：
+如果你希望登录后自动拉起，并在解锁或恢复睡眠后快速自愈：
 
 ```powershell
 npm run background:install
@@ -156,7 +159,7 @@ npm run background:uninstall
 
 ## 常用命令
 
-普通用户最常用的是这些：
+终端里最常用的是这些：
 
 - `npm run login`
 - `npm run accounts`
@@ -169,7 +172,7 @@ npm run background:uninstall
 - `npm run doctor`
 - `npm run help`
 
-微信里常用的是这些：
+微信里最常用的是这些：
 
 - `/bind /绝对路径`
 - `/status`
@@ -184,19 +187,35 @@ npm run background:uninstall
 - `/model <id>`
 - `/help`
 
-更完整的命令说明见：
+更完整的命令与架构说明见：
 
 - [docs/commands.md](./docs/commands.md)
 - [docs/architecture.md](./docs/architecture.md)
+- [docs/release.md](./docs/release.md)
 
-## 发布与 CI
+## 命名与兼容
 
-仓库现在已经内置 GitHub Actions CI 与 npm 发布 workflow。  
-发布流程、所需 secret、tag 约定和 slug 迁移约束统一见：
+这轮开始，公共品牌以 `Codeksei` 为主。
 
-- [docs/release.md](./docs/release.md)
+- 主名称：`Codeksei`
+- 主包名：`codeksei`
+- 主 CLI 名：`codeksei`
+- 主环境变量前缀：`CODEKSEI_*`
+- 主状态目录：`~/.codeksei`
 
-## 本地数据在哪里
+为了不打断已有本地使用，当前仍保留兼容层：
+
+- 旧 CLI：`cyberboss`
+- 旧环境变量前缀：`CYBERBOSS_*`
+- 旧状态目录：`~/.cyberboss`
+
+兼容规则：
+
+- 新前缀优先于旧前缀
+- 如果 `~/.codeksei` 不存在但 `~/.cyberboss` 已存在，运行时会优先复用旧状态
+- Windows 后台任务会安装为 `Codeksei Shared *`，同时清理旧 `Cyberboss Shared *`
+
+## 本地数据与公开边界
 
 当前默认状态目录是：
 
@@ -210,7 +229,7 @@ npm run background:uninstall
 ~/.cyberboss
 ```
 
-常见内容包括：
+常见运行态内容包括：
 
 - `accounts/`
 - `sessions.json`
@@ -226,6 +245,8 @@ npm run background:uninstall
 
 如果你单独设置了 `CODEKSEI_DIARY_DIR` 或 `CODEKSEI_TIMELINE_STATE_DIR`，真正的数据会写到你指定的位置，状态目录只保留运行态文件。
 
+这个仓库和 npm 包默认只放代码、脚本、模板与文档，不应包含你的账号、会话、日志、个人 `.env` 或本地业务数据。
+
 ## Timeline 可单独复用
 
 Codeksei 的时间轴能力建立在 [`timeline-for-agent`](https://github.com/WenXiaoWendy/timeline-for-agent) 之上。  
@@ -238,10 +259,10 @@ Codeksei 是在其基础上发展出来的版本，但当前已经进行了大
 
 ## FAQ
 
-### 为什么不是直接 `npm install codeksei`？
+### 为什么不是直接 `npm install -g codeksei`？
 
-因为当前默认入口仍是 clone 仓库后本地运行。  
-现在已经有 GitHub Actions CI 和 npm trusted publishing workflow，但真正首发前仍需要先在 npm 后台完成一次 trusted publisher 配置，再走 release/tag 流程。
+现在已经可以直接 `npm install -g codeksei`。  
+如果你只想安装使用，npm 就是最短路径；如果你要做本地定制、调试共享桥接脚本或直接改仓库源码，clone 仓库仍然更合适。
 
 ### 现在到底该用 `codeksei` 还是 `cyberboss`？
 

package/bin/cyberboss.js

@@ -8,4 +8,4 @@ main().catch((error) => {
   console.error(`[${LEGACY_PACKAGE_NAME}] ${message}`);
   process.exitCode = 1;
 });
-
+