ElizaOS（Eliza）ElizaOS（Eliza）
ElizaOS 把「角色」做成 agent 单元（MIT，TypeScript）：一个 character 配置文件定义人格与能力， 常驻进程接多渠道（官方仓自称「agentic operating system」）。加密社区出身、插件生态大—— 框架面与投机叙事要分开看。
ElizaOS makes the "character" the agent unit: one config file defines persona + capabilities, a resident process connects channels. Crypto-community origins and a big plugin ecosystem — keep the framework separate from the speculation narrative.
适合与不适合When to use it, when not to
适合：有人格的常驻 agent（社交/社区 bot）、TS 生态、插件式扩展。 不适合：编程任务底座、企业工作流编排、对第三方插件供应链敏感的场景。
Fits: resident persona agents (social/community bots), the TS ecosystem, plugin-style extension. Not a fit: coding-task bases, enterprise workflow orchestration, plugin supply-chain-sensitive settings.
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-31
- 出品属地Origin
- 国外出品foreign-made ElizaOS 社区（GitHub org elizaOS，20 个公开仓）；主体站现挂「Eliza Research」（elizaresearch.ai，自述「builds products at the intersection of AI and people」）。ElizaOS community (GitHub org elizaOS, 20 public repos); the entity site now runs as "Eliza Research" (elizaresearch.ai, self-described as building "products at the intersection of AI and people").
- 国内使用Direct access
- 大陆可直连direct OK elizaos.ai 直连 301→elizaresearch.ai 直连 200、docs.elizaos.ai 直连 200（2026-10-31）；GitHub 仓大陆直连波动（同日代理可达）。elizaos.ai measured 301→elizaresearch.ai 200 direct, docs.elizaos.ai 200 direct (2026-10-31); the GitHub repo's mainland reachability fluctuates (200 via proxy the same day).
- 备案状态CAC filing
- 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-31 检索）；开源框架不面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-31); an open-source framework not serving the mainland public, so filing does not apply.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
插件式多模型接入（各家 API 与本地线都有插件，未逐条清点）； 它的本体不在模型，在「角色」抽象——一个 agent 配置文件定义人格+能力。
Plugin-style multi-model access (each vendor's API and local lines have plugins, not itemized); its core is not the model but the "character" abstraction — one agent configuration file defines persona + capabilities.
- 运行位置Where it runs
TypeScript 运行时（官方仓描述「Open source agentic operating system」）：起一个常驻进程， agent 按角色配置对外接渠道。GitHub elizaOS/eliza 19,739★、最近推送 2026-10-30（API 核验，活跃）。
A TypeScript runtime (official repo description: "Open source agentic operating system"): run a resident process, the agent connects to channels per its character config. GitHub elizaOS/eliza 19,739 stars, last push 2026-10-30 (API verified, active).
- 本地文件Local files
自托管跑在你自己的进程/机器上；记忆与状态在本地存储层（细节未逐条核验）。
Self-hosted, running in your own process/machine; memory and state live in a local storage layer (details not itemized).
- 关机后的任务Tasks after shutdown
常驻进程+多渠道接入是默认形态：agent 长期在线接消息、按角色行事—— 「角色 agent」是它的产品叙事核心。
Resident process + multi-channel connection is the default form: the agent stays online long-term receiving messages and acting per its character — the "character agent" is the core of its product narrative.
- 工具与扩展Tools & extensions
插件生态是主轴（渠道插件/动作插件）；MCP 支持状态未逐条核验。
The plugin ecosystem is the main axis (channel plugins / action plugins); MCP support status not itemized.
- 上下文与记忆Context & memory
角色文件（character 配置）定义人格与知识面，跨渠道共享（官方文档 Character Interface/Agent Configuration 在册）。
The character file defines persona and knowledge surface, shared across channels (official docs: Character Interface / Agent Configuration on record).
- 权限与限制Permissions & limits
插件与动作可触达外部账号/渠道——接什么渠道、给什么凭据是配置者责任； 插件第三方代码面要自己审。
Plugins and actions can reach external accounts/channels — which channels to connect and which credentials to grant is the configurator's responsibility; third-party plugin code must be audited by you.
- 适合什么任务Best for
适合：要「有人格的常驻 agent」（社交/陪伴/社区 bot）、TS 生态、插件式扩展。 不适合：要编程任务底座、要企业工作流编排、对第三方插件供应链敏感的场景。
Fits: "a resident agent with a persona" (social/companion/community bots), the TS ecosystem, plugin-style extension. Does not fit: coding-task bases, enterprise workflow orchestration, scenarios sensitive to third-party plugin supply chains.
头号误解Top misconception
- 品牌与域名散：elizaos.ai 301→elizaresearch.ai（新主体站「Eliza Research」）、文档在 docs.elizaos.ai、仓在 elizaOS/eliza——三处口径要一起看，别按单域名判断项目死活Brand and domains are scattered: elizaos.ai 301→elizaresearch.ai (the new entity site "Eliza Research"), docs at docs.elizaos.ai, repo at elizaOS/eliza — read all three together; do not judge the project's liveness by one domain
- 加密社区出身：项目与 token 生态关联深（ai16z 线）——选型时把技术框架与投机叙事分开，本站只记框架面Crypto-community origins: deep ties to the token ecosystem (the ai16z line) — separate the technical framework from the speculation narrative; this site records only the framework surface
- 插件=第三方代码：动作插件可持凭据触达外部渠道，供应链审查是配置者责任Plugins = third-party code: action plugins can hold credentials reaching external channels — supply-chain review is the configurator's duty
未知项清单Known unknowns
- MCP 支持状态（未逐条核验）
- 记忆/状态存储层细节（未逐条核验）
- Eliza Research 与 elizaOS 社区/token 生态的治理关系（未核验，不下断言）
- MCP support status (not itemized)
- Memory/state storage-layer details (not itemized)
- The governance relationship between Eliza Research, the elizaOS community, and the token ecosystem (not verified, no assertion made)
证据来源Evidence sources
判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-31，内容更新日content updated on 2026-10-31。
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| repo | elizaOS/eliza · 仓库（MIT；19,739★，最近推送 2026-10-30，GitHub API 核验）elizaOS/eliza · repository (MIT; 19,739 stars, last push 2026-10-30, GitHub API verified) | https://github.com/elizaOS/eliza |
| docs | ElizaOS · 官方文档（Overview/Character Interface/Agent Configuration）ElizaOS · official docs (Overview / Character Interface / Agent Configuration) | https://docs.elizaos.ai/ |
| docs | Eliza Research · 主体站（elizaos.ai 301 目标，当日核验）Eliza Research · entity site (the 301 target of elizaos.ai, verified same day) | https://elizaresearch.ai/ |
| changelog | elizaOS/eliza · Releases（changelog）elizaOS/eliza · Releases (changelog) | https://github.com/elizaOS/eliza/releases |
实测记录Measured runs
本档未跑集成与性能实测；结论只覆盖 API 与官方文档披露的能力面。
This site has not completed measured runs. The test protocol is at protocols/framework/_protocol.md.
相关条目Related entries
- CrewAICrewAI同大类对照：CrewAI 按「角色分工」编排多 agent，ElizaOS 按「角色人格」常驻单 agent——两种「角色」语义。Same-category contrast: CrewAI orchestrates multi-agent work by "role division"; ElizaOS keeps a single agent resident by "role persona" — two meanings of "character".
- Hermes AgentHermes Agent同大类对照：同为常驻通用 agent 运行时，Hermes 走模型厂商线，ElizaOS 走社区插件线。Same-category contrast: both are resident general-purpose agent runtimes — Hermes follows the model-vendor line, ElizaOS the community-plugin line.
- ChatGPTChatGPT跨大类对照：ChatGPT 的「自定义 GPT」也是人格化角色但跑在官方托管里；ElizaOS 把角色跑在你自己的进程与渠道里。Cross-category contrast: ChatGPT's "custom GPTs" are also persona-style characters but run inside the official hosted surface; ElizaOS runs characters in your own process and channels.
本页由This page is generated from the ai-handbook 数据层生成（CC BY 4.0）。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.