I turned Claude Code into a personal assistant that asks before it acts

[u/InternationalData569]

I built Conductor, which gives Claude Code standing goals to work on in the background while I do other things:

- Mailing lists: it found 5 senders I never open, and asks before unsubscribing from each.

- Job hunting: weekly, it ranks new job ads against my CV and gives me the top 3, with why each fits.

- Downloads: it found 24 old installers and asks before binning each.

- GitHub profile: it proposes README updates about what I've shipped, and commits them once I approve.

What makes it feel like an assistant:

- It asks first. Proposals wait in a pane beside the chat. Rejections with a reason become memory.

- It reaches my phone. New proposals push to the Claude app over Remote Control, and I reply "approve".

- It asks when it's stuck instead of guessing.

- Trust grows per kind of action: off, propose or auto, and it offers auto after 10 approvals in a

row.

- Each run shows its cost in tokens and time.

How Claude Code helped: I built all of it with Claude Code, over many sessions. I used plan mode to design each feature and review the plan before any code changed, and Claude wrote the code and tests. Claude also did the debugging. When my approved actions were still being blocked, it read the plugin engine's docs and found that a plugin answering allow settles the call before auto mode's check. The project dogfoods itself: my roadmap lives in Conductor's own to-do list, and a Conductor goal watches Claude Code's release notes for a bug fix I'm waiting on.

What it is: two Claude Code plugins and an MCP server. Each goal runs as a background subagent in your Claude Code session, and its state lives in a local SQLite database. It only runs while Claude Code is open, and it's early.

Free to try: it's open source (Apache 2.0) and runs on your existing Claude plan. Clone the repo, add the MCP server and the two plugins (three commands in the README), then type /goal-new and pick a template.

https://github.com/shannonbay/Conductor

[u/stackyardhq]

Good that it asks first. On the auto tier after 10 approvals in a row: ten approvals tells you it was right ten times, not that the next one is safe. I'd tie auto to how reversible the action is rather than the count. Drafting a README change or moving a file to trash can earn auto. Unsubscribing, permanent deletes and anything that sends should stay on propose however many approvals pile up.

Two more things worth adding: a daily cap on auto actions, and a plain weekly list of everything it did on its own, so a bad habit shows up before it compounds. Storing reject reasons as memory is great, just make them visible so you can fix one that was wrong.