Teloa Community 0.2.10

Teloa Community 0.2.10

0.2.10 是 0.2.9 的补丁版：原生包的发行清单补齐固定的 DSH 版本号（dshVersion），与 ReleaseManifest schema 一致。功能与 0.2.9 相同。

0.2.9 带来的功能（本版继续提供）

• 输入框「下一条建议」（对齐 Codex Composer predictions）：回复后空输入框内以灰字给出模型生成的下一步；按 Tab 才放入草稿、不会自动发送；开始输入即隐藏、删回空会重新出现；设置 → 通用可关闭；文案支持简/繁/英
• 建议由宿主受管辅助模型通路生成（withAuxiliaryContext + withAuxiliaryModel），不直连供应商 HTTP，不产生消息、任务或执行

验证

• pnpm build、check:client、check:dsh 通过；test:repo 112/112；test:contract 676/676
• 镜像 teloa/teloa:0.2.10（linux/arm64）构建成功；隔离 compose 冒烟 app/db 健康、GET / 401、镜像内 CLI 0.2.10 且含本功能
• 原生包：安装后 teloa --version = 0.2.10、teloa doctor 通过；清单含 dshVersion: 0.2.1-rc.2

发布状态

• GitHub Release：本文件
• 原生包：teloa-cli-0.2.10.tgz（19,193,694 字节，3628 文件），SHA-256 5e04b3ee538f73388d52ef97b4aee15d39219ab839a17db1d0bb2635e43ded48
• npm：已发布 @teloa/cli@0.2.10（latest 已指向该版本）https://www.npmjs.com/package/@teloa/cli/v/0.2.10 ；已用 npm i @teloa/cli@0.2.10 实测安装，teloa --version = 0.2.10
• Docker Hub：已发布 teloa/teloa:0.2.10（linux/arm64），digest sha256:4f91a98bb5ff20a0c3e7d41783d65b74ad3bb6c44407e5a5beeaaf748344b2fd
  • docker pull teloa/teloa:0.2.10；隔离 compose 冒烟通过（app/db 健康、GET / 401、镜像内 CLI 0.2.10 且含本功能）
  • Compose 地址：https://docs.teloa.ai/downloads/0.2.10/compose.yaml
• 原生包下载：https://github.com/teloa-ai/teloa/releases/download/v0.2.10/teloa-cli-0.2.10.tgz

Teloa Community 0.2.9

Teloa Community 0.2.9

后续补丁版 0.2.10 已发布，修正了本版原生包发行清单缺失的 dshVersion 字段（运行期校验不依赖它，安装与 teloa doctor 不受影响）。建议升级：https://github.com/teloa-ai/teloa/releases/tag/v0.2.10

输入框「下一条建议」（对齐 Codex Composer predictions）

• 助手回复后，空输入框内以灰字给出模型生成的下一步（框内显示、无额外提示按钮）
• 按 Tab 才放进草稿，不会自动发送；继续输入即隐藏，删回空会重新出现；Escape 丢弃本条
• 设置 → 通用 →「显示下一条建议」（默认开，可关闭）；文案支持简/繁/英，其余语言回退英文
• 生成走宿主受管辅助模型通路（withAuxiliaryContext + withAuxiliaryModel），不直连供应商 HTTP，不产生消息、任务或执行

验证

• 分支：pnpm build、check:client、check:dsh 通过；test:repo 112/112；test:contract 676/676；本功能单测 16/16
• 镜像：teloa/teloa:0.2.9（linux/arm64）构建成功；隔离 compose 冒烟 app/db 健康、GET / 401；镜像内 CLI 0.2.9 且包含本功能
• 真实模型实例：灰字显示模型句、Tab 后进草稿且消息数不变、输入即消失、设置开关生效

发布状态

• GitHub Release：本文件
• 原生包：teloa-cli-0.2.9.tgz（18,520,555 字节，3628 个文件），SHA-256 7291dbf231dfdbc9f65385b93756084ff3d56b1802b22e0b4a1c0db8cfdb09ae
  • 下载：https://github.com/teloa-ai/teloa/releases/download/v0.2.9/teloa-cli-0.2.9.tgz
• Docker Hub：已发布 teloa/teloa:0.2.9（linux/arm64），digest sha256:d6721248…
  • docker pull teloa/teloa:0.2.9；Compose：https://docs.teloa.ai/downloads/0.2.9/compose.yaml
• npm：已发布 @teloa/cli@0.2.9（发布时 latest 指向该版；现 latest 已是 0.2.10）https://www.npmjs.com/package/@teloa/cli/v/0.2.9 ；已用 npm i @teloa/cli@0.2.9 实测安装，teloa --version = 0.2.9、teloa doctor 通过

已知问题

• 本版原生包 release-manifest.json 缺少必填的 dshVersion 字段；运行期 verifyRelease 不校验它，安装、升级与 teloa doctor 均正常。该字段已由 0.2.10 补齐。

Teloa Community 0.2.8

Teloa Community 0.2.8

0.2.8 extends the employee API with per-request execution controls, makes successful API work deliver a formal artifact and completed task automatically, and closes the remaining employee-package and market creation gaps found in production QA.

Highlights

