What's New in v0.41: Many Sessions, One Issue | Blog | Lanes

v0.41 is about depth on a single issue: one ticket, as many agents as the work needs.

Multi-session runs them in parallel on the same worktree. Quick Actions joined the session selector, and Session Settings collects CLI, model, and effort in one place. Plus stability fixes across awaiting-input, token revocation, and project switching.

Many sessions on a single issue

Until now an issue meant one session. Opening a new agent on an issue that already had one took the existing one over. That fit the common case but fought you the moment the work outgrew a single conversation.

v0.41 drops that constraint. An issue can host as many sessions as you like, each with its own slot (session-1, session-2, ...) and an editable name. They share the issue's worktree branch but run independently. Start a new session from inside an existing one and Lanes treats it as a sibling on the same issue, no setup, no second ticket.

A few patterns this unlocks:

Plan, implement, review on the same ticket. The screenshots above show exactly that layout: one session drafts the approach, the next executes it, a third audits the diff. Each stage keeps its own history instead of collapsing into one giant transcript.

Two approaches, one comparison. Spawn a sibling to try a different prompt, a different model, or a different cut at the same problem. Pick the diff you like, drop the other.

Keep work organised. A long-running investigation in one session, scratch work in another. Nothing has to be rolled back or forgotten when you context-switch.

The point is that the issue stays the unit of work, and the sessions become the stages of it.

Quick Actions from the issue panel

The session selector now doubles as the launching point for Quick Actions. Whatever you've configured for this worktree, plus your general ones, appear under a Quick Actions group below the active sessions: test, commit, release, fix-lint, deploy scripts, anything the project asks for.

So the "run the tests on this branch" thought is the same shape as the "spawn a new session" thought. Both live in the same menu, both run on the same worktree, both stay attached to the issue you're already looking at. No terminal hop, no separate panel.

Pick model and effort upfront

When you start a new session, the picker now opens with a Session Settings flyout that puts CLI, Model, Effort, and Flags into one place. The pill at the top of the new-session view shows the current selection at a glance (e.g. Claude Code / claude-opus-4-7 / max), and one click on it opens the rest.

Before this, you'd start a session and only reach for model or effort once it was already running, sometimes mid-prompt. Now the choice is part of starting the session, so the agent runs with the right settings from the first message instead of being reconfigured halfway through.

Other improvements

Editable session names so slots can read as plan, implement, review instead of session-1, 2, 3.

Worktree creation from Quick Actions so you can scaffold a fresh worktree the same place you launch a session.

Welcome screen polish for a cleaner first-run, with quick paths into folder access, adding a project, starting a CLI session, or opening a terminal.

Git diff and issue panel got UI passes for spacing, hover states, and density.

Sidebar on hover so the project list expands when your cursor lands and tucks away when it doesn't.

Stability and bug fixes

v0.40 dialed in worktrees and session state, v0.41 keeps the pressure on.

Awaiting-input flicker is gone. Action-floor gates on the status file and title-idle markers, with a 5-second floor, so the orange bell stops false-triggering on continuous title updates.

Linear and GitHub reconnect UI. When a Linear refresh token or GitHub PAT gets revoked, the integration surfaces a one-click reconnect instead of failing silently.

Project switching cleans state. Switching projects in the issue side panel no longer leaves a stale branch, stale diff, or stale PR fetch from the previous project.

No PR-fetch toast on non-git folders. The error toast on non-repo working folders is suppressed.

Multi-session tests caught up to the new schema, with peer-lock detection, fallback session state, and a tighter, simpler session state model behind the scenes.

Session sort, terminal bell flicker, session-history and git-diff view, project right-click scoping, and a handful of MCP session fixes round out the patch run.

We'd love your feedback. Join our Discord to stay updated.

Latest Posts

May 18, 2026<br>What's New in v0.40: Lanes Meets Your Stack<br>Bring Linear issues into Lanes with one click. Open the working folder in your editor of choice. A cleaner side panel for working folder and changes, with stability fixes across sessions and worktrees.

May 15, 2026<br>Anthropic just split the bill. Lanes did not have to change.<br>On June 15, Claude subscriptions stop covering programmatic agent usage. Lanes runs the...