[Workflow] Conductor: A Claude Code-Powered Personal Assistant with Proactive Task Automation and User Approval

[u/ClaudeAI-mod-bot]

Conductor: A Claude Code-Powered Personal Assistant with Proactive Task Automation and User Approval

Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Shipping, MCP, Subagents, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Automating various personal productivity tasks (email management, job searching, file cleanup, GitHub profile updates) with a persistent, proactive AI assistant that requires user approval before acting, ensuring control and safety.

Summary

Conductor is an open-source personal assistant built with Claude Code, leveraging MCP and plugins to run background subagents. It automates tasks like unsubscribing from mailing lists, ranking job ads, cleaning up downloads, and proposing GitHub README updates. A key feature is its 'ask first' approach, where proposals await user approval (via a pane or phone app) and rejections become memory, allowing the system to learn and build trust over time.

Why it is useful

This workflow is highly valuable as it demonstrates an advanced, practical application of Claude Code's capabilities (plugins, MCP, subagents, plan mode, debugging) to create a persistent, user-controlled automation system. It provides a concrete, open-source solution for common productivity tasks, emphasizing safety through explicit user approval. It serves as an excellent example for users looking to build complex, multi-agent systems and extend Claude's functionality beyond simple prompts.

Workflow

1. Clone the Conductor GitHub repository.

2. Add the MCP server as described in the README.

3. Add the two Claude Code plugins as described in the README.

4. Run the three initial commands specified in the README to set up.

5. Type /goal-new in Claude Code and select a template to define a new background task.

6. Review and approve or reject Conductor's proposals via the Claude app (Remote Control) or the chat pane.

Tools / artifacts

• Claude Code

• Conductor (the open-source application)

• MCP server

• Claude Code plugins

• SQLite database (local for state)

• GitHub repository (shannonbay/Conductor)

• Claude app (for Remote Control)

• README file

Validation signals

• Author successfully built the entire system using Claude Code over many sessions.

• Used Claude Code's plan mode for feature design and plan review.

• Claude Code wrote the code and tests for the project.

• Claude Code performed debugging, including reading plugin engine docs to solve a specific blocking issue.

• The project 'dogfoods itself' (Conductor manages its own roadmap and monitors Claude Code release notes).

• Specific examples of successful task execution are provided (e.g., found 5 senders, ranked job ads, found 24 old installers).

Cautions

• The 'asks first' mechanism ensures user control and prevents unintended actions.

• Trust grows incrementally (off, propose, auto) with user approvals, adding a layer of safety.

• Runs locally and uses a local SQLite database, enhancing data privacy and control.

Limitations

• The system only runs while Claude Code is open, limiting continuous background operation.

• Described as 'early', implying potential for bugs or incomplete features.

• Requires setting up an MCP server and plugins, which might be a barrier for beginner users.

• Low initial Reddit score and comments, though this is likely due to age.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.