• Employee API execution controls: permissionMode (danger-full-access, workspace-write, read-only) and custom model provider/model on start and continue. Each round inherits or overrides explicitly, is persisted, returned in work status, checked against native presets and the platform model catalog, and protected by idempotency.
• Automatic API result delivery: a fixed successful result now creates a formal artifact, completes the linked task, records delivery, and updates work progress in one transaction. Failed delivery rolls back and retries with the same fixed result; legacy succeeded-but-undelivered work is repaired without recalling the model.
• Employee package materials: package material bodies can be previewed, employee single chats retrieve within the employee's role scope, and the library can add all of an employee's materials to local retrieval in one action.
• Employee package lifecycle: update/unload previews, transactional switching, shared-resource protection and old-install management remain available.
• Market creation: the Create menu now includes Create skill and Create app alongside AI employee, AI team, import template and import skill.
• Agent presets: the Teloa standard preset is grouped under built-in presets; PTC code modes have clear names and accurate retained-state descriptions.
• Settings and layout: settings groups have visible separators and hierarchy; the non-Chinese sidebar brand no longer overlaps new/search actions.
• Security baseline: container and documented native runtime baseline is Node.js 24.22.1; built-in skills hard uninstall remains available.

Install

• npm: npm install --ignore-scripts @teloa/cli@0.2.8
• GitHub tarball: teloa-cli-0.2.8.tgz (SHA-256 in SHA256SUMS)
• Docker: teloa/teloa:0.2.8 (Linux ARM64); use the attached compose.yaml

Upgrade

Install 0.2.8 into a new command directory, run teloa stop against the old home, then teloa upgrade --to 0.2.8. The upgrade backs up data before switching. 0.2.7 → 0.2.8 keeps tasks and identity; existing work continues with its saved configuration.

Verification

• Backend, harness, SDK and browser targeted regressions for the changed features passed.
• npm candidate fresh-cache install, 13 lifecycle checks and four-page headless UI acceptance.
• Public source CI and post-release registry/image readback are recorded in the release evidence.

Teloa Community 0.2.7

Teloa Community 0.2.7

0.2.7 adds real hard uninstall for installed skills from both the workbench and natural language, with explicit host confirmation and protection for current selections, loaded packages and historical run evidence. It also closes production-QA gaps across task and group execution gates, project and employee memory, AutoDream, creation-draft recovery, installed-market management and directory focus.

Highlights

• Hard uninstall installed skills: removes the managed native skill directory and installation records; refuses to break the current selection, industry load usages or historical run evidence. Single-version selections can be uninstalled directly; multi-version selections require switching to the version to keep.
• Natural-language uninstall: new teloa_skills_uninstall tool requires a real installation identity and two explicit confirmations (uninstall confirmation plus host tool approval); the model cannot forge confirmation.
• Execution gates: empty-tool employee/group runs are blocked at prepare/start; AutoDream system-digest runs are correctly exempt.
• Project and employee memory: project sessions no longer fail with UNKNOWN after project changes; unavailable employee materials are rejected before save and localized at prepare.
• Creation and market: created-sentence drafts are retained for recovery after prepare; installed market packages/skills expose update/uninstall management; share drafts can be applied or discarded.
• AutoDream: terminal evidence, plan timezone, same-day duplicate protection and scheduled skip.
• Directory and completion: filter popovers stay above the scrolling directory; completion selection resets when the connection changes.

Install

• npm: npm install --ignore-scripts @teloa/cli@0.2.7
• GitHub tarball: teloa-cli-0.2.7.tgz (SHA-256 in SHA256SUMS)
• Docker: teloa/teloa:0.2.7 (Linux ARM64); use the attached compose.yaml

Upgrade

Keep the existing data and identity by installing 0.2.7 into a new command directory, running teloa stop against the old home, then teloa upgrade --to 0.2.7. The upgrade creates a backup before switching. Verified: 0.2.6 → 0.2.7 CLI upgrade preserves tasks; Docker 0.2.7 starts on a 0.2.6 database volume and keeps data.

Verification

• Public source gate: repo 112/112, contract 676/676, backend 2622/2622, typecheck/check pass.
• npm candidate: fresh-cache install, 13 lifecycle checks, four-page headless UI, stop passed.
• Docker candidate: fresh volume start and 0.2.6 data-volume upgrade passed.
• Known environment-only failures: 4 local sandbox/PTC/worktree tests are not part of this release's product paths.

Teloa Community 0.2.6

Teloa 社区版 0.2.6 修复自然语言创建、使用与分享 AI 员工、AI 团队、应用和 SKILL 的连续操作问题。

• 原创 SKILL 可读取明确声明的许可并分享；同名技能仍核对实际选用来源与正文。
• 确认员工草稿后落定原草稿，避免重复创建；模板缺字段时准确提示修正位置。
• 资源准备清单核对技能实际可用状态，避免把被遮蔽的安装记录显示为就绪。
• 完成分享后可继续下一次操作；接收完成后可直接导入另一份模板，未完成申请保留原选择。
• 修正群工作路由与交付复核的参数指引；已用真实 MiniMax 验证初稿、复核和最终稿。
• 四类自然语言创建示例补齐使用与分享步骤，并加入中英文真实界面配图。

安装与升级 · 开发指南 · 分享方法

安装：npm install --prefix ./teloa-command-026 --ignore-scripts @teloa/cli@0.2.6。已有安装使用原 --home，先停止并备份，再执行 teloa upgrade --to 0.2.6。镜像为 teloa/teloa:0.2.6（Linux ARM64）；SDK 继续使用 @teloa/sdk@0.2.4。附件提供原生安装包、Compose 配置及 SHA-256。

---

Teloa Community 0.2.6 fixes natural-language authoring, use and sharing across AI employees, AI teams, Apps and SKILL.

• Share original skills with an explicitly declared license; preserve source and content checks for names shared by multiple installations.
• Apply the original employee draft once and report missing template fields precisely.
• Check actual skill availability before marking imported resources ready.
• Continue sharing and importing after completed operations while retaining unfinished requests.
• Clarify group-routing and delivery-review parameter contracts; verify draft, review and final delivery with real MiniMax.
• Add verified authoring, usage and sharing instructions with Chinese and English interface screenshots.

