Session labels, a redesigned approval flow, and long sessions that compact instead of failing.
- Connect your computer from the desktop app, with access approval and a tunnel that keeps running while the app is closed.
- Fork a conversation from any point in a session.
- Share a secret or connector account with an agent across all its sessions, triggers and schedules.
- Failed triggers show their reason on the Schedule page and send one push notification when a failure streak starts.
- Edit queued prompts in place in a dedicated card above the composer.
New
70- Fork a conversation. A session's conversation offers a Fork action, so you can branch from any point.
- Cancel a subscription from the billing pane.
- One permission per topic. The broad
project.customize.*permissions are replaced byproject.settings.write,project.sandbox.write, andproject.model.read/.write. Agent changes useproject.agent.write. Every role keeps exactly what it had. Project members can now open Agents and Triggers read-only. - Permissions decide, for agents as for people. An agent that holds a permission can do the work end to end.
kortix_permissions: all,"*", and any list that contains"*"mean the same thing. Withall, an agent can also manage project members and delete the project. Creating credentials stays with people. - An agent can grant only what it holds. When an agent edits an agent's permissions, connectors, secrets, or Apps, it can add only what it holds itself. This applies through every route, change request, and push. An agent that does not hold every grant opens a change request instead of pushing the default branch directly.
- One authorization path. Every agent with a
kortix_permissionsgrant acts as itself, in every project. The per-project switch back to the authority of the person who started it is gone. - One bad permission entry no longer empties an agent. An entry Kortix cannot grant is skipped, and the rest of the agent's grant stays.
kortix validatestill reports it. - The Meta agent is platform-owned. It runs read-only and appears first in the agent picker.
- No more active-session limits. Billing is the only limit on how many sessions run at once.
- The blog is served from its own app at
/blog. - Your computer, on the web. Each physical computer appears once, even after you re-pair it. Computer Use runs inside the Kortix desktop app, and it asks for every macOS permission right after you connect. Pairings with no hardware id that stay silent for 30 days are removed.
- Edit a queued prompt in place. The prompt queue sits in its own card above the composer.
- Review Center has its own page. You approve requests in a modal on the approve page.
- Channel bindings live in one dialog, with one tab per platform and a settings dialog for each binding. Teams bindings read "Team › Channel" and include the thread title.
- Shared sessions show who sent each message, with an avatar per sender.
- Marketplace redesign: one card per item, a file tree in the sidebar, and related skills.
- A new /developers page. Its "copy prompt command" output now pastes safely into any POSIX shell.
- One-day personal API keys. You can create a key that expires after one day.
- Apps on mobile: a new Apps tab in the project drawer.
- Show files name the file in a hover card.
- Microsoft Teams is on for every project. There is no feature flag to turn on: connect Teams from the project's Connectors → Channels page. A tenant admin consents once, or the project brings its own bot. A project that connected Teams while it was a flag keeps its install.
@kortix/sdkkeepsteamsas a deprecated flag key that always reports enabled. (#8601, #8603) - What Kortix says to one person in Teams stays with that person. In a channel or group chat, only that person sees: - the prompt to connect an account or request access, with the connect button right in the thread; - command replies; - why a message did not run; - approval requests and decisions. Teams marks these "Only you can see this message", as Slack does. The shared "Working on it…" card appears only when the message can run. (#8609)
- Kortix shows when your Teams app is out of date. When your organization's Teams catalog has an older Kortix app, the Channels page and
kortix channels statussay so and name the two steps: a Teams admin publishes the update, then a team owner updates the app in each team where Teams offers it. A Teams thread that the agent may not read now comes back with who fixes it, instead of Microsoft's error alone. The Teams app moves to version 1.6.1. (#8624) - A failing trigger is no longer silent. When a trigger's run fails, the Schedule page shows the trigger as failed with the reason, and the account owner gets one push when a failure streak starts, not one per fire. The next run that finishes clears it. A reused session that grew too large to compact is retired, so the next fire starts a fresh one. (#8586, #8588)
- Human Messaging reaches every agent surface (projects with the Human Messaging feature on). Agents in sessions, Slack, Teams and the hosted MCP server know how to ask a person and answer back, and the mobile app groups what people asked you under "Asked you". An ask from a session runs the asking session's own agent. (#8622, #8623)
- Share a secret or a connector account with an agent. "Who can use it" now offers agents next to people and groups. A value shared with an agent reaches every session of that agent, triggers and schedules included; running the agent stays gated by its own access. A secret link can keep the value to the person who asked.
kortix secrets share --agent <name>does the same from the CLI. (#8635, #8638) - Approve or deny a connector call from the Review Center header, next to Back, as for a change request. Deny takes an optional note that reaches the agent. Long parameter values collapse behind Show more. (#8641)
- An agent's ask names the agent, not the session title, in "Asked you" (Human Messaging projects). With the Human Messaging feature off, it no longer appears anywhere. (#8626, #8637)
- Every prompt records who wrote it, and the transcript shows the author.
- Agents can ask a person a question or start a group conversation with people, behind the
human_messagingproject flag (off by default). - Sessions carry writable labels and metadata across the API, SDK, CLI, MCP and web, and the session list filters by label.
- Redesigned approval, preview and install consent screens.
- A split "Connect your computer" dialog with one-click CLI copy.
- Recent session views stay open across project navigation; the command palette finds sessions by ID.
- The desktop app copies the current session URL from the Go menu and reports sanitized crash telemetry.
- Push notifications route by browser presence: a session open in a tab does not also push.
- Project-bound agents get their own cost rollups.
kortix apps access --viewer, and the CLI lints manifest wiring references.- The pi harness loads repository-native Pi configuration and supports config releases.
- Each agent's OpenCode plugins load in isolation.
- Sign in to OpenCode Go with your OpenCode account from a sign-in card, instead of pasting a key; each provider now has its own key name.
- Connector discovery is on by default for every project.
- Choose who can use a secret's value: only you, everyone, or chosen people and groups.
- Manifest v3: agents boot from
kortix.yaml. - Computers are connector accounts like any other: the same row, the same Share dialog (people, groups or everyone), and one registration per machine.
- The audit trail shows Via for each event: the credential the API authenticated (browser session, personal access token, connected app, session token, API key, service account or SCIM token), never a self-reported client label.
- The hosted MCP server reaches full
kortixCLI parity through a sandboxedkortixtool, and serves project skills. - Connectors are first-class MCP tools.
- Projects can run their sessions in the US East region.
- A GDPR-complete privacy policy and a public subprocessors page at /legal/subprocessors.
- Local mode: connect your computer from the desktop app. Each computer is a connector account with access approval, and the tunnel keeps running in the background while the app is closed.
- Microsoft Teams reaches Slack parity: direct messages, a connected note, a home tab, message actions, edit and delete,
/unbind,/statusbuttons,/sessions, the full agent picker, review cards, and call-to-action links as buttons. - Saved session history is always on, and a reload shows the newer saved copy.
- Mobile: an empty session opens on its composer, messages queue while the computer wakes, and sub-agents show their saved steps.
- A redesigned Create a project page. New accounts get their name during onboarding, not from the email address.
- Sessions list as a tree that shows who started each run, with server-side search.
- Copy a session ID or link from the session menu.
- One account-level MCP server at
/v1/mcp, bound to your token like the CLI. It exposes sandbox shell and files, skills, and the session list; long commands run as jobs, and connected apps can be listed and revoked.kortix mcpruns the whole CLI as an MCP server, and a Connect MCP menu sets it up. - The LLM gateway accepts the OpenAI Responses API, so the Codex CLI works against Kortix.
- Reminders: schedule prompts into a session, with a Reminders view and a per-project flag.
- Approvals: the agent describes each gated call, the approver can reply, and approval cards reach Slack and Teams.
- New projects get a three-step onboarding and a first chat.
- GitHub projects can be created under personal GitHub accounts, and their sessions start.
- Sandbox templates can run Docker inside the sandbox.
- Agents can store secrets they already have, and long setup links load.
- ChatGPT accounts show when they need reconnection, and a failed ChatGPT turn offers Reconnect or Connect ChatGPT.
- Saved session history is 1:1 with the live session and on by default, including sub-agents.
- The mobile app signs in to self-hosted Kortix instances.
- Slack: a session's Slack thread is bound automatically so replies come back to it, and the agent can remove its own reactions.
- The CLI saves large connector results as JSON (
--out, and MCP results above 16 KB).