nolo-cli 0.1.43 → 0.1.45

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Bin Zhang
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,290 +1,145 @@
-# @nolo/cli
+# nolo-cli
 
-Agent-first terminal client for Nolo.
+Local-first agent automation for open-source maintainers.
 
-`nolo` should be understood as the terminal workspace for Nolo agents. The
-existing command mode still wraps repo scripts, but the product direction is a
-TUI-first experience similar to Claude Code / Codex CLI:
+[![npm version](https://img.shields.io/npm/v/nolo-cli.svg)](https://www.npmjs.com/package/nolo-cli)
+[![npm downloads](https://img.shields.io/npm/dm/nolo-cli.svg)](https://www.npmjs.com/package/nolo-cli)
+[![test](https://github.com/nolotus/nolo-cli/actions/workflows/test.yml/badge.svg)](https://github.com/nolotus/nolo-cli/actions/workflows/test.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE)
 
-- open `nolo` and work inside a persistent Agent session;
-- chat with an Agent;
-- inspect and manage that Agent's dialogs, docs, tables, skills, and spaces;
-- run internal ops/doctor agents with the same mental model;
-- use non-interactive commands and `--json` for automation.
+`nolo-cli` is a Bun-powered command-line and TUI client for running local and
+remote AI agents around real repository maintenance. It focuses on practical
+open-source maintainer workflows: Codex-assisted review, issue triage, release
+smoke checks, docs updates, runtime diagnostics, and automation-friendly JSON
+commands.
 
-The current MVP uses a dependency-free readline workspace. It is intentionally
-small: status line, text input, lightweight slash commands, and script-backed
-Agent chat. A richer Ink UI can replace the rendering layer later without
-changing the session model.
+The project is moving toward a no-login, bring-your-own-key local mode:
 
-Inside `nolo`, normal text continues the current dialog after the first agent
-reply. Use `/new` when you want a clean dialog. Response token details stay
-hidden by default; set `NOLO_SHOW_USAGE=1` when debugging usage.
+- `nolo run "review this repository"` runs a local Codex-style agent in the
+  current repository without requiring a Nolo account.
+- Authenticated Nolo workflows remain available for synced agents, dialogs,
+  docs, tables, and machine-bound automation.
+- The desktop direction is local-first by default: users should be able to run
+  with their own OpenAI, Anthropic, OpenRouter, Codex CLI, Qoder, or other
+  provider credentials without depending on hosted Nolo infrastructure.
 
-Nolo is intentionally not trying to copy coding-only CLIs one-for-one. Claude
-Code, Codex CLI, and Copilot CLI are strongest when a developer is already
-inside a codebase. Nolo's CLI should sit between ordinary users and developers:
-one assistant by default, with specialist agents, docs, tables, dialogs, and
-synced workspace data one slash command away.
-
-## Usage
+The npm package is published as `nolo-cli`:
 
 ```bash
 npm install -g nolo-cli
 nolo
-
-# see which install you are running
 nolo doctor
 nolo --version
-
-# no Nolo login required: runs the local Codex CLI in the current directory
 nolo run "review this repository"
-
-# update later from your shell
-nolo update
-```
-
-Inside the TUI, run:
-
-```text
-/update
-```
-
-The npm package expects Bun to be available because the executable is a Bun
-TypeScript script.
-
-For local maintainer workflows, `nolo run "..."` does not require a Nolo
-account. It resolves to the built-in `local-codex` agent, runs in the current
-working directory, and uses the local Codex CLI installation. This is intended
-for repository-local review, triage, and release-check tasks.
-
-Remote Nolo records and synced workflows still require a token:
-
-```bash
-NOLO_SERVER=https://nolo.chat AUTH_TOKEN=<token> nolo
-```
-
-Or save a local profile once:
-
-```bash
-nolo login --server https://nolo.chat
-nolo whoami
-nolo
 ```
 
-By default, `nolo login` opens the Nolo website and waits for browser
-authorization. In SSH or browserless environments, use:
+## Why This Matters
 
-```bash
-nolo login --no-browser
-```
+Open-source maintainers are increasingly using coding agents for issue triage,
+pull-request review, release checks, documentation, and repository maintenance.
+Those workflows need more than a single chat box: they need repeatable command
+entry points, local runtime checks, scoped shell permissions, structured
+task/dialog history, release smoke checks, and automation-friendly output.
 
-Then open the printed URL on a logged-in browser. Automation can still save a
-token directly:
+`nolo-cli` is aimed at that layer. It is designed to make agent-maintainer
+workflows inspectable and scriptable, while keeping local runtime boundaries
+clear.
 
-```bash
-nolo login --server https://nolo.chat --token <token>
-```
+## Maintainer Workflows
 
-Local repo development should use `nolo login` or an explicit `AUTH_TOKEN` for
-agent runs.
+The project is built around ongoing maintainer duties that can be reviewed,
+tested, and improved in public:
 
-Inside the TUI, `/update` is the shortcut for the same global `nolo update`
-command.
+- **Pull request review:** run local Codex or another CLI agent against a diff,
+  ask for risk-focused review, and keep the review prompt reproducible.
+- **Issue triage:** classify bug reports, installation failures, runtime
+  provider issues, and docs gaps into actionable labels.
+- **Release management:** run doctor checks, smoke checks, changelog review,
+  and package verification before publishing.
+- **Security review:** keep shell, machine connector, BYOK provider, and token
+  boundaries explicit so contributors can reason about local access.
 
-```bash
-nolo --help
-nolo doctor
-nolo update
-nolo
-nolo run "review this repository"
-nolo chat "triage the failing tests"
-nolo chat
-nolo connect
-nolo connect --watch
-nolo connect --daemon
-nolo daemon --server-url https://api.nolo.chat --machine-key sk_machine_xxx
-nolo machine status
-nolo run "summarize my latest agent dialogs"
-nolo doc create --title "Trip Notes" --body "hello" --sync local,us --dry-run
-nolo doc create --title "Proxy Notes" --description "Windows setup" --body-file ./proxy.md --sync local,main,us --allow-secrets
-nolo skill-doc create --title "Agent Query Skill" --description "Inspect recent agent dialogs" --body-file ./skill.md --sync local,main,us
-nolo space read 01KKY77TT0DA9NY7TNW3R7255N --content-key page-user-id --brief
-nolo agent list --json
-nolo agent bind-current agent-user-1-agent-1
-nolo agent runtime-doctor agent-user-1-agent-1
-nolo agent smoke-current agent-user-1-agent-1 --msg "ping"
-nolo chat --agent agent-pub-01APPBUILDER00000001YAII3I --msg "你好"
-```
-
-For document creation, prefer the CLI over direct scripts. Use `nolo doc create`
-for ordinary pages and `nolo skill-doc create` for skill-backed pages. Both
-support `--sync`, `--dry-run`, `--json`, and `--allow-secrets`, and both write
-for the current auth token user rather than a demo bootstrap user.
-
-Experimental machine connector commands:
-
-```bash
-nolo connect          # send one machine heartbeat
-nolo connect --watch  # keep this terminal process online with periodic heartbeats
-nolo connect --ws     # keep a live connector websocket for bound agent runs
-nolo connect --daemon # start connect --ws silently in the background
-nolo daemon --server-url https://api.nolo.chat --machine-key sk_machine_xxx
-nolo machine status   # list machines registered to the current profile
-```
+See [MAINTAINER_WORKFLOWS.md](./MAINTAINER_WORKFLOWS.md) for concrete command
+patterns and [OPEN_SOURCE_BOUNDARY.md](./OPEN_SOURCE_BOUNDARY.md) for what is
+being opened versus intentionally kept private.
 
-These commands only register machine presence and runtime capabilities today.
-They do not expose shell, file-write, or raw local LLM endpoints.
+## Public Source
 
-Run a Slock-style connector command:
+The first reusable source modules are now mirrored in this repository:
 
-```bash
-nolo daemon --server-url https://api.nolo.chat --machine-key sk_machine_xxx
-```
+- [`src/localRun.ts`](./src/localRun.ts) documents and tests the no-login local
+  run contract for `nolo run` and `nolo chat`.
+- [`src/providerConfig.ts`](./src/providerConfig.ts) documents the BYOK
+  provider credential boundary: public config stores environment variable
+  references, not raw API keys.
+- [`src/runtimeBoundary.ts`](./src/runtimeBoundary.ts) documents the local
+  runtime boundary for no-login CLI and desktop flows: local provider
+  credentials, workspace-scoped shell policy, local persistence, and no remote
+  sync by default.
+- [`src/localRun.test.ts`](./src/localRun.test.ts) verifies that shorthand runs
+  use local Codex without requiring Nolo auth, while explicit agent runs remain
+  distinct.
 
-Future published package shape:
+Run the public tests with:
 
 ```bash
-npx @nolo/daemon@latest --server-url https://api.nolo.chat --machine-key sk_machine_xxx
-```
-
-The daemon registers this computer, reports local CLI capabilities, keeps a live
-websocket open, and executes bound CLI agents on this computer. Agents bind to a
-machine, not to a workspace or project folder.
-
-Bind an agent to the current machine:
-
-```bash
-nolo agent bind-current <agentKey>
-```
-
-The agent keeps its own CLI settings. The binding only records which connected
-machine must be online when that agent runs.
-
-Run a one-command connector smoke test:
-
-```bash
-nolo agent runtime-doctor <agentKey>
-nolo agent smoke-current <agentKey> --msg "ping"
-```
-
-`runtime-doctor` checks whether the agent is a CLI agent and whether the current
-machine has the required CLI capability. `smoke-current` heartbeats the current
-machine, binds the agent to it, opens a temporary connector websocket, calls
-`/api/agent/run`, and prints the returned dialog id/content.
-
-## Product Shape
-
-The preferred command model is Agent-first:
-
-```bash
-nolo agent list
-nolo agent switch <agent>
-nolo agent read <agent>
-nolo agent update <agent> --model gpt-5.4 --cli-provider codex --api-source cli
-nolo agent run <agent> "检查最近失败任务"
-nolo agent run frontend-implementer --msg "修一个小的通知弹窗 CSS 问题"
-nolo agent list --space <space>
-nolo dialog list
-nolo dialog list --space <space>
-nolo dialog read <dialog>
-nolo dialog delete <dialog...> --yes
-nolo doc list --agent <agent>
-nolo table query --table meta-0e95801d90-NOLOTASKBOARD --limit 20
-nolo table query --table meta-0e95801d90-NOLOTASKBOARD --columns '["title","status","owner","priority","codeStatus"]' --no-base-fields --output items
-nolo table update-row --table meta-0e95801d90-NOLOTASKBOARD --row 01ROWID --changes '{"status":"已完成"}'
-nolo table add-column --table meta-0e95801d90-NOLOTASKBOARD --schema-write-ok --name "blockedBy" --label "Blocked By"
-```
-
-`agent list`, `dialog list`, and record delete commands use global server
-candidates for the current CLI profile: the selected `--server` / `NOLO_SERVER`
-plus known Nolo cluster peers. List commands merge tombstones so a newer delete
-on one server hides older live records from another. Dialog, doc, skill-doc,
-space, and agent public-record deletes send the delete to all target servers;
-each server applies the normal tombstone/cascade behavior for that record type.
-
-`nolo table add-column` mutates table schema metadata, so it requires
-`--schema-write-ok` and should be run serially per table. Row-level table writes
-do not require this flag.
-
-For agent config inspection and small config mutations, prefer the CLI-native
-commands instead of ad hoc scripts:
-
-- `nolo agent list` is CLI-native and prefers the local cache, then degrades to
-  remote query when the local LevelDB cache is unavailable or locked.
-- `nolo agent read <agent>` reads local cached agent records first, then falls
-  back to remote fetch + local cache refresh across known server candidates.
-- if the local LevelDB cache is unavailable or locked, `nolo agent read`
-  degrades to remote-only lookup instead of hard-failing on the local DB.
-- `nolo agent update <agent> ...` is CLI-native and supports small targeted
-  updates such as `--model`, `--cli-provider`, `--api-source`, and repeated
-  `--field key=value`.
-
-Account ownership matters for private agent maintenance. Default new tests,
-validation dialogs, task-board writes, machine-bound agent runs, and
-user-visible results should write to the current operator account
-`0e95801d90`. The legacy
-`b2e06f801f` / platform-demo account still owns older public/shared records, but
-it is being retired as the default write target. Use `nolo agent read`,
-`nolo agent update`, and repo-native helpers as the normal entrypoints; only
-owner-only operations that explicitly target legacy records should use the
-maintained platform-demo token from `scripts/testUtils.ts` or a regenerated
-token from `scripts/generateToken.ts`. Do not copy token strings into docs,
-logs, or prompts.
-
-Inside the current TUI, examples of supported slash commands include:
-`/agent`, `/agents`, `/switch`, `/context` (alias `/ctx`), `/dialog`, `/doc`,
-`/help`, `/new`, `/customize`, `/login`, `/profile`, `/version`, `/quit`
-(alias `/exit`), and `/update` (which maps to `nolo update`).
-
-Future product-direction examples for the broader TUI command model:
-
-```text
-/agent list
-/agent switch ops
-/dialog open latest
-/doc list
-/table query builtin-dialog-probe-runs
-```
-
-See [`docs/nolo-cli-tui.md`](../../docs/nolo-cli-tui.md) for the product and
-technical direction.
-
-## Building for Publish
-
-The CLI is developed in a monorepo with workspace dependencies (`ai` and
-`connector-experimental`). To generate a publish-safe package that can be
-installed via npm outside the monorepo:
-
-```bash
-bun run build:publish
-```
-
-This creates a `dist/` directory with:
-- All source files from the `files` array in package.json
-- Inlined workspace dependencies (copied as nested directories)
-- A modified package.json with workspace dependencies stripped
-
-The `dist/` directory is the publish-safe artifact consumed by the CI npm
-publish workflow:
-
-```bash
-bun ./scripts/release/prepareCliPublishPackage.ts --out-dir .tmp/nolo-cli-publish
-cd .tmp/nolo-cli-publish
-npm pack
-```
-
-For this repository, the default release path for `nolo-cli` is the GitHub
-Actions workflow [`.github/workflows/cli-npm-publish.yml`](../../.github/workflows/cli-npm-publish.yml).
-Use local `npm pack` or tarball-based `npm install -g` as preflight verification.
-Do not treat manual local `npm publish` as the normal release route unless you
-are intentionally debugging the CI publish lane.
-
-Key differences between repo-local and published versions:
-- **Repo-local**: Runs from source (`packages/cli/index.ts`) with workspace
-  dependencies resolved by the monorepo
-- **Published**: Runs from dist (`dist/index.ts`) with workspace dependencies
-  inlined as nested directories
-
-Both versions use the same Bun runtime and TypeScript source files. The build
-process does not transpile; it only restructures the package for standalone use.
+bun test src
+```
+
+Current public source status:
+
+| Area | Public evidence |
+| --- | --- |
+| No-login local run | `src/localRun.ts`, `src/localRun.test.ts`, passing GitHub Actions |
+| BYOK provider boundary | `src/providerConfig.ts`, `src/providerConfig.test.ts`, PR #8 |
+| Local runtime boundary | `src/runtimeBoundary.ts`, `src/runtimeBoundary.test.ts`, PR #8 |
+| Release management | `RELEASE_CHECKLIST.md`, issue #9 |
+| Source mirror safety | `OPEN_SOURCE_BOUNDARY.md`, `SOURCE_MIRROR_CHECKLIST.md`, issues #1 and #5 |
+
+## Project Status
+
+This repository is the public OSS entry point for the CLI project. The package
+is actively maintained and has frequent releases on npm. As of June 2026,
+`nolo-cli` source is prepared for version `0.1.45`; npm reports about 3.5k
+downloads for the last-month window ending 2026-06-02. Version `0.1.44` was
+published from the public `nolotus/nolo-cli` GitHub Actions npm workflow, and
+`0.1.45` should be published from the same public workflow after review.
+
+The current implementation is developed in a broader private monorepo because
+it shares product infrastructure with Nolo. Public source mirroring is being
+managed in a staged way so that reusable CLI, local runtime, provider adapter,
+desktop local-mode, docs, tests, and maintainer workflow code can be opened
+without exposing private product records, credentials, production operations,
+billing systems, or user-data paths.
+
+See [OPEN_SOURCE_STATUS.md](./OPEN_SOURCE_STATUS.md) and
+[ROADMAP.md](./ROADMAP.md) for the public-source migration plan.
+
+## Maintenance Scope
+
+The public maintenance scope for this project is:
+
+- Agent-first terminal and TUI workflows for OSS maintainers.
+- No-login local agent runs in the current repository.
+- BYOK provider configuration for CLI and desktop local mode.
+- Local-first agent runtime boundaries and scoped shell permissions.
+- Runtime doctor, release smoke-check, and package verification workflows.
+- Optional authenticated commands for synced Nolo agents, dialogs, docs, tables,
+  and machine connectors.
+
+## Links
+
+- npm package: https://www.npmjs.com/package/nolo-cli
+- Nolo: https://nolo.chat
+- Maintainer workflows: [MAINTAINER_WORKFLOWS.md](./MAINTAINER_WORKFLOWS.md)
+- Open-source boundary: [OPEN_SOURCE_BOUNDARY.md](./OPEN_SOURCE_BOUNDARY.md)
+- Open-source status: [OPEN_SOURCE_STATUS.md](./OPEN_SOURCE_STATUS.md)
+- Roadmap: [ROADMAP.md](./ROADMAP.md)
+- BYOK provider setup: [docs/provider-setup.md](./docs/provider-setup.md)
+- Desktop local mode: [docs/desktop-local-mode.md](./docs/desktop-local-mode.md)
+- Release checklist: [RELEASE_CHECKLIST.md](./RELEASE_CHECKLIST.md)
+- Source mirror checklist: [SOURCE_MIRROR_CHECKLIST.md](./SOURCE_MIRROR_CHECKLIST.md)
+
+## License
+
+MIT

package/agentAliases.ts

@@ -1,95 +1,25 @@
-export const CURRENT_OPERATOR_USER_ID = "0e95801d90";
 export const NOLO_DEFAULT_AGENT_ID = "01NOLOAPPBLD000000019KCKT0";
 export const NOLO_DEFAULT_AGENT_KEY = `agent-pub-${NOLO_DEFAULT_AGENT_ID}`;
-export const NOLO_PROJECT_MANAGER_AGENT_ID = "01NOLOPROJMGR00000000MSVGG";
-export const NOLO_PROJECT_MANAGER_AGENT_KEY =
-  `agent-${CURRENT_OPERATOR_USER_ID}-${NOLO_PROJECT_MANAGER_AGENT_ID}`;
-export const NOLO_FRONTEND_AGENT_ID = "01FRONTENDAG0000000115N4E1";
-export const NOLO_FRONTEND_AGENT_KEY =
-  `agent-${CURRENT_OPERATOR_USER_ID}-${NOLO_FRONTEND_AGENT_ID}`;
-export const WIN_CODEX_AGENT_ID = "WINCODEX00000000FQ0LK0";
-export const WIN_CODEX_AGENT_KEY =
-  `agent-0e95801d90-${WIN_CODEX_AGENT_ID}`;
-export const WIN_QWEN_AGENT_ID = "01CUSTOMCODEA00000001JEAG3";
-export const WIN_QWEN_AGENT_KEY =
-  `agent-0e95801d90-${WIN_QWEN_AGENT_ID}`;
-export const MIMO_MONTH_AGENT_ID = "01MIMO25MONTH0000000NEW001";
-export const MIMO_MONTH_AGENT_KEY =
-  `agent-0e95801d90-${MIMO_MONTH_AGENT_ID}`;
-export const QODER_AGENT_ID = "01QODERCLIAGENT00000000NEW";
-export const QODER_AGENT_KEY =
-  `agent-0e95801d90-${QODER_AGENT_ID}`;
 export const LOCAL_CODEX_AGENT_ID = "01LOCALCODEXCLI000000NEW";
 export const LOCAL_CODEX_AGENT_KEY =
-  `agent-${CURRENT_OPERATOR_USER_ID}-${LOCAL_CODEX_AGENT_ID}`;
+  `agent-local-${LOCAL_CODEX_AGENT_ID}`;
 export const LOCAL_QODER_AGENT_ID = "01LOCALQODERCLI000000NEW";
 export const LOCAL_QODER_AGENT_KEY =
-  `agent-${CURRENT_OPERATOR_USER_ID}-${LOCAL_QODER_AGENT_ID}`;
+  `agent-local-${LOCAL_QODER_AGENT_ID}`;
 
 const AGENT_ALIAS_TO_KEY: Record<string, string> = {
   nolo: NOLO_DEFAULT_AGENT_KEY,
   default: NOLO_DEFAULT_AGENT_KEY,
   "default-nolo": NOLO_DEFAULT_AGENT_KEY,
 
-  // Win Codex (高智力终审与架构把关)
-  "win-codex": WIN_CODEX_AGENT_KEY,
-  "wincodex": WIN_CODEX_AGENT_KEY,
-  "win codex": WIN_CODEX_AGENT_KEY,
-  "nolo-reviewer": WIN_CODEX_AGENT_KEY,
-  reviewer: WIN_CODEX_AGENT_KEY,
-  "nolo-code-review": WIN_CODEX_AGENT_KEY,
-  "code-review": WIN_CODEX_AGENT_KEY,
-  review: WIN_CODEX_AGENT_KEY,
-  "代码审查": WIN_CODEX_AGENT_KEY,
-  "nolo 代码审查": WIN_CODEX_AGENT_KEY,
-
-  // 包月 Mimo (全栈业务代码与常规杂活物理实体)
-  "包月mimo": MIMO_MONTH_AGENT_KEY,
-  "包月mimo2.5": MIMO_MONTH_AGENT_KEY,
-  "mimo-month": MIMO_MONTH_AGENT_KEY,
-  "nolo-fullstack": MIMO_MONTH_AGENT_KEY,
-  fullstack: MIMO_MONTH_AGENT_KEY,
-  "full-stack": MIMO_MONTH_AGENT_KEY,
-  "全栈": MIMO_MONTH_AGENT_KEY,
-  "nolo 全栈工程师": MIMO_MONTH_AGENT_KEY,
-
-  // Qoder CLI (本机 Qoder CLI 实现 agent)
-  qoder: QODER_AGENT_KEY,
-  "qoder-agent": QODER_AGENT_KEY,
-  "qoder cli": QODER_AGENT_KEY,
-  "qoder-cli": QODER_AGENT_KEY,
-
-  // Explicit local CLI agents. These are ordinary private agent records that
-  // run through the current computer local runtime when unbound.
+  // Explicit local CLI agents. These are ordinary user-scoped agent records
+  // that run through the current computer local runtime when unbound.
   "local-codex": LOCAL_CODEX_AGENT_KEY,
   "codex-local": LOCAL_CODEX_AGENT_KEY,
   "local codex": LOCAL_CODEX_AGENT_KEY,
   "local-qoder": LOCAL_QODER_AGENT_KEY,
   "qoder-local": LOCAL_QODER_AGENT_KEY,
   "local qoder": LOCAL_QODER_AGENT_KEY,
-
-  // 产品前端实现
-  "frontend": NOLO_FRONTEND_AGENT_KEY,
-  "frontend-agent": NOLO_FRONTEND_AGENT_KEY,
-  "frontend-implementer": NOLO_FRONTEND_AGENT_KEY,
-  "nolo-frontend": NOLO_FRONTEND_AGENT_KEY,
-  "nolo frontend": NOLO_FRONTEND_AGENT_KEY,
-  "前端agent": NOLO_FRONTEND_AGENT_KEY,
-  "前端 agent": NOLO_FRONTEND_AGENT_KEY,
-  "前端": NOLO_FRONTEND_AGENT_KEY,
-
-  // Win Qwen (本地轻量无Token消耗辅助)
-  "win-qwen": WIN_QWEN_AGENT_KEY,
-  "win qwen": WIN_QWEN_AGENT_KEY,
-  "winqwen": WIN_QWEN_AGENT_KEY,
-
-  // 其他辅助/特定角色
-  "nolo-project-manager": NOLO_PROJECT_MANAGER_AGENT_KEY,
-  "project-manager": NOLO_PROJECT_MANAGER_AGENT_KEY,
-  "nolo-pm": NOLO_PROJECT_MANAGER_AGENT_KEY,
-  pm: NOLO_PROJECT_MANAGER_AGENT_KEY,
-  "项目经理": NOLO_PROJECT_MANAGER_AGENT_KEY,
-  "nolo 项目经理": NOLO_PROJECT_MANAGER_AGENT_KEY,
 };
 
 function parseAgentKeyFromInput(raw: string): string {

package/agentMachineCommands.ts

@@ -1,6 +1,6 @@
 import type { MachineHeartbeat } from "./connector-experimental/protocol";
 import { resolveConnectorWebSocketTarget } from "./connectorWebSocketTarget";
-import { resolveCliAgentKeyInput } from "./agentAliases";
+import { resolveAgentInput } from "./agentNameResolver";
 import {
   type AgentCommandDeps,
   type LocalCliExecutor,
@@ -173,10 +173,10 @@ export async function runAgentBindCurrentCommand(
 ) {
   const env = deps.env ?? process.env;
   const output = deps.output ?? process.stdout;
-  const agentKey = args[0]?.trim();
-  if (!agentKey || agentKey === "--help" || agentKey === "-h") {
-    output.write("Usage: nolo agent bind-current <agentKey>\n");
-    return agentKey ? 0 : 1;
+  const agentInput = args[0]?.trim();
+  if (!agentInput || agentInput === "--help" || agentInput === "-h") {
+    output.write("Usage: nolo agent bind-current <agent>\n");
+    return agentInput ? 0 : 1;
   }
 
   const authToken = resolveAuthToken(env);
@@ -197,6 +197,15 @@ export async function runAgentBindCurrentCommand(
   const machine = await (deps.machineInfo ?? detectLaunchableMachineInfo)();
 
   try {
+    const { agentKey } = await resolveAgentInput({
+      agentInput,
+      authToken,
+      db: deps.db,
+      env,
+      fallbackFetchImpl,
+      fetchImpl,
+      output,
+    });
     await heartbeatCurrentMachine({ authToken, fetchImpl, machine, serverUrl });
     const existing = await readAgentRecord({ agentKey, authToken, fallbackFetchImpl, fetchImpl, serverUrl });
     const updated = {
@@ -228,7 +237,7 @@ export async function runAgentBindCurrentCommand(
     return 1;
   }
 
-  output.write(`Bound agent ${agentKey} to this machine: ${machine.name} (${machine.machineId})\n`);
+  output.write(`Bound agent ${agentInput} to this machine: ${machine.name} (${machine.machineId})\n`);
   return 0;
 }
 
@@ -243,8 +252,6 @@ export async function runAgentSmokeCurrentCommand(
     output.write("Usage: nolo agent smoke-current <agent> --msg \"hello\"\n");
     return agentInput ? 0 : 1;
   }
-  const agentKey = resolveCliAgentKeyInput(agentInput);
-
   const authToken = resolveAuthToken(env);
   if (!authToken) {
     output.write("[nolo] agent smoke-current requires an auth token. Run `nolo login` or set AUTH_TOKEN.\n");
@@ -264,6 +271,15 @@ export async function runAgentSmokeCurrentCommand(
   const sentMessages: string[] = [];
 
   try {
+    const { agentKey } = await resolveAgentInput({
+      agentInput,
+      authToken,
+      db: deps.db,
+      env,
+      fallbackFetchImpl,
+      fetchImpl,
+      output,
+    });
     await heartbeatCurrentMachine({ authToken, fetchImpl, machine, serverUrl });
     const existing = await readAgentRecord({ agentKey, authToken, fallbackFetchImpl, fetchImpl, serverUrl });
     assertSmokeCompatible(existing, machine);
@@ -358,8 +374,6 @@ export async function runAgentRuntimeDoctorCommand(
     output.write("Usage: nolo agent runtime-doctor <agentKey>\n");
     return agentInput ? 0 : 1;
   }
-  const agentKey = resolveCliAgentKeyInput(agentInput);
-
   const authToken = resolveAuthToken(env);
   if (!authToken) {
     output.write("[nolo] agent runtime-doctor requires an auth token. Run `nolo login` or set AUTH_TOKEN.\n");
@@ -372,6 +386,15 @@ export async function runAgentRuntimeDoctorCommand(
   const machine = await (deps.machineInfo ?? detectLaunchableMachineInfo)();
 
   try {
+    const { agentKey } = await resolveAgentInput({
+      agentInput,
+      authToken,
+      db: deps.db,
+      env,
+      fallbackFetchImpl,
+      fetchImpl,
+      output,
+    });
     const agent = await readAgentRecord({ agentKey, authToken, fallbackFetchImpl, fetchImpl, serverUrl });
     const requiredCapability = requiredCapabilityForAgent(agent);
     const runtimeClass = classifyAgentRuntime(agent);