I don't like claude code web due to its lack of planning mode. I found the result is often lackluster compare to claude code cli.

My current setup: Tailscale + Terminus(ipad) + home machine(code base)

Need to look into how to work on multiple features at the same time next.

▲

LatencyKills 3 days ago | parent | next [-]

I've been using git worktrees with Claude and it's pretty awesome:

https://www.youtube.com/watch?v=up91rbPEdVc

Pair worktrees with the ralph-wiggum plugin and I can have Claude work for hours without needing any input:

https://looking4offswitch.github.io/blog/2026/01/04/ralph-wi...

▲

scubbo 3 days ago | parent [-]

Worktrees took way too much setup and hand-holding for me, but https://conductor.build made it easy!

	▲	nikcub 3 days ago \| parent \| next [-]
		I delayed adopting conductor because I had my own worktree + pr wrappers around cc but I tried it over the holidays and wow. The combination of claude + codex + conductor + cc on the web and claude in github can be so insanely productive. I spend most of my time updating the memory files and reviewing code and just letting a ton of tasks run in parallel
	▲	behnamoh 3 days ago \| parent \| prev \| next [-]
		software is all about wrappers, isn't it? :) conductor -> multiple claude codes/codexes -> multiple agents -> multiple tools/skills/sub-agents -> LLMs
	▲	thelittleone 2 days ago \| parent \| prev [-]
		Sadly only allows sign up with Github.

▲

simonw 3 days ago | parent | prev | next [-]

I haven't missed planning mode myself. I tend to tell it "write a detailed plan first in a file called spec.md for me to review", then use that as the ongoing plan.

I like that it ends up in the repo as it means it survives compaction or lets me start a fresh session entirely.

	▲	s900mhz 3 days ago \| parent \| next [-]
		I was doing the same, but recently I noticed that Claude now writes its plans to a markdown file somewhere nested in the ~/.claude/plans directory. It will carry a reference to it through compaction. Basically mimicking my own workflow! This can be customized via a shell env variable that I cannot remember ATM. The downside (upside?) is that the plan will not end up in your repo. Which sometimes I want. I love the native plan mode though.
	▲	dbbk 2 days ago \| parent \| prev [-]
		Plans in plan mode also survive compaction

▲

dbbk 2 days ago | parent | prev | next [-]

The lack of Plan Mode is puzzling, I'm sure they must get to it at some point. But until then it CAN still plan, you just have to ask it to write a plan and not write code yet.

▲

eclipxe 3 days ago | parent | prev | next [-]

I've been really impressed with https://github.com/BloopAI/vibe-kanban to do this. Really really impressed.

▲

bakies 2 days ago | parent | prev | next [-]

Not sure if this works in claude code web, but running non-interactive claude code I can still get it to use plan mode by simply asking it. It's just a tool call.

▲

nobodywillobsrv 3 days ago | parent | prev [-]

Can you not use PAL MCP for this? Have one top agent as controller etc? It's not ideal but it feels like the space of multi agent stuff is evolving ... I notice that there are a lot of posts on hn about these things so we are trying to do the same thing really.