8.2 Software changelog

0.2.2 (stable)

2026-10-18 · GitHub Release · npm · Docker Hub

Teloa 0.2.2 (Community edition) brings persistent roles, team collaboration, multiple execution harnesses, project memory, document retrieval and versioned deliverables into one workspace. Describe your goal, follow the work, handle required approvals, then collect and revise the result.

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.

Experience and reliability fixes

• Clearer import recovery: when an import outcome is unconfirmed, preserve the file and field mapping, guide users to check the original request and do not resend automatically.
• Release checks match the current interface: update the employee-creation preview assertion and precisely identify field-protocol prompts intended only for the model.

Install and upgrade

• Install @teloa/cli@0.2.2 from npm, use this version’s native GitHub Release package, or run the Docker Hub image teloa/teloa:0.2.2.
• For an existing native installation, use the new command package to run teloa stop, teloa upgrade --to 0.2.2 and teloa status. Keep the original --home, installation identity, data and workspace. Retain the Compose project and volumes when upgrading Docker, and back up before switching.
• This release has been verified on native macOS ARM64 and Docker Linux ARM64; amd64 and other native systems have not been verified.
• Codex delivery, saving a method and running a plan manually have real-model verification. Calendar-triggered real-model execution, Claude Agent through the owner’s Anthropic sign-in, complete OpenAI/ElevenLabs speech combinations and all optional device combinations have not been fully verified.

See installation and backup and upgrades. The release documentation snapshot is retained under /v/0.2.2/; the root path tracks current documentation.

Previous stable releases

View the 0.2.1 stable release record

0.2.1 (stable)

2026-10-18 · GitHub Release · npm · Docker Hub

Teloa 0.2.1 (Community edition) brings persistent roles, team collaboration, multiple execution harnesses, project memory, document retrieval and versioned deliverables into one workspace. Describe your goal, follow the work, handle required approvals, then collect and revise the result.

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.

Experience and reliability fixes

• Create employees in Markdown: the main creation entry accepts one description, carries in the business and preserves drafts; writes still require preview and confirmation.
• Clearer counts: marketplace “Added” consistently means items added on this machine; the workbench labels task counts explicitly, and deliverable counts show the actual values.
• Import and calls: Traditional Chinese import copy respects regional terminology; narrow-window call controls avoid both quick chat and the companion.
• Recover existing work: older assignments can recover their exact original owner message; submission failures retain safe diagnostics without automatic resending.
• Avoid blocked concurrency: verified finished work releases its active slot while unknown token usage remains reserved. A timeout alone never releases the slot.
• Catalog and documentation: team requirements describe Teloa permissions; release notes explain employees, teams, execution harnesses and speech services separately.

Install and upgrade

• Install @teloa/cli@0.2.1 from npm, use this version’s native GitHub Release package, or run the Docker Hub image teloa/teloa:0.2.1.
• For an existing native installation, use the new command package to run teloa stop, teloa upgrade --to 0.2.1 and teloa status. Keep the original --home, installation identity, data and workspace. Retain the Compose project and volumes when upgrading Docker, and back up before switching.
• This release has been verified on native macOS ARM64 and Docker Linux ARM64; amd64 and other native systems have not been verified.
• Codex delivery, saving a method and running a plan manually have real-model verification. Calendar-triggered real-model execution, Claude Agent through the owner’s Anthropic sign-in, complete OpenAI/ElevenLabs speech combinations and all optional device combinations have not been fully verified.

See installation and backup and upgrades. The release documentation snapshot is retained under /v/0.2.1/; the root path tracks current documentation.

View the 0.2.0 stable release record

0.2.0 (stable)

2026-10-18 · Available on GitHub Releases, npm and Docker Hub.

AI employees: lasting responsibility for recurring work

• 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. Some employee and group creation flows in 0.2.0 still use structured configuration.

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.

Installation, upgrades and support

• Use the stable command package to run teloa stop, teloa upgrade --to 0.2.0 and teloa status. Keep the original --home for a custom installation; the upgrade retains identity and data and creates a backup before switching. Keep an existing Docker deployment's Compose project and data volumes, and back it up before updating the image.
• Native macOS ARM64 and Docker Linux ARM64 are verified separately; amd64 and other native operating systems are outside this release's acceptance. Configure and check each model, speech provider and optional device combination according to its guide. A stable version number does not grant permissions or guarantee result quality.
• See installation and backup and upgrades. Stable documentation is preserved under /v/0.2.0/; the root path continues to track current documentation.

Historical prereleases

View Alpha/Beta release history

0.2.0-beta.7 (preview · GitHub Release / Docker Hub)

2026-10-18 · The native package is published on GitHub Releases and has been verified on macOS arm64 with Node.js 24. The Docker image has passed an isolated startup check on Linux ARM64. npm still provides 0.2.0-alpha.7. It includes everything in 0.2.0-beta.6.

This historical version collected Beta-stage business, marketplace and installation fixes. The complete capability overview for stable 0.2.0 is in the section above.

Latest fixes

• Fix: business pages now separate Records from Dashboards, and each tab remembers its own page. Dashboard cards show their title once, state shared notes once per page (cards still note their own missing or truncated data), size to their content, and label chart bars with categories and values. Pages created from an official template show their built-in page names in the interface language, while names you changed stay as you set them.
• Fix: in the marketplace, a team's skills and connections are counted separately, a team added to this computer shows Added with Continue adding, counts use the singular form for one item, buttons no longer wrap their labels in English, and the template import dialog wording was corrected.
• Upgrades: run teloa upgrade --to 0.2.0-beta.7 from the new command package to upgrade an existing installation, such as 0.2.0-beta.6, 0.2.0-beta.5 or 0.2.0-alpha.7, while keeping its identity and data.

Known limitations are the same as in 0.2.0-beta.4.

0.2.0-beta.6 (preview · superseded by 0.2.0-beta.7)

2026-10-18 · The native package is published on GitHub Releases and has been verified on macOS arm64 with Node.js 24. It is not published to npm or Docker Hub. It includes everything in 0.2.0-beta.5.

• Fix: in-app guidance now points to the places that exist today: resume a newly added employee from Employees, open files and skills from Apps, reopen a configuration draft from Added, and the Auto Dream notice opens the employee it refers to. Wording that still said solution now says template, and several English labels in the work results panel and import forms were corrected.
• Upgrades: run teloa upgrade --to 0.2.0-beta.6 from the new command package to upgrade an existing installation, such as 0.2.0-beta.5, 0.2.0-beta.4 or 0.2.0-alpha.7, while keeping its identity and data.

Known limitations are the same as in 0.2.0-beta.4.

0.2.0-beta.5 (preview · superseded by 0.2.0-beta.6)

2026-10-18 · The native package is published on GitHub Releases and has been verified on macOS arm64 with Node.js 24. It is not published to npm or Docker Hub. It includes everything in 0.2.0-beta.4.

• Fix: when another add of the same catalog employee is still installing its methods, adding that employee no longer returns early as pending; it continues to the same method installation and returns the complete receipt for the same employee.
• Upgrades: run teloa upgrade --to 0.2.0-beta.5 from the new command package to upgrade an existing installation, such as 0.2.0-beta.4, 0.2.0-beta.3 or 0.2.0-alpha.7, while keeping its identity and data.

Known limitations are the same as in 0.2.0-beta.4.

0.2.0-beta.4 (preview · superseded by 0.2.0-beta.5)

2026-10-18 · The native package is published on GitHub Releases and has been verified on macOS arm64 with Node.js 24. It is not published to npm or Docker Hub. It includes everything in 0.2.0-beta.3.

• Fix: running a plan right away while the scheduler is recovering the same run no longer reports a conflict, marks the plan as failing or leaves an extra session; the run starts once.
• Upgrades: run teloa upgrade --to 0.2.0-beta.4 from the new command package to upgrade an existing installation, such as 0.2.0-beta.3 or 0.2.0-alpha.7, while keeping its identity and data.

Known limitations: saving a confirmed deliverable's method as a plan from the conversation, running it once manually, opening the result and completing the task have been verified with a real model; a run started by the calendar schedule itself has not. Other limitations are the same as in 0.2.0-beta.3.

0.2.0-beta.3 (preview · superseded by 0.2.0-beta.4)

2026-10-18 · The native package is published on GitHub Releases and has been verified on macOS arm64 with Node.js 24. It is not published to npm or Docker Hub. See Install and run Teloa for installation and upgrades.

• Runtime: DSH is pinned to 0.2.1-rc.2.
• Upgrades: run teloa upgrade --to 0.2.0-beta.3 from the new command package to upgrade an existing installation, such as 0.2.0-alpha.7, while keeping its identity and data. Other versions still upgrade from the npm registry.
• Work and deliverables: assign work to the general agent or an AI employee and follow it in the original conversation. Deliverables keep versions; give feedback or revise a selected part, and earlier versions stay readable.
• Reusable methods: save a confirmed way of working as a skill, or as a plan that stays paused until you enable it.
• Collaboration: group conversations carry explicit @ mentions through the work; employee chats are kept separate from general conversations.
• External coding agents: run Codex or Claude Agent tasks from the workbench with native approvals, using credentials you configure.
• Web search and fetch: optional DeepSeek search and page fetch in Settings > Connections and runtime > Web search, with your own credentials.
• Market: one flow to create employees and teams; installing an employee brings its complete resources; reviewed app packs; share an AI employee as a template.
• Business: local business work with approved record changes, and dashboards that reflect task results.
• Voice: local speech recognition, and speech playback with MiniMax, OpenAI or ElevenLabs, including compact bilingual voice selection, preview and continuous playback.

Known limitations: saving a confirmed deliverable's method as a plan through the conversation, enabling it and its first scheduled run have not been verified end-to-end with a real model. In complex analyses, model conclusions can claim more than the evidence supports; review deliverables before relying on them. Claude Agent with Anthropic models through your own account sign-in has not been verified.

0.2.0-beta.2 (preview · superseded by 0.2.0-beta.3)

2026-10-18 · The first public 0.2.0 Beta preview. Its GitHub Release is unchanged. Its command package cannot upgrade an existing installation to its own version; use 0.2.0-beta.3 instead.

0.2.0-alpha.7 (published · Alpha)

2026-10-01 · The exact version is published on npm as @teloa/cli and Docker Hub as teloa/teloa. Docker has been verified on Linux ARM64; amd64 has not been verified.

• Build and verify an SOC business from the business page: connect a read-only alert source, declare its mapping and enable sync, assign a real Task/Run from a record, then see its progress and the exact version of the accepted deliverable on the same business page. Other industries are examples without end-to-end acceptance.
• CSV and XLSX imports preview data, write a fixed batch, and recover the same request after a lost response or restart. Sync rules are controlled per mapping; equal external IDs from different sources do not overwrite local records.
• Includes projects, task teams, updated extension management and composer improvements, along with marketplace, connection, local-model and extension work. External connections and extensions still need configuration and authorization.