跳到正文Skip to content
Agent J Beta
菜单Menu
中文EN
登录Sign in

搜索文档和页面Search docs and pages

文档Docs

旧版安装迁移Older-install migration

保留旧命令、状态和下载入口,按原有流程迁移到 Agent J。Keep older commands, state and download addresses working while moving to Agent J.

旧版兼容细节

仅在旧版安装上使用本页。先按当前安装说明核验并保留新签名下载包,告知主人并取得同意,再停止旧服务。不要清除身份、配对信息或个人文件。

  • 先用 uv tool list(或 pipx list)确认旧版主机包是否存在,不要仅凭命令名称猜测安装状态。
  • 确认新包已按当前安装说明下载并核验签名和校验值,再用旧版主机命令的 service uninstall 停止旧服务。用原安装工具卸载列表里确认的旧包,最后按安装说明装 agentj。不要直接执行未经核验的下载。
  • 当前状态目录为 ~/.local/state/agentj。旧状态目录仅在主人同意后迁移:终端询问 y/N;无终端用 agentj --migrate-legacy status。旧路径保留兼容链接,旧服务仍运行时不会强行搬走。
  • 回退用 agentj migrate rollback,随后按原方式重装原版本。不要靠删目录或重新配对来修迁移。
  • 迁移后的主机可能保留旧版兼容命令;旧命令和状态的退役另行安排,本次不删除。新安装只使用 agentj 或短命令 aj,用 agentj alias install 管理短命令。同名命令已存在时不会覆盖。
  • 已配对的旧手机入口继续工作;当前入口为 https://m.agentj.app,不因改名字要求重新配对。

兼容下载地址

旧安装可能仍从原下载域名及其测试、API 子域名获取 /install.md、校验文件和 /dl/。仍须与 GitHub 副本及当前签名核对。本次仅改文字,不迁移域名、API POST/WSS、邮件、浏览器来源或配对资料。

旧访客存储来源继续兼容。本次仅改文字,不调整 iframe、来源校验或浏览器存储。

Older compatibility details

Use this page only for an older install. Download and verify the current signed package using the current install guide: install guide. Tell your human and get their consent before stopping the old service. Keep identity, pairing data and personal files.

  • Check uv tool list (or pipx list) for the old host package. Do not identify an installation by command name alone.
  • After verifying the new package's signature and checksum, stop the old service using its command's service uninstall. Remove the old package listed by your original install tool. Install agentj using the current guide. Never run an unverified download.
  • The state moves from the old state folder to ~/.local/state/agentj on the first run of agentj after your human says yes (Step 5: a terminal asks y/N; without one, agentj --migrate-legacy status). Paired phones, the approval passphrase and the Agent J account stay — no new pairing, no new login. A serve still running on the old folder keeps using it; a compatibility link to the old folder remains.
  • Run agentj migrate rollback to undo the move, then reinstall the old program the same way, in reverse. Do not delete folders or pair again to fix migration.
  • Migrated installations may keep an old compatibility command (a link to agentj if the name is free). It prints a notice pointing here. New installs never get the old command. Retiring old commands and state is a separate step.
  • Use agentj alias install to add the optional short command aj. If it already exists, keep using agentj; the installer does not overwrite it.
  • Optional short command aj: agentj alias install. It is skipped when aj already exists on the Agent J host — then tell your human that aj is taken and they keep using agentj.
  • The phone keeps working at its old address; the new one is https://m.agentj.app (Step 11, nothing to re-pair if the old page still shows the Agent).

Compatible download addresses

Older installations may still use the original download domain and its testing or API subdomains for /install.md, checksums and /dl/. Verify against the GitHub copy and current signatures. This documentation update does not move domains, API POST/WSS endpoints, mail, browser origins or stored pairing data.

The old visitor-storage origin remains compatible. This text-only step does not change its iframe, origin checks or browser storage.

这一页的 Markdown 原文This page as Markdown: zh.md · en.md