u/Solid-Industry-1564

Starting June 15, Anthropic is splitting Agent SDK usage into its own monthly credit pool, separate from your normal subscription limits. Caps are per-user and non-rolling:

• Pro: $20/mo
• Max 5x: $100/mo
• Max 20x: $200/mo

Those credits drain first. Once they're gone, you either pay API rates (if extra usage is enabled) or wait for the next cycle.

The tools hit hardest are the ones built on top of the Agent SDK: Zed, Conductor, T3 Code, superset, and the GitHub Actions integrations. Theo Browne reported roughly a 40x reduction in effective subscription value.

The workaround (surfaced by Zed): Anthropic's official `claude` CLI in a real terminal still pulls from your regular Pro/Max subscription, not the new SDK pool. So you have two options:

1. Drop back to the raw terminal. Cheapest, but you lose the things SDK-based tools gave you: a board, parallel sessions across worktrees, automations, status visibility, Linear/GitHub bridges, etc.
2. Use a tool that drives the official CLI natively in a pseudo-terminal. From Anthropic's side every session looks like a person typing into a terminal, so it stays on subscription pricing, but you keep the orchestration layer on top.

Lanes.sh (disclaimer: I built it) is in that second bucket: it's a Claude Code CLI orchestrator with a board, worktrees, parallel sessions, and Linear/GitHub bridges, and each session is a native pty running the real `claude` binary. Because it never touches the Agent SDK, the June 15 change has zero effect on it, and the same will be true for whatever pricing change comes next. The same logic applies to anything you roll yourself on top of the CLI.

Full breakdown with sources: https://lanes.sh/blog/claude-billing-split

I guess like everyone here, over the last period, I have been going all in with Claude Code CLI and also Codex CLI.

Also, I care a lot about shipping fast. I used to plan quarterly, then monthly, now it's weekly, and I want to get to intra-daily.

However, while working on larger projects and running multiple sessions in parallel, I started to feel that I was getting overwhelmed, kept loosing track and sometimes different agents were working against each other. I tried to use worktrees but again I kept loosing overview cause I was trying to do too many different things at the same time.

I decided therefore to do something about it and considered building a solution for it. This is how I came to the idea of Lanes:

----

👉 https://lanes.sh

brew install --cask lanes-sh/lanes/lanes && open -a Lanes

----

Its described as a workspace to run multiple AI coding sessions in parallel while keeping a clear overview and staying in control.

I would appreciate your honest feedback, give it a try or comment below if you had the same problem and how you have been solving it.

• Does this resonate with you?
• How are you managing multiple sessions today?
• Why or why not would you be interested in trying something like this?

Thanks!

Hi all,

I just wanted to share a new release from Lanes, and a workflow that it has enabled: running Claude sessions on issues from Linear.

The setup is two MCP servers in the same Claude Code session:

• Linear's official MCP — hosted by Linear at https://mcp.linear.app/mcp, OAuth, nothing to install. Gives you the full ticket/project/comment surface.
• Lanes' local MCP — runs on localhost:5353, served by the Lanes desktop app. Exposes your local board: issues, sessions, terminal scrollback, git changes per worktree, start/stop controls.

Adding Linear is one command:

claude mcp add --transport http linear <https://mcp.linear.app/mcp>

For Lanes you toggle Local MCP on in Settings and click Connect for Claude Code (it writes the entry to ~/.claude.json for you).

Once both are connected, the workflow is just prompts. Some that have actually been useful:

>"Pull all my open Linear issues with the frontend label and create matching issues in Lanes tagged with the same label."

>"Find the Lanes issue for ENG-742 and start a Claude Code session in plan mode with a fresh worktree."

>"Summarize the work done on ENG-742, post it as a comment on the Linear issue, and move it to In Review."

The agent resolves the session in an isolated environment, and when you close the loop, it pulls the session history, token stats, and Git diff from Lanes to compose the Linear comment.

Once you are done, you can ask the agent to return the result to Linear, giving you a clear overview of what has been completed and what remains.

Have you encountered similar workflows? Would love to hear more.