Copilot Modes
Understanding the AI copilot modes in NUXA Flow
Copilot Modes
NUXA Flow's AI copilot adapts its behavior based on context and user intent. Different modes provide different capabilities and tools.
Mode Overview
| Mode | Context | Purpose | Tools Available |
|---|---|---|---|
| Chat | Workspace | Quick Q&A and search | Search, basic queries |
| Explore | Workspace | Deep analysis | Code execution, API calls, artifacts |
| Guide | Workflow | Learning assistance | Read-only workflow analysis |
| Studio | Workflow | Building workflows | Full editing capabilities |
| Agent | Deployed | Customer-facing | Configured per deployment |
Workspace Modes
Chat Mode (workspace-chat)
The default mode for quick interactions in the workspace.
Best For:
- Quick questions about your workflows
- Searching for templates
- Finding specific blocks or features
- Getting help with syntax
Capabilities:
- Search across workflows and templates
- Query knowledge base
- Explain workflow concepts
- Suggest best practices
Example Prompts:
"Find all workflows using the Slack block"
"How do I use variables in conditions?"
"What templates are available for email automation?"Explore Mode (workspace-explore)
Deep analysis mode with extended capabilities.
Best For:
- Complex data analysis
- Generating reports
- Exploring API responses
- Creating artifacts (images, code, documents)
Capabilities:
- Execute JavaScript/Python code
- Make API calls
- Generate visualizations
- Create downloadable artifacts
- Analyze large datasets
Example Prompts:
"Analyze my workflow execution logs from the past week"
"Generate a report of all API errors"
"Create a visualization of my workflow usage patterns"Workflow Modes
Guide Mode (workflow-guide)
Learning-focused mode for understanding workflows.
Best For:
- Learning how a workflow works
- Getting recommendations
- Understanding block connections
- Debugging issues
Capabilities:
- Read workflow structure
- Explain block configurations
- Suggest improvements
- Identify potential issues
Example Prompts:
"Explain what this workflow does"
"Why might this condition be failing?"
"What's the best way to handle errors here?"Studio Mode (workflow-studio)
Full workflow building mode with all editing tools.
Best For:
- Building new workflows
- Modifying existing workflows
- Adding and configuring blocks
- Setting up integrations
Capabilities:
- Add, remove, and configure blocks
- Create connections between blocks
- Set up variables and conditions
- Test workflow execution
- Configure triggers
Example Prompts:
"Add a Slack notification at the end of this workflow"
"Create a condition to check if the user is premium"
"Set up a schedule to run this daily at 9 AM"Agent Runtime Mode
Agent Mode (agent)
Mode for deployed agents serving end customers.
Best For:
- Production agent deployments
- Customer-facing interactions
- Tool execution within defined boundaries
Capabilities:
- Configured tools per deployment
- Conversation memory
- Knowledge base access
- Custom guardrails
Configuration Options:
- Available tools
- System prompt
- Memory settings
- Rate limits
- Response formatting
Mode Switching
Automatic Mode Selection
The copilot automatically selects the appropriate mode based on:
- Current context: Workspace vs. workflow editor
- User intent: Questions vs. building requests
- Available permissions: What the user can access
Manual Mode Override
Users can explicitly request a mode change:
"Switch to explore mode"
"I want to build - use studio mode"
"Just help me understand this - guide mode"Mode Capabilities Matrix
| Capability | Chat | Explore | Guide | Studio | Agent |
|---|---|---|---|---|---|
| Search | β | β | β | β | βͺ |
| Knowledge Base | β | β | β | β | β |
| Code Execution | β | β | β | β | βͺ |
| API Calls | β | β | β | β | βͺ |
| Artifacts | β | β | β | β | βͺ |
| Read Workflow | β | β | β | β | βͺ |
| Edit Workflow | β | β | β | β | β |
| Add Blocks | β | β | β | β | β |
| Test Workflow | β | β | β | β | β |
| Custom Tools | β | β | β | β | β |
Legend: β Available | β Not Available | βͺ Configurable
Best Practices
Choosing the Right Mode
- Start with Chat for quick questions
- Use Explore when you need data analysis or reports
- Use Guide when learning or debugging
- Use Studio when actively building
Mode-Specific Tips
Chat Mode:
- Keep questions focused and specific
- Use natural language
- Reference specific workflows by name
Explore Mode:
- Describe your analysis goals clearly
- Request specific output formats
- Ask for explanations of results
Guide Mode:
- Ask "why" questions to understand logic
- Request step-by-step explanations
- Ask about best practices
Studio Mode:
- Describe your automation goal clearly
- Specify integrations you want to use
- Mention any constraints or requirements
Legacy Mode Mapping
For backwards compatibility with older integrations:
| Legacy Mode | + Workspace | + Workflow |
|---|---|---|
ask | Chat | Guide |
build | Explore | Studio |
agent | Agent | Agent |