Install and upgrade · Developer guide · Sharing

The native package is verified on macOS ARM64 and the container on Linux ARM64. SDK compatibility remains @teloa/sdk@0.2.4.

Teloa Community 0.2.5

Teloa Community 0.2.5

2026-10-22

修复员工准备执行时错误要求注入可选的浏览器／电脑提供方服务的问题。未启用这些组件时，员工仍可使用已配置模型；对应浏览器与电脑工具仍按实际可用性和授权显示。

• 用真实 MiniMax 验证 HTTP API、SDK、MCP 的员工调用、固定成果、同一工作续做与取消。
• 本次更新宿主和安装器；SDK 接口保持兼容，继续使用 @teloa/sdk@0.2.4。
• 原生安装验证范围：macOS ARM64；Docker 验证范围：Linux ARM64。
• 保留原安装 home 与数据，使用官方 CLI 的停止、备份和 teloa upgrade --to 0.2.5 流程。不要重新初始化已有数据库。

安装与升级 · 员工 API / SDK / MCP · 完整开发者指南

安装渠道状态 / Distribution status

GitHub 安装包与 Docker 0.2.5 已就绪。npm 官方正在处理安装与发布服务故障；npm 渠道尚未补发，@teloa/cli 的 latest 当前仍为 0.2.4。

GitHub tarball and Docker 0.2.5 are available. The npm channel is pending the registry incident; npm latest remains 0.2.4.

新建空目录后，可下载本页的 compose.yaml，以独立项目启动 Docker：

curl --fail --location https://github.com/teloa-ai/teloa/releases/download/v0.2.5/compose.yaml --output compose.yaml
TELOA_PORT=3101 docker compose -p teloa-025 up -d --no-build

原生安装包：本页的 teloa-cli-0.2.5.tgz。安装时仍需从 npm 获取依赖，可能受当前 npm 故障影响；已有运行环境请保留原 home 与数据。

English

Fix employee execution preparation when optional browser or computer providers are unavailable. Optional services are now looked up without requiring dependency injection. Available tools still depend on actual provider availability and authorization.

Real MiniMax validation covers invocation, versioned results, continuation of the same work, and cancellation through HTTP API, SDK and MCP. This host patch remains compatible with @teloa/sdk@0.2.4.

Validated installation platforms: native macOS ARM64 and Docker Linux ARM64. Keep your existing home and data, and use the CLI backup and upgrade flow.

Install and upgrade · Employee integrations

Source: 698cd1e0ce9aff036f0bc1aa5dda45f479088f88.

Teloa Community 0.2.4

Teloa Community 0.2.4

中文

2026-10-21
本次更新让 AI 员工与 AI 团队更稳定地承接持续业务，延续 0.2.3 的成果统一右栏与协作界面。

工作台与首次使用

• 工作台、对话、项目、员工、业务、资料和市场使用更清楚的导航与页面层级；头像直接打开“我的分身”，设置保留独立入口。

• 主聊和员工会话在首次进入、应用内切换、刷新后保留可用编辑器和各自的文字草稿。

• 首次仅配置一个可用的 BYOK 提供方、原默认缺少密钥时，自动初始化默认模型；本人有效默认与明确选模保持。

• 群路由跟随当前默认模型，按所选模型保留思考档位；认证失败与正常空回答分开处理，正常空回答最多重问一次。

• 自然语言新建任务先准备草稿。没有真实创建时明确提示，可带着原目标使用“按表单创建”；保存不执行。明确交办走原生确认卡，批准后才启动，拒绝不创建任务。

• 项目总览可直接打开 Markdown 创建窗口，保留未提交草稿；业务内项目筛选在页签往返后保留，并按业务与本人连接隔离。

• 通用工作只提供适用的菜单动作；窄窗口中资料列表、正文与返回路径保持可达。

• 归档会话可撤销；市场加载、重试和取消状态更准确；退役等高影响操作按影响范围明确确认。

• 平台普通文字与控件统一跟随当前文字字体，数量和时间保持表格数字对齐；代码、快捷键和终端保留各自字体。工作总览、需要你、任务与自动化保持协调的字号层级。

• 市场卡片限制摘要行数并对齐尺寸，长标题或说明不再拉高整排；完整说明仍可在详情查看。“我的应用与技能”置于市场顶部。

• 内置本地模型统一在“设置 > 本地模型”选择、下载和启用；资料页保留简短检索状态、索引操作及设置入口，不自动下载或启用模型。

身份、回复与工具发现

• 明确 Teloa 助手、个人分身和 AI 员工的工作身份，让自我介绍与当前真实岗位一致；涉及技术架构时再解释执行框架。
• 简单问题优先简洁、直接回复；完整成果、必要依据、真实阻断与审批要求仍完整保留。
• 回复语言优先遵循本轮明确要求和可信设置，再按当前输入语言回应；资料中的原文、引用、代码和专有名称保持原样。
• 按当前工作需要发现并加载工具，使用前核对实际接口契约；现有授权、连接和审批边界保持。
• 避免在后续模型输入中重复携带历史产品规则，保留原始记录、岗位事实与权限边界。

安装与模板兼容

