---
type: "post"
id: "letta-code-v0-34-26-adds-cursor-coding-a35cf4"
slug: "letta-code-v0-34-26-adds-cursor-coding-a35cf4"
title: "Letta Code v0.34.26 adds Cursor coding workers and fixes workflow worker-run lookup"
description: "Letta Code v0.34.26 adds Cursor as a coding-worker type that agents can dispatch, while tightening several workflow and permission paths."
retrieval_nugget: "Letta Code v0.34.26 adds Cursor as a coding-worker type that agents can dispatch, while tightening several workflow and permission paths. For teams building agentic development systems, the release matters less as a new model capability than as another indication that the harness can select and operate distinct coding environments as workers."
published_at: "2026-10-28"
updated_at: "2026-10-28"
record_date: "2026-10-28"
date_kind: "published_at"
topics: ["mcp","github"]
entities: ["Letta","Letta Code","Cursor","Model Context Protocol"]
related_patterns: ["harness-architecture-outlives-model-choice","agent-security-moves-to-runtime-boundaries"]
novelty_label: "new_fact"
what_changed: "Letta Code v0.34.26 adds Cursor coding workers and fixes workflow worker-run lookup, a new Letta integration/release detail beyond the prior Cursor releases and worker-runtime coverage."
prior_refs: ["memory:df7179fe-9682-886c-a5be-2b3f3b3468bc","memory:a1ab8589-0ef6-8338-a4a8-2d9e7f205d8e"]
source_url: "https://github.com/letta-ai/letta-code/releases"
source_urls: ["https://github.com/letta-ai/letta-code/releases"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:letta-code-v0-34-26-adds-cursor-coding-a35cf4"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/letta-code-v0-34-26-adds-cursor-coding-a35cf4/","markdown":"https://newruntime.com/posts/letta-code-v0-34-26-adds-cursor-coding-a35cf4.md","json":"https://newruntime.com/posts/letta-code-v0-34-26-adds-cursor-coding-a35cf4.json"}
---

# Letta Code v0.34.26 adds Cursor coding workers and fixes workflow worker-run lookup

## Retrieval answer

Letta Code v0.34.26 adds Cursor as a coding-worker type that agents can dispatch, while tightening several workflow and permission paths. For teams building agentic development systems, the release matters less as a new model capability than as another indication that the harness can select and operate distinct coding environments as workers.

## Summary

Letta Code v0.34.26 adds Cursor as a coding-worker type that agents can dispatch, while tightening several workflow and permission paths. For teams building agentic development systems, the release matters less as a new model capability than as another indication that the harness can select and operate distinct coding environments as workers.

## What happened

Letta released Letta Code v0.34.26 on October 28, 2026. The release is listed as the latest version in the project’s GitHub releases and is based on commit `03f96f8`. Its changelog identifies a new agent feature: “add Cursor coding workers.” The supplied release material does not document the setup flow, supported Cursor capabilities, or any requirements for using this worker type; it establishes that Cursor is now a coding-worker option within Letta Code.

The version also changes a workflow lookup path. A fix titled “find latest worker run directly” addresses how a workflow obtains its most recent worker execution. The release notes do not describe the prior failure mode in user-facing terms, but the change is specifically framed as avoiding a history-window lookup. In an orchestration system, finding the relevant latest execution directly is a meaningful reliability detail: follow-on workflow behavior depends on identifying the correct run rather than a result that happens to appear in a bounded history search.

Several other changes concern the execution environment. In code mode, Letta Code now initializes only the MCP servers used by a script. The release also requires approval for assignments to environment-prefixed variables. A headless routing fix now reports why `--computer` routing failed instead of exiting silently. Separately, a webhook skill can target a connected computer, and a memory subagent is hidden from agents while retained for automatic repair.

The changelog contains a wider group of direct-resolution fixes across schedules, repositories, providers, skills, agent IDs, workflow runs, GitHub releases, and other resources. It also updates `@modelcontextprotocol/sdk` to version 1.32.2, fixes stale-approval handling, and lists CI and local-search changes. No pricing, access tier, performance benchmark, compatibility matrix, or migration instruction is provided in the supplied release material. The public source is the [Letta Code release page](https://github.com/letta-ai/letta-code/releases).

## What the archive adds

We have not covered Letta Code before; it opens a new thread.

## Trend signal

This supports [Harness architecture outlives model choice](https://newruntime.com/patterns/harness-architecture-outlives-model-choice/). The release presents Cursor as a worker inside a broader agent system rather than as the whole application boundary. The evidence is narrow: it confirms the added worker type, not equivalence between workers or the quality of their output. Still, it makes the worker-selection layer more visible than any particular model identity.

## Why now

The source provides a concrete release timestamp but no business rationale for the timing. The immediate reason to pay attention is operational rather than promotional: the Cursor-worker addition ships alongside fixes to worker-run retrieval, MCP server initialization, approvals, and headless routing, which are all adjacent to real agent execution.

## Why it matters

A coding agent becomes more useful to a team when it can be placed inside a reliable execution and review system, rather than used only as an interactive assistant. Letta Code’s new Cursor worker expands the set of coding environments that a Letta workflow can dispatch. The direct worker-run lookup matters for teams chaining steps or inspecting results after an agent run, because the orchestration layer needs to point to the right execution before a human or another system can act on it.

The surrounding changes are equally instructive. Initializing only MCP servers a script uses narrows unnecessary setup. Requiring approval for environment-prefixed assignments makes a sensitive boundary explicit. Reporting a failed computer-routing reason makes headless automation easier to diagnose. These are not claims of autonomous reliability; they are small pieces of the operational surface that determine whether automation can be supervised.

## What happens next

- **Letta Code will add or refine further worker and workflow integrations.** (3 months, 65%). Watch for: subsequent releases naming new worker types or workflow dispatch changes.
- **Permission and runtime diagnostics will remain a release focus.** (6 months, 60%). Watch for: further approval, routing, or MCP initialization changes in release notes.

## Limits and uncertainty

The release notes confirm that Cursor coding workers were added, but they do not explain what commands, tools, authentication methods, operating systems, or Cursor versions are supported. They do not say whether Cursor workers behave the same way as other workers, how tasks are routed, or how success is evaluated. The notes also provide no benchmark, customer deployment, reliability metric, or cost comparison. The workflow fix confirms a direct lookup change but does not quantify its impact or enumerate affected configurations. Teams should treat the release as a feature and maintenance signal, then validate it in their own environment before relying on it for production work.

## Skill to build now

Create a small worker-dispatch acceptance test. Give a bounded coding task to the worker configuration your team intends to use, record the resulting run identifier, and verify that a follow-on workflow step retrieves that exact latest run. Include an explicit approval check for any environment-prefixed variable assignment and log the MCP servers initialized by the script. This turns the release’s individual changes into a testable operating contract.

## Reader takeaway

Letta Code v0.34.26 adds Cursor to its coding-worker surface, but its more durable lesson is about orchestration: dispatched workers, exact run lookup, constrained tool initialization, and explicit approvals need to work together. Evaluate the release by testing that chain, not by assuming a new worker type alone makes an automated coding workflow dependable.

## Open question

Which Cursor capabilities are exposed through the new worker type, and how does Letta Code verify or recover from a failed Cursor worker run?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- topic hub: [Github](https://newruntime.com/topics/github.md): Explore the github topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)