Knowledge Mode - Instant Toggle

Instantly switch between Development Mode 🔧 (code-focused) and Knowledge Work Mode 🎓 (research, strategy, UX).

What's New in v7.2.1

✅ Instant switching - No loading delays, optimized for speed ✅ Clearer output - Scannable status designed for Claude Code chat ✅ Error-free - Fixed config update issues ✅ Persistent - Settings automatically saved

Current Status

Checking your current mode...

${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh knowledge-mode

Usage in Claude Code

Just run the command in your conversation:

/claude-octopus:knowledge-mode on
/claude-octopus:knowledge-mode off
/claude-octopus:knowledge-mode

Or even simpler - just tell me!

• "Switch to knowledge mode"
• "Enable research mode"
• "Back to development mode"
• "What mode am I in?"

I'll automatically detect and switch for you! ✨

Quick Toggle

Run this command to toggle modes:

${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh knowledge-toggle

Or specify explicitly:

Enable Knowledge Mode:

${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh knowledge-mode on

Disable Knowledge Mode:

${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh knowledge-mode off

Check Current Status:

${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh knowledge-mode status

What Changes When You Toggle?

Development Mode (Default) 🔧

When OFF, claude-octopus optimizes for software engineering:

• "Review this" → Code review
• "Analyze this" → Technical analysis
• "Research X" → Technical research
• Primary agents: codex, gemini, code-reviewer
• Workflows: embrace, probe, tangle, optimize

Knowledge Work Mode 🎓

When ON, claude-octopus optimizes for research and strategy:

• "Review this" → Document/strategy review
• "Analyze this" → Market/user analysis
• "Research X" → Academic/market research
• Primary agents: ux-researcher, strategy-analyst, research-synthesizer
• Workflows: empathize, advise, synthesize

Current Status (v7.2.1)

After toggling, you'll see a clearer, more scannable output:

Knowledge Mode Enabled:

  🎓 Knowledge Work Mode ENABLED

  Optimized for: Research, UX analysis, strategy
  Workflows: empathize, advise, synthesize

  Switch back: /claude-octopus:km off

Development Mode Active:

  🔧 Development Mode ACTIVE

  Optimized for: Code development, technical tasks
  Workflows: embrace, probe, tangle, ink

  Switch to research: /claude-octopus:km on

The new output is:

• 50% shorter - Less scrolling in chat
• More scannable - Key info stands out
• Actionable - Clear next steps shown

Usage Examples

Enable for Research Session

/claude-octopus:knowledge-mode on

Then work naturally:

• "Synthesize these 10 research papers on AI safety"
• "Analyze our market positioning vs competitors"
• "Review user interview transcripts and create personas"

Quick Status Check

/claude-octopus:knowledge-mode

(No argument = shows current status)

Return to Development

/claude-octopus:knowledge-mode off

Then resume coding:

• "Build an authentication system"
• "Review this PR for security issues"
• "Optimize database queries"

Keyboard Shortcut

You can also use the shorter command:

/claude-octopus:km on
/claude-octopus:km off
/claude-octopus:km

Persistent Across Sessions

The mode setting is saved to ~/.claude-octopus/.user-config and persists across terminal sessions. You only need to toggle once, and it stays that way until you change it.

Pro Tips

1. Task-specific toggle: Turn on knowledge mode for research sprint, then turn off for implementation sprint
2. Check before big tasks: Run /claude-octopus:knowledge-mode to confirm you're in the right mode
3. Use with auto command: The mode only affects auto routing - direct commands (empathize, embrace) work regardless of mode

Related Commands

• /claude-octopus:setup - Initial configuration
• /claude-octopus:check-updates - Check compatibility
• See available workflows: ${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh help --full

Troubleshooting

Mode not persisting? Check that ~/.claude-octopus/.user-config is writable:

ls -la ~/.claude-octopus/.user-config

Want to see what mode does? Run with dry-run to see routing differences:

${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh auto "review this document" --dry-run