• 源码部署能识别 Docker 的另一种“卷不存在”回执并继续创建数据库；权限或连接错误仍会停止。
• 市场员工预览与宿主使用同一模板校验，保留结构化职责和运行预设，模板中的模型账户不会随安装继承。市场站同步展示触发、自主动作、确认点、升级规则与交付检查。
• 市场统一提供 AI 员工、AI 团队、应用与技能四个独立浏览入口；技能可单独筛选与添加，应用保留其原有技能和连接组成。
• 修复在设置中启用官方网页搜索后，重启无法启动的问题。
• 应用安装恢复会复用经当前目录和完整内容校验的已准备技能，只为缺失来源重新下载；版本或内容不符时明确停止。
• 遇到 GitHub API 明确限流时，已审核目录可从同一固定提交归档核对并取得技能；继续校验文件、许可、来源与摘要，也兼容官方仓库更名。添加应用不会替你连接外部账号。
• 原生 Auto review 的审核请求正确关联当前工具和工作，避免因受理归属缺失而中断；撤销、取消和工作额度继续逐次核验。

分享与工作成果

• AI 员工、AI 团队、应用与技能可从工作台打开官方在线分享页，核对公开文件并明确确认后生成链接；接收方按自己的配置安装，分享者可撤销链接。
• 看板可导出 PNG；完整原始记录可用时可导出 CSV，也可明确分享到同业务协作群。数据读取失败可重试；发送结果未知时核对原请求，避免重复发送。
• 业务配置历史可查看并按原校验恢复已记录版本，恢复前保留明确确认。
• 已启用原生浏览器时，“开始”侧栏提供手动网页入口，代理按实际启用的提供方发现浏览器工具。

员工对外调用与集成

• 业务系统可通过稳定 HTTP API、OpenAPI 3.1 和 TypeScript / JavaScript SDK 调用已启用的员工，读取状态与固定版本成果，并在原工作上续办或请求停止。
• 外部 Agent 可通过 /mcp 的 Streamable HTTP 接口调用同一工作能力。接口密钥在“设置 > 员工对外调用”创建，绑定一位员工的版本、业务范围、权限、有效期与并发上限；支持轮换和撤销。
• 可配置签名 CloudEvents 回调，核验签名后按事件标识去重；投递记录持久保存，失败自动重试，也可手动重投。运行成功与业务验收分别记录。
• 接入步骤、错误处理和示例见员工 API、SDK 与 MCP。本版不声明 A2A 或 MCP Tasks 扩展兼容。

自定义 MCP 应用与权限

• 用 Markdown 说明创建应用，在草案确认卡中填写接入地址和多组 Header 认证；支持连接验证、失败重试、查看、断开和删除，凭据加密保存。
• 本人可显式选择 Full access，原默认权限保持；该模式下已授权 MCP 工具不再重复要求额外连接审批，员工工具与业务授权仍单独生效。
• 已明确标注只读、非破坏性且不要求 MCP Tasks 的工具可在原生循环中有界并发；写入、未知或冲突标注的工具继续串行执行。

业务来源驱动员工工作

• 已接入业务来源（如日志应用）的新事件可逐条启动对应员工的工作，并保留来源、对象与任务之间的关联。
• 业务首页按实际同步规则与连接状态显示哪些来源已真正接入；读取中显示“待核对”，不把仅有映射配置当作已接入。
• 业务高级设置在尚未配置同步时显示明确说明和配置路径，避免空白面板；空配置不提供启用或立即同步操作。
• 任务目标与成果正文使用统一排版，浏览器标签页标题跟随当前页面。

群内交接与续办更可靠

• 员工在群内交接给另一位员工时，正式开始调查并可直接使用本次已授权的工具；交接路由失败会在消息下显示状态并可由本人重新安排。
• 本人引用员工回帖或自己当初的交办消息退回修订时，按原任务续办，不另建同题任务；每轮路由互不串扰。
• 原任务已暂停时，续办消息说明原因，并可在原群抽屉中经确认恢复原工作。
• 停下后重新安排的消息会如实结束，不再停在“正在安排”。

交付复核更稳

• 复核回执格式或引用有误时，提示具体哪一处不符（字段、引用段落范围、块号），模型可据此纠正一次。
• 复核期间的自动上下文压缩不再吞掉复核内容；同一轮内可多次压缩。
• 模型误调用未授权工具且已被拒绝时，不再导致整份交付失败；复核正文中的网址路径不再被当作文件读取拦截。
• 模型服务过载（如 529）按可重试处理。

工作额度与恢复

• 工作额度按滚动 24 小时统计模型耗时，额度停止时说明原因与下一步；群消息在路由因额度被拒时同样说明。
• 运行启动按原子方式受理，排队中的计划持久保留。
• 本人执行 teloa upgrade 后，自动恢复仅因本次重启而暂停的工作；本人自行暂停或存在待核对操作的工作保持暂停。

安装与升级

通过 GitHub Release、npm 和 Docker Hub 提供。安装与验收范围为原生 macOS ARM64、Docker Linux ARM64。

升级已有安装时保留原 home 与数据，使用官方 CLI 的备份和 upgrade 流程；不要重新初始化数据库。安装步骤见 文档，完整能力说明见 更新日志。

---

English

2026-10-21
This update makes AI employees and AI teams more dependable for continuous business work. It builds on the unified results sidebar and collaboration interface delivered in 0.2.3.

Workbench and first use

• Clearer navigation and page hierarchy for the workbench, conversations, projects, employees, business areas, library, and market. Your avatar opens My twin, while Settings keeps its own entry.

• Personal and employee conversations keep their editors and separate text drafts when first opened, switched, or refreshed.

• When the old default lacks a key and exactly one BYOK provider is configured, Teloa initializes the default model. Valid defaults and explicit model selections are preserved.

• Group routing follows the current default model and its reasoning configuration. Authentication errors are distinguished from normally completed empty replies; an empty reply is retried at most once.

• Natural-language task creation prepares a draft first. If no task was actually created, an inline notice offers Create with a form with the original goal. Saving does not run it. Explicit assignments use the native approval card: approval starts execution, while rejection creates no task.

• Archived conversations can be restored with Undo. Market loading, retries, and cancellation have clearer states, and high-impact actions such as retirement require confirmation appropriate to their effects.

• Create projects directly from the project overview with a Markdown description and preserved drafts. Business project filters survive tab navigation and stay isolated by business and owner connection.

• General work shows applicable menu actions. Reference lists, documents, and the return path remain reachable in narrow windows.

• Ordinary UI text and controls follow the current text font, with tabular alignment for counts and times. Code, keyboard shortcuts and terminals keep their own fonts. Work overview, Needs you, Tasks and Automation use a consistent type hierarchy.

• Market cards constrain summary lines and align their sizes, so long titles or descriptions no longer stretch a whole row. Full descriptions remain available in details, and My apps and skills is placed at the top of the market.

• Choose, download and enable built-in local models in Settings > Local models. The library keeps concise retrieval status, indexing actions and a settings entry; it does not automatically download or enable a model.

Identity, replies and tool discovery

• Clarify the working identities of the Teloa assistant, personal twins and AI employees, so introductions reflect the actual current role. Explain the execution framework when technical architecture is requested.
• Prefer direct, concise answers to simple questions while keeping complete deliverables, necessary evidence, real blockers and approval requirements intact.
• Follow explicit instructions and trusted reply-language settings first, then respond in the language of the current input. Preserve original source text, quotations, code and proper names.
• Discover and load tools as the current work requires, checking their actual contracts before use. Existing authorization, connection and approval boundaries remain.
• Avoid repeatedly carrying historical product rules in later model input while retaining original records, role facts and permission boundaries.

Installation and template compatibility

• Source setup recognizes another Docker “volume not found” response and creates the database volume. Permission and connection errors still stop setup.
• Market employee previews and the host share template validation, preserving structured responsibilities and runtime presets. Model accounts from a template are not adopted on installation. The marketplace website also shows triggers, autonomous actions, confirmation points, escalation rules and delivery checks.
• Browse AI employees, AI teams, Apps and Skills as four independent categories. Skills can be filtered and added separately; Apps keeps its existing skills and connections.
• Fix startup after enabling the official web search option in Settings.
• Resuming an application installation reuses prepared skills verified against the current catalog and full content. Only missing sources are downloaded; version or content mismatches stop recovery.
• When GitHub explicitly rate-limits its API, reviewed catalog skills can be obtained from the same pinned commit archive. Files, licenses, source and digests are still checked, including official repository renames. Adding an app does not connect an external account for you.
• Native Auto review requests are associated with the current tool and work, avoiding an interruption caused by missing admission context. Revocation, cancellation, and work budgets are still checked per request.

Sharing and work results

• Open the official online sharing page for an AI employee, AI team, app or skill, review the public files and explicitly confirm to generate a link. Recipients install with their own configuration, and owners can revoke links.
• Export dashboards as PNG and, when complete raw records are available, CSV, or explicitly share them to a group in the same business. Retry failed reads; recover an uncertain send result through the original request to avoid duplicate messages.
• View business configuration history and restore a recorded version through the existing validation and explicit confirmation.
• When the native browser is enabled, the Start sidebar offers a manual browsing entry. Agents discover browser tools from the provider that is actually enabled.

Employee APIs and integrations

• Business systems can use the stable HTTP API, OpenAPI 3.1 contract, and TypeScript / JavaScript SDK to invoke an enabled employee, read status and versioned results, continue the same work, or request cancellation.
• External agents can invoke the same work capabilities through Streamable HTTP at /mcp. Create keys in Settings > Employee integrations, binding each to one employee version, business scope, permissions, expiry, and concurrency limit. Keys support rotation and revocation.
• Optional signed CloudEvents callbacks keep durable delivery records, retry failures automatically, and support manual redelivery. Verify signatures and deduplicate by event ID. Execution success and business acceptance are recorded separately.
• See Employee API, SDK and MCP for setup, errors, and examples. This release does not claim A2A or MCP Tasks extension compatibility.

Custom MCP apps and permissions

• Describe an app in Markdown, then enter...

Teloa Community edition (0.2.3)

Teloa 社区版（0.2.3）

本次更新改善成果交付与日常协作体验，延续 0.2.2 的 AI 员工、AI 团队、项目与项目记忆、本地文档索引、Codex / Claude Code Harness 及语音 TTS 能力。

成果统一右栏

• 会话、群聊、任务和项目沿用同一套成果右栏。先看成果列表，选择后原栏阅读正文；通过「全部成果」返回列表，不再嵌套常驻目录。
• 保留版本选择、来源、下载、未提交反馈和原工作上下文；支持调整栏宽及放大阅读。
• 群聊只展示该群实际分享的成果及固定版本。个人未分享的版本和草稿不会自动进入群成果。
• 会话目录的「… → 工作成果」可直接读取已保存成果。按标题搜索时，没有聊天消息但已有保存成果的原会话也可找到，无需重新发送消息。

协作界面更清楚

• 员工「邀请参与协作」改为紧凑列表，保留原成员选择、范围、草稿与明确确认。
• 市场、团队资料、详情和相关抽屉统一间距与滚动层级，减少重复说明和无效留白。

任务目录稳定性

已确认完成群回复的任务可以正常读取；后端、执行宿主与客户端采用一致校验，普通待办、异常状态和归属检查保持。

安装与升级

使用 GitHub Release 附件中的原生包，或对应 npm / Docker Hub 版本。原生包已核对 macOS ARM64 完整性；Docker 发布范围为 Linux ARM64。

升级已有安装时保留原 home 与数据，使用官方 CLI 的备份和 upgrade 流程；不要重新初始化数据库。安装步骤见 文档，完整能力说明见 更新日志。

---

Teloa Community edition (0.2.3)

This update improves deliverable review and everyday collaboration. It builds on the AI employees, AI teams, projects and project memory, local document indexing, Codex / Claude Code harness integrations, and voice / TTS capabilities delivered in 0.2.2.

One sidebar for results

• Conversations, groups, tasks and projects use the same results sidebar. Select a result from the list, read it in place, and return with “All results”; there is no nested permanent directory.
• Versions, sources, downloads, unsent feedback and the original working context remain available, with resizable and expanded reading views.
• Group results show only versions explicitly shared with that group. Private versions and drafts are not automatically included.
• Open saved results through the conversation directory’s “… → Work results” menu. An explicit title search can also find an original conversation with saved results but no chat messages, without sending a new message.

Clearer collaboration controls

• Employee collaboration invitations use a compact selection list while preserving members, scope, drafts and explicit confirmation.
• Marketplace, team materials, details and related drawers share consistent spacing and scrolling, with less repetition and empty space.

Reliable task listings

Tasks with verified completed group replies remain readable. Backend, execution-host and client validation now agree, while ordinary attention requirements, invalid-state checks and ownership checks remain enforced.

Install and upgrade

Use the native package attached to this release or the matching npm / Docker Hub version. Native package integrity is verified on macOS ARM64; Docker publication targets Linux ARM64.

Keep the original home and data, and use the official CLI backup and upgrade flow. Do not initialize the existing database again. See the installation guide and full changelog.

Teloa Community edition (0.2.2)

简体中文 · English

English

Teloa Community edition (0.2.2) is here: build and run your own AI team

Today, Teloa Community edition (0.2.2) is officially available.

Teloa is an AI-native team workspace. Describe a goal in natural language, create AI employees with ongoing responsibilities, and organize a team around projects, materials, memory and deliverables.

This release brings together AI employees, AI teams, multiple execution harnesses, projects and project memory, local document indexing, voice interaction and versioned delivery. It also turns lessons from product development into two standardization initiatives made publicly available to the industry.

30-second workspace tour

teloa-community-0.2.2-en.mp4

Community 0.2.2 · Actual interface with sample data. Watch with captions

AI employees: persistent roles for ongoing work

Describe the role, working requirements and expected deliverables in natural language or Markdown, then review the proposal to create an AI employee.

For example:

Create a product researcher to organize user feedback, check product assumptions, and deliver source-backed analysis and validation suggestions. List open questions when evidence is insufficient, and ask for my confirmation before publishing externally.

Each employee can have its own responsibilities, working methods, business scope, reference materials, skills and available tools. These settings stay with the role so it can keep handling similar work.

Chat privately with an employee, inspect its tasks, deliverables and accumulated experience, or add it to a team to collaborate on a shared goal.

An employee's role identity is managed separately from the model. Changing models or starting a new task can preserve the same employee's responsibilities and work history.

AI teams: organize responsibilities around shared results

Combine multiple AI employees into a team with clear responsibilities for research, analysis, production and review.

The marketplace provides team templates for product, marketing, sales and other work. They organize roles, skills, reference materials, optional connections and work templates together, reducing repetitive setup. After adding a template, review the members, target business and work arrangements before enabling the capabilities you need.

Use @ mentions in group chats to involve specific employees while retaining the source of assignments, collaboration and result replies. Main messages and topics are organized separately, with distinct entry points for ordinary chats, employee conversations and groups.

Persistent teams carry ongoing responsibilities; temporary execution teams serve the current task. Independent parts can run in parallel before the responsible worker consolidates the results. Collaboration across business areas continues to follow each member's actual access to materials and tools.

Multiple harnesses: DSH, Codex and Claude Code

Teloa connects different execution engines to the same workflow:

• DSH handles the main conversation, native execution and tool calls.
• Codex handles independent code, file and tool tasks through its native execution provider.
• Claude Code / Claude Agent connects to the native Claude execution path, handles independent work and returns the results.

You can ask directly:

Use Codex to review the code this time, and have Claude Agent analyze these files.

The results return to the original task, retaining the work's source and attribution.

Model connections and harnesses are configured separately. Each execution provider uses its own authentication, and external engines require confirmation of their native working directory and permissions before launch. Choose the execution approach that fits the work, then follow its actual status and deliverables in the workspace.

Projects and project memory: carry context into subsequent work

Projects bring together goals, briefs, tasks, employees, groups, materials, automations and deliverables, with dedicated project conversations.

Project goals, active rules, relevant materials and memories can participate in subsequent model requests. Inspect what was used and its sources to understand the basis of an employee's work.

Review memory candidates, trace their sources, withdraw future use, and share a fixed revision. New conversations can choose whether to read and write long-term memory, and the owner decides whether personal preferences participate in a project.

From the first discussion through later deliveries, a project can accumulate reusable background, rules and reasoning.

Local document indexing and local models: put your own materials to work

Add explicitly selected local Markdown files to an index, track material versions, and inspect citations and the locations of source excerpts during retrieval.

Prepare retrieval models after confirmation on the materials page, with options including Qwen3 Embedding and EmbeddingGemma. Chat models handle understanding and generation; embedding models handle retrieval. The two are managed separately.

Through Ollama, check the local chat environment, connect existing models, and confirm a download or cancel model preparation.

The document index runs on the device or container where you deploy Teloa. Answers can use local models or remote models you configure. When you choose a remote chat service, relevant retrieved excerpts may be sent to that service as part of the current context.

Natural-language tasks and versioned deliverables: from a brief to a result

The main task-creation flow centers on a natural-language or Markdown brief. Describe the goal, requirements and delivery format; the source conversation, project and business are carried in from context.

Follow execution, handle required approvals, stop work, preview files and collect deliverables in the same workflow. Even before creating employees, you can work independently with Teloa, the squirrel assistant, or the general-purpose Agent.

Preview and download deliverables, then request revisions to a selection or the whole document. Each revision retains a clear version. Earlier results such as v1 and v2 remain available with their original attribution, and acceptance can refer to the specific version adopted at the time.

The workspace previews Markdown, code, images, PDF, HTML, Office files and spreadsheets so you can inspect the actual delivery.

Business workflows, dashboards and the marketplace

Create or adjust business configurations in natural language, review and adopt the draft, then import records or connect authorized data sources.

Business content and statistical dashboards are organized separately, so you can inspect individual records and observe changes across the business. Tasks, materials and deliverables can continue within the same business context.

Discover AI employees, AI teams, skills, apps and connectors through dedicated marketplace entries. The apps page manages installed capabilities and connections.

For more complex work, use step-by-step Workflow orchestration, PTC tool composition, and Ralph iteration when explicitly requested by the owner. Optional capabilities such as Browser Use, Computer Use and IM channels are configured and authorized separately as needed.

Voice input, TTS and calls: collaborate by speaking

Teloa brings voice input, recognition, speech output and calls into the workspace:

• Voice input: SenseVoice supports local transcription. Recognized text enters an editable draft for the owner to review and send.
• Call recognition: choose MiniMax cloud recognition or local SenseVoice.
• Text-to-speech: MiniMax, OpenAI and ElevenLabs are supported, with separate model, voice and credential settings.
• Voices and previews: MiniMax offers Mandarin and English voice selection and previews. Other providers use their corresponding model and voice settings.
• Continuous speech and call controls: MiniMax supports continuous audio output, reducing repeated starts between short phrases, while retaining mute, interruption and hang-up controls.

Call an employee or the squirrel assistant, or leave a voice message to add work requirements. Calls remain associated with the original conversation, and you can continue reviewing work and deliverables after a call ends.

Auto Dream, employee experience and personal digital twins

Auto Dream organizes private daily summaries from work evidence and records employee experience with its source and scope. You can inspect it and withdraw its use.

Employee experience, project memory and personal digital twin materials are managed separately. A twin can accumulate judgment examples supplied by its owner and observations of working habits to help organize personal working methods. Each material retains its own scope of use.

Methods you have confirmed as useful can also become skills or recurring-plan drafts. Work arrangements are explicitly enabled by the owner, allowing recurring work to develop into processes that can be inspected and adjusted.

Two open standards: how AI works and acts safely

To describe how AI workers are organized and where their security boundaries lie, Teloa has made two standardization initiatives publicly available to the industry, for developers, enterprise users and other platforms to implement, review and improve together.

AI Worker Standard 1.0

Initiated and maintained by Teloa, AI Worker Standard 1.0 provides working definitions and collaboration contracts for AI Workers, AI Teams and AI Organizations.

It describes:

• Worker identity, responsibilities and definition versions that persist across tasks.
• Inputs, outputs, dependencies, authorization conditions and acceptance requirements.
• Responsibilities, handoffs and shared deliverables between team...

Teloa 0.2.1 · Community edition

Teloa 0.2.1 — Community edition is a self-hosted AI-Native Team Studio. Build and run an AI team with persistent roles, project context, delegated execution and versioned deliverables.

简体中文说明见下方

What you can do in 0.2.1

AI employees: lasting responsibility for recurring work

• Describe the role and requirements in Markdown, carry in the current business and preserve the draft. Review the proposed responsibilities and boundaries before explicitly confirming creation.
• Keep an employee's responsibilities, working methods, business scope, knowledge, skills and permitted tools together across tasks.
• Open employee conversations, tasks, deliverables and experience from the employee directory. Chats, employees and groups have separate lists; compact employee overviews reveal details on demand.
• Adding an employee, configuring capabilities and starting execution remain separate actions. Employees work within their actual business and tool permissions.

AI teams: combine roles into a business workflow

• Discover AI teams separately in the marketplace. Team templates can include multiple employees, skills, reference materials, optional connections and work templates, reducing repetitive setup.
• Review the employees and target business, then enable the connections and work arrangements you need. A template does not connect accounts, expand permissions or start background work automatically.
• Collaborate with several employees in a group, use explicit @ mentions, and retain the assignment source and result replies. Sharing a group does not grant access to every member's business materials.
• Lasting teams and temporary execution teams are different: employees are persistent roles; execution assistants split up the current task, can work on independent parts in parallel, and return results for consolidation. They do not automatically become employees or group members.

Multiple execution harnesses: DSH, Codex and Claude Code

Execution option	Its role in Teloa
DSH	Runs the main conversation, tools and native runtime. Teloa maintains business attribution, employee identity, permissions, approvals and delivery. This release pins 0.2.1-rc.2.
Codex	Receives independent work through the native Codex provider, uses its native execution environment after the owner's confirmation, and returns code, file or tool results to the original work.
Claude Code / Claude Agent	Receives independent work through the native Claude Code provider and Claude Agent execution path. Some product labels use “Claude Agent”.

• Specify the engine in natural language: “Use Codex to review this code,” “Have Claude Agent analyze these files,” or ask for an available engine to be selected automatically. A task-specific choice does not change permanent preferences or silently replace the chat model.
• An engine is not a model service. Integration does not include a provider account, subscription or inference allowance. Configure the authentication and model connection required by the chosen provider. Ordinary chats, groups and employees retain their working rules.
• External engines use their native permissions and require the owner's consent for each launch. Teloa's file scope and per-tool approvals are not automatically passed into the external engine; review its actual working directory and permissions before consenting.
• Follow actual execution and required authorization, then receive the result in the original task. If a requested engine is unavailable, Teloa preserves the task and reports the reason instead of silently substituting another engine.

Projects and project memory: context for subsequent work

• Organize project goals, briefs, tasks, employees, groups, materials, automations and deliverables, with dedicated project conversations.
• Include the project goal, active rules, relevant materials and memories in subsequent model requests. Inspect what was used and its sources, beyond a list of linked objects.
• Review memory candidates and sources, withdraw unsuitable content, start a conversation without long-term memory, and explicitly choose whether personal preferences apply.
• Share a fixed memory revision and withdraw subsequent use. Withdrawal cannot recall information already sent to an external model.

Document indexes and local models: retrieval and generation configured separately

• Select local Markdown files explicitly, track versions, add them to an index and inspect citations and excerpt locations. Teloa does not scan the entire computer automatically.
• Prepare the built-in Qwen3 Embedding 0.6B or EmbeddingGemma 2 in the Knowledge retrieval-model panel, with download confirmation and visible progress. This list is separate from the marketplace model catalog.
• Use Ollama to inspect the local chat runtime, connect an existing model, confirm downloads or cancel preparation. Chat models generate answers; embedding models support retrieval. They are managed separately.
• Indexing runs on the deployment device or container. Retrieved excerpts may still reach a remote chat provider. File preview supports more formats than the current local index.

Chats and groups: distinguish stream replies, topics and assignments

• Keep ordinary chats, employee conversations and groups in separate lists, preserving drafts and working context.
• Replies to a group-stream message stay in the stream with their source; topic replies stay inside the topic rather than turning every response into a topic.
• Explicit @ mentions carry through to assigned work. Execution still checks membership, business scope, materials and tool permissions; a group message does not replace the owner's approval.

Natural-language tasks and versioned deliverables

• Describe work in Markdown in the main task entry points, carrying the source conversation, project or business into the draft. Saving is separate from execution.
• Follow execution, handle approvals, stop work, inspect files and obtain deliverables in one working path. The companion and general Agent can work without any created employees.
• Preview and download results, revise a selection or the whole deliverable from feedback, and retain v1, v2 and later versions with their original attribution. Business acceptance continues to reference its selected version.
• Reuse an accepted method as a skill or plan draft. A new plan stays paused until explicitly enabled. Employee creation uses a Markdown draft; some group configuration remains structured.

Business records, dashboards and apps

• Describe a business configuration or change in natural language, review and adopt its draft, import records, connect approved sources and progress to an accepted result.
• Records and Dashboards show their own pages and remember their selections. Cards remove repeated headings and explanations, fit their content, and show chart labels and values; missing data remains distinct from zero.
• Discover employees and teams in the marketplace; manage installed capabilities and connections in Apps. Model setup, application setup and business permissions remain explicit rather than changing automatically when a template is added.

Voice input, TTS and calls

Capability	What this release provides
Voice input	Local SenseVoice transcription after model preparation and microphone permission. Recognized text goes into a draft for review and sending.
Call recognition (ASR)	MiniMax cloud recognition or local SenseVoice, configured separately from speech playback.
Speech playback (TTS)	MiniMax, OpenAI and ElevenLabs, each with its own API key, model and voice settings, rather than one hardcoded provider.
Voice selection and preview	Compact Mandarin/English voice lists and preview for MiniMax. OpenAI and ElevenLabs use model and voice IDs with a saved-configuration test.
Continuous call speech	Improve transitions between consecutive short sentences. MiniMax's persistent bidirectional TTS supplies continuous audio; HTTP fallback remains sentence-based, with stop, cancellation and interruption controls.

• Call an employee or the companion, mute, interrupt a response or hang up, and keep call controls accessible during navigation. Closing details does not hang up; hanging up does not stop work already running in the conversation.
• Record a companion voice message and review its transcription in the original conversation draft. Hiding the companion does not end the conversation.
• Voice credentials are separate from chat-model credentials.

Auto Dream, employee experience and a personal twin

• Auto Dream organizes private daily summaries from work evidence and saves employee experience with sources and scope, with inspection and withdrawal controls.
• Employee experience, project memory and personal twin materials remain distinct. Judgment samples and habit observations are private materials, not automatic context for every ordinary conversation or model-weight training.

Files, tools and upgrade continuity

• Preview Markdown, code, images, PDF, HTML, Office files and tables, inspect current-turn files and available text changes, and save a specific deliverable version when needed.
• Use Workflow steps, PTC tool composition and explicitly requested Ralph iteration within their approval boundaries. Temporary delegation retains the current work scope and allowance.
• Configure and authorize optional Browser Use, Computer Use and IM channels separately. Their presence in the package does not grant device access.
• Preserve the original installation identity, data and workspace during upgrades, with a backup before switching. More consistent drawers, navigation, pending/failure states and reduced repeated copy retain history and unsubmitted drafts.

Fixes in 0.2.1

• Create employees from a Markdown description, retaining business context, drafts and explicit confirmation.
  -...