Documentation

switch_mode

Transition between specialized Sypha personas to align the AI's toolset with your current objective.

← All guides

Sypha functions through various specialized Modes, each optimized for a distinct phase of the development lifecycle. The switch_mode utility allows for seamless transitions between these personas as your project requirements evolve.

Parameters

  • mode_slug (required): The unique identifier for the target mode (e.g., strategist, developer, debug, chat).
  • reason (optional): A contextual explanation for why the mode transition is being initialized.

Operational Triggers

Sypha will typically suggest a persona shift when the nature of the task changes:

  • Strategist -> Developer: Transition occurs after a high-level technical plan is finalized and implementation is ready to begin.
  • Developer -> Debug: Triggered if execution logs indicate errors or if a test suite failure requires systematic investigation.
  • Chat -> Developer: Facilitated when a conceptual inquiry evolves into a request for a physical codebase modification.

Primary Personas

  • Developer: Grants comprehensive access to file editing, terminal execution, and implementation-focused utilities.
  • Strategist: Optimized for high-level system design, technical leadership, and markdown-based documentation.
  • Chat: A rapid, knowledge-retrieval mode designed for informational queries without altering project files.
  • Debug: Specifically engineered for analyzing stack traces, log files, and environmental issues to resolve technical blockers.

Every mode transition requires your explicit authorization. Once confirmed, Sypha's internal logic, behavioral personality, and available tools will update immediately.