Blog
/Product

What's New in Lanes v0.50: Custom Statuses, New Models, and Lanes Link Updates

Lanes v0.50 is here, and this release brings something many of you have asked for: custom board statuses.

Until now, every Lanes board had the same six columns. You can finally change that and set up your board the way you actually work.

We've also added support for the latest Claude and Codex models, made the desktop app more reliable when running multiple agents, and released a major update to Lanes Link.

Here's what's changed since v0.49.

1. Make the board yours with custom statuses

Everyone works a little differently. Some people use a simple backlog and done workflow. Others want separate stages for planning, development, testing, and review.

You can now customize your board to match your workflow.

Head to Settings → Workflows → Statuses to:

  • Rename existing statuses
  • Create your own statuses
  • Choose a color for each status
  • Reorder statuses within their category
  • Disable statuses you don't use

The original six statuses (Backlog, Planning, Implementation, Review, Misc, and Done) are still there by default. But you're no longer stuck with them.

How statuses work

Each status belongs to one of three categories: Not started, In progress, or Done.

These categories help Lanes understand what should happen when you move an issue.

For example, a status called Ready in the Not started category lets you launch work using the Start action. A status called Shipped in the Done category behaves just like the original Done status.

Your agents also see your custom statuses through the MCP tools, so they can use the same workflow as you.

You can disable any of the original statuses, although each category must have at least one active status.

More control over running sessions

Previously, moving an issue to Done automatically stopped its running sessions.

That's still the default, but you can now change it.

If you disable Stop sessions on Done, you can mark an issue as complete without interrupting an agent that's still running. Its session, tab, and worktree stay available.

This also means a teammate's running session won't prevent you from completing an issue.

2. The latest Claude and Codex models

We've updated the model selection for both Claude and Codex.

Claude: choose a model family or a specific version

You can now select a Claude model using a simple alias:

  • opus
  • sonnet
  • haiku
  • fable

These aliases automatically use the latest available model in that family on your account.

For example, selecting opus means you won't need another Lanes update just to use the next Opus model.

If you'd rather stick to a particular version, you can still select it directly.

The current list includes:

  • claude-opus-5-5
  • claude-sonnet-5-5
  • claude-fable-5-2
  • claude-haiku-5-5
  • claude-opus-5

Codex: models from your installed CLI

Codex now gets its available models directly from your installed Codex CLI, so the list stays in sync with what you have installed.

We've also updated the fallback list with gpt-6-astra, gpt-6.1-sol, gpt-6.1-terra, and gpt-6-luna.

You can still select Default to let the CLI decide, or Custom value to enter any model identifier manually.

3. Lanes Link: fewer tools, same capabilities

We've also shipped a major update to Lanes Link, our self hosted endpoint that gives agents access to your connected accounts, memory, tasks, and other resources.

One of the biggest improvements is how agents discover and use tools.

A much smaller tool list

When you connect several accounts to Lanes Link, the number of available tools can grow quickly. That means your agent can spend a significant part of its context window just reading tool descriptions.

We've introduced a new option called surface: crunched that makes this much more manageable.

Here's what changed on an endpoint with two profiles:

BeforeWith crunched
Exposed tools27828
Context usage~180,000 tokens~8,000 tokens

That's roughly 95% less context used for tool descriptions, without losing access to any capabilities or changing permissions.

We've also rebuilt the tool search behind it, making it easier for agents to find what they need.

Easier account and access management

We've simplified how connections and access profiles work.

Previously, connections were managed separately for each profile. Now, you authorize an account once at the workspace level and decide which profiles can access it.

You can also set permissions for individual connections. For example, two email accounts in the same profile can have different access rules.

Profiles now also specify which people are allowed to use them.

Other improvements in Lanes Link 0.17

This update includes several smaller fixes that make everyday use more reliable:

  • Email replies: Replies, drafts, and revisions now stay in the correct email conversation.
  • Fewer unnecessary permission prompts: Memory entries, tasks, and other records are returned as text rather than file attachments. Actual stored files still behave as files.
  • Clearer credential errors: If a credential store cannot be accessed, Lanes Link reports the problem instead of showing an empty store.
  • Dependency and security checks: Dependencies have been updated, and automated security checks now run correctly.

You don't need to change your existing setup to use version 0.17.

If you're already using Lanes Link, updating is the usual single command. If you're new, check out the quickstart guide.

4. A smoother desktop experience

We've also made several improvements to the Lanes desktop app, particularly for those running many agents at once.

More reliable updates

We've fixed an issue where an update could fail while Lanes continued showing a successful installation message.

Now, Lanes verifies that the installed version has actually changed before reporting success.

It can also repair an outdated Homebrew tap automatically, and installation logs are written as the update runs, making problems easier to diagnose.

Better performance with multiple agents

Running several agents at the same time should feel smoother now.

We've improved how Lanes handles session output and transcripts, reducing unnecessary processing.

We've also fixed an issue where stopping many sessions at once could temporarily freeze the app.

These changes are especially useful if you regularly run multiple Claude or Codex sessions in parallel.

Give custom statuses a try

If you're already using Lanes, start with the new board customization.

Open Settings → Workflows → Statuses, rename a few columns, or add the stages you've been missing.

And if you've come up with an interesting workflow, share it with us on Discord. We'd love to see how you're organizing your agents.

That's it for v0.50. Thanks for using Lanes!

Latest Posts