What's New

This page tracks what shipped in Octo, newest first. Open an entry for the detail, and follow Read more where there is a full page on the topic.

Entries are grouped by the month the change landed. Anything marked Behavior change altered how something already worked — worth reading even if you are not adopting the new feature.

August 2026

[Voice] Dial — place outbound calls from a workflow

Workflows can now call someone rather than only answer. The Dial node places an outbound call and branches on what happened: Connected, Voicemail, No answer, or Failed. From the Connected branch onward it is an ordinary AI call — same agent, transcript, and recording as an inbound one.

Everything before the node runs before the phone rings, so a CRM lookup or ticket can complete first and the agent already knows who it is calling. Calls go out from one of your purchased numbers.

Connect a Play node to the Voicemail branch and the call waits for the greeting and the beep, then leaves your message. Leave that branch empty and it hangs up as soon as a recording answers, which is faster and costs less.

[Automation] One-time schedules — run a workflow once at a chosen time

Schedules previously ran on a recurring cron. A schedule can now fire once, at a specific moment, which is what a requested callback needs.

Give the time either as an exact instant or as a local wall-clock time paired with a timezone. A local time keeps its hour even if that zone’s daylight-saving rules change before it is due, so “Tuesday at 9am” stays 9am. A local time sent without a timezone is rejected rather than guessed.

A one-time schedule retires itself once it has fired, so the same request cannot place a second call. The schedule page shows whether one is waiting, overdue, or already run.

[Developer] OneOcto CLI 1.3 — manage Octo from a terminal

The CLI is published on npm as @appbox.ai/oneocto-cli and installs with npm install -g @appbox.ai/oneocto-cli. It covers 44 resources with the canonical list, get, create, update, and delete verbs, and returns JSON from every command.

Two things make it more than a wrapper over the API. Code-defined flows publish, revise, export, audit, and diagnose workflows from a single spec, so node ids, canvas layout, and edge wiring cannot be got wrong. And the CLI describes its own capabilities through oneocto resources, describe, and explain, which makes it usable by an AI agent that needs to discover what is possible rather than be told.

[Docs] Octo rebrand and a new documentation home

The product is now Octo, and this documentation site moved to docs.oneocto.dev. Update any saved links to the new address.

Nothing in the product changed as part of the rename. Resource names, API paths, and CLI commands are unaffected.

July 2026

[Workflows] Published workflow versions are read-only — Behavior change

A published version is fixed once it is live. The configuration tab and every node inspector present its fields as read-only, so the state of a published workflow is clear at a glance.

To change a published workflow, start a draft from it, edit the draft, and publish that. If you script against the API, oneocto flow revise-workflow starts the draft for you when the latest version is published.

[Automation] Schedules — run a workflow on a recurring cron

Schedules trigger a workflow on a recurring cron expression, without an inbound call or message to start it. Each schedule records its runs, so you can see what fired and what happened.

Pause a schedule to stop its timer, resume it to re-arm, and run it once immediately without disturbing the cron timer. Manage schedules from the Schedules page, or from the CLI with oneocto schedules.

[Billing] Self-serve plans, top-ups, and saved cards

Select a plan, buy additional credits, and manage payment methods directly in the product. Card details are entered in the payment provider’s own flow and never touch Octo.

Plan limits apply automatically — the number of phone numbers you can hold follows your active plan.

[Billing] Auto-recharge when credits run low

With auto-recharge enabled, credits top up from your saved payment method as interactions complete, so a busy deployment keeps running without manual top-ups.

Voice interactions now attribute LLM usage back to the interaction that caused it, so usage reporting reflects where credits actually went.

[Billing] LLM provider catalog with per-provider pricing

Available LLM providers are now managed centrally and synchronized to your instance. Each provider shows its credits-per-minute cost, so you can see what a model choice will cost before selecting it in a workflow.

Providers approaching retirement carry a deprecation date, so you can plan a move well ahead of time.

[Voice] Barge-in handling and a hard call duration limit

Callers can interrupt the agent mid-sentence and be heard. Playback yields the moment the caller starts speaking, so the exchange feels like a natural conversation.

Calls also carry a hard duration limit. When a call reaches the ceiling it ends cleanly and the interaction is finalized, keeping call spend predictable.

[Platform] Notification logs

Sent notifications are now recorded with their delivery outcome, so you can confirm delivery and filter to a specific recipient or template.

June 2026

[Platform] Reliable invite and notification email

Invitations and notifications are sent through a dedicated delivery service, with your instance logo and a ready-to-use sign-in link in every invite email.

May 2026

[Voice] Multiple speech providers — ElevenLabs, Murf, and Soniox

Voice synthesis runs on ElevenLabs, Murf, or Soniox, each with its own audio format and sample-rate handling. The provider is resolved per workflow version, falling back to the workflow’s language.

Pick a provider per workflow based on voice quality, latency, or cost, matching each workflow to the voice that suits it.

[Workflows] Node slugs you can reference and copy

Every node now carries a readable slug alongside its generated id, and the inspector can copy it to the clipboard. Slugs are what you reference from templates and prompts, so they are stable to write against and readable when you come back to a workflow months later.

April 2026

[Workflows] Canvas editing — undo, redo, snaplines, and sticky notes

The workflow canvas gained the editing behavior you would expect from a design tool. Undo and redo cover every canvas operation. You can pan the canvas and rubber-band select multiple nodes at once. Snaplines appear while dragging to align nodes and show consistent spacing.

Sticky notes let you leave context on the canvas itself — useful for explaining a branch to whoever opens the workflow next.

[Workflows] Watch a run happen on the canvas

The debug panel subscribes to live interaction events, so a run lights up the canvas as it executes. Node traversal is highlighted as execution moves through the graph.

[Voice] Generate and preview speech before you ship

Voice generation is available directly in the product, and a preview modal plays a sample so you can hear a voice and language combination before committing a workflow to it.

[Workflows] Transfer a call to a contact

The Transfer node can hand a live call to a number stored as a contact. Create the contact once and reference it from any workflow that needs to escalate.

Transfer nodes are terminal — a call that transfers does not come back into the graph.

[Platform] API keys for programmatic access

API keys let external systems authenticate without an interactive user session. Keys carry a name, an optional expiry for planned rotation, and the permissions of the account behind them.

[Platform] Audit logs and per-record history

Changes to records are now recorded and reviewable, both as a searchable audit trail and as history on individual records. Use it to answer who changed a workflow, when a role assignment moved, or what a setting was before it was edited.

March 2026

[Telephony] Phone numbers, provisioning, and recordings

Search the provider for available numbers, purchase one, assign it to an entry point, and release it when it is no longer needed — all from the product.

Call recordings are stored durably and retrieved through time-limited signed URLs rather than being served directly. Recording behavior and silence handling are configured per workflow in phone settings.

[Knowledge] Knowledge sheets

Knowledge sheets give an agent structured reference data to draw on during a conversation. Sheets are edited in a grid with searchable content, so you can maintain lookup data without an external system.

[Workflows] Test a tool without building a workflow around it

Tools can be tested standalone. REST tools show the full request and response, so you can confirm an endpoint works before wiring it into a workflow.

You can also import a REST tool directly from a cURL command, which is usually faster than transcribing an API’s docs field by field.

[Platform] Environment settings

Configuration values are managed per environment, with the input type matching the value — a code editor for structured content, plain inputs for simple values. Settings can hold an empty value where that is meaningful.

[Voice] Streaming speech synthesis

Speech is synthesized and played as a stream rather than being generated in full before playback begins, which cuts the pause between the agent deciding what to say and the caller hearing it. Text is normalized before synthesis so numbers, dates, and digits are spoken naturally.

[Interactions] Interaction finalization with transcript and sentiment

When an interaction ends it is finalized: the transcript is assembled, configured analysis prompts run against it, and sentiment is normalized onto the record. The result is a conversation you can read back and review in full.

February 2026

[Workflows] Filler and delay messages while a tool runs

Tools keep the conversation flowing while they work. A tool can play a message before it runs, repeat a delay message while waiting, and say something specific if it does not succeed. Each message is static text, AI-generated, or silent.

[Workflows] Tool configuration unified — Behavior change

REST and script tools now share a single configuration object, with AI-extracted parameters in aiFields.

Existing tools were migrated automatically. Integrations that write tool definitions directly against the API should adopt the new shape.

January 2026

[Platform] Roles, permissions, and team sign-in

Access control has its own surface: roles are managed on dedicated pages, and each role shows the permissions behind it in full.

Sign-in, registration, password reset, and user invitations landed alongside, so an instance could be opened to a team instead of a single account.

[Workflows] AI Extraction and AI-driven conditions

The AI Extraction node pulls structured fields out of a conversation, so you can capture a date, a name, or an order number without asking the caller to repeat it in a rigid format.

Conditions can branch on an AI judgment rather than only on a deterministic comparison, which covers the cases where “did the caller agree?” has no clean boolean answer.

December 2025

[Platform] ★ v1.0 — the first release

The first release, built around a drag-and-drop canvas for designing conversational workflows. It shipped with the node set the product still uses — Start, Play, Tool, Transfer, If/Else, and Agent — where agent nodes branch on named exit conditions, so a conversation leaves a node by whichever outcome it actually reached.

The entries below it in this month cover what shipped alongside: versioning and publishing, the test panel, dashboards, and contacts.

[Workflows] Versioning and publishing

Workflows are edited as drafts and published as immutable versions, and an entry point routes to a specific version. That means you can keep building without touching what is live, and roll forward deliberately.

[Workflows] Test a workflow while you build it

The test panel holds a live conversation with the workflow open on the canvas, so you can try a change the moment you make it. An interaction can be resumed to continue exactly where it left off.

[Dashboards] Dashboards and widgets

Charts and tables over your own interaction data, driven by scripts, so reporting is defined in the product rather than exported to a spreadsheet.

[Platform] Contacts, voices, and languages

Contacts store the people and numbers your workflows reach. Voice and language selection arrived alongside, including a default language per workflow.

November 2025

[Workflows] Workflows run as resumable graphs

The execution engine underneath the product. A workflow runs as a graph whose state is durable, so a run can pause partway through — waiting on a caller, a tool, or a schedule — and continue later rather than starting over.

Everything that came after depends on it: resuming an interaction, watching a run on the canvas, and firing a workflow from a schedule are all the same engine.

About these dates

Entries are dated by the month each change landed in the product. Where a change altered existing behavior, it is marked Behavior change rather than listed as a new feature.