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
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.
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.
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.
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.
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.
I wouldn't trust Zoho. More than 10 years ago, they shadowbanned (can not be shared or publicly viewed) my documents because it criticized Chinese communist party.
I'm building a information hub that utilize AI agents to compile all the relevant information from China (gov, econ, commerce, anything and everything). I call it "information domination". Heard many times that language barrier stops people having a better understanding of China. Now the LLM translation is good enough, and AI agents can do way more in information gathering stage. It's time to put things in practice.
For now, it only has a daily newsletter fully compiled by AI agents without any human intervention. I plan to add public listed companies (semiconductor, energy provider, etc) onto the platform. Already found lots of good data points that can be used by analysts, researchers or observers.
Looks really interesting, I'll have a proper read. What would be your reasoning to incorporate this if we already have vector functionality and semantic search?
Only public on iOS store for now, due to Google requires larger # of testers to authenticate the app.
This app idea came from my last Japan trip. I had a hard time finding good local restaurants (not tourist traps). So I decided to build this app with Japanese-oriented lists, due to lists' lacked of maps, etc. The app actually helped me discover some great spots, since it lists places all over Japan. Please give it a try and let me know if you have any feature requests or ideas.
China's land area is approximately 25 times of Japan, def has a bigger network. But the top speed is comparable in current generations[1] except the Maglev.
I would think that the vast amount of central/Western land in China that is sparsely populated might skew this statistic quite a bit, where Spain and Japan don't have that at the same scale.
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.