Overview
Agent Settings give you fine-grained control over Workshop’s behavior. Access them by clicking the wrench icon in the interface. These settings affect how Workshop operates during conversations and can be adjusted at any time.Custom instructions
Custom Instructions set consistent guidelines that Workshop follows across all your conversations. They act as extensions to Workshop’s system prompt, reflecting your personal preferences and requirements.What they do
Custom Instructions ensure Workshop behaves consistently without you repeating the same guidance in every conversation. They apply globally across all projects in both Workshop Cloud and Workshop Desktop.Examples
Best practices
- Be specific but not restrictive.
"Include proper error handling in APIs"is good."Only use Express 4.18.2 with these exact middleware packages"is too rigid. - Focus on consistent preferences. Instructions that apply across conversations work best — project-specific rules belong in
.memex/rules.md. - Match your skill level. Beginners:
"Explain technical concepts in simple terms and provide step-by-step instructions."Advanced:"Focus on efficiency and assume familiarity with development tools."
How to set them
- Click the wrench icon to open settings
- Navigate to the Custom Instructions section
- Enter your guidelines in the text area
- Click Save to apply across all future conversations
Model selector
Choose which AI model powers your conversations, balancing speed, capability, and cost.Workshop currently uses the Claude model family to power all tiers. The specific models behind each tier are upgraded over time to always use the best available fit.
Available tiers
| Tier | Model | Best for | Credit cost |
|---|---|---|---|
| Fast | Claude Haiku | Quick tasks, simple questions, rapid iteration | $ |
| Balanced | Claude Sonnet | Most everyday development work | $$ |
| Genius | Claude Opus | Complex problems requiring deep reasoning | $$$ |
Switching models
The model selector appears as a chip in the message input toolbar (CPU icon with the model name). Click it to open the dropdown and select a different tier. You can switch models at any time during a conversation. A common pattern:- Fast for initial exploration and brainstorming
- Balanced for building features and standard development
- Genius for complex architectural decisions or challenging bugs
- Fast for quick follow-up questions
Code execution control
Control when Workshop executes code on your system.- Automatic (default)
- Manual approval
Workshop executes code blocks automatically without asking. This is the fastest workflow and is recommended once you’re comfortable with Workshop’s behavior.
Max turns
Limit how many autonomous actions Workshop takes before stopping for your input.How it works
By default, Workshop continues working autonomously until it completes your request. When Max Turns is enabled, Workshop stops after the specified number of turns and waits for your guidance.- Toggle Max Turns On or Off with the switch
- When enabled, use the slider to set the limit: 1 to 25 turns
- The counter resets when you send a new message
Recommended settings
| Use case | Turns | Why |
|---|---|---|
| Learning / reviewing | 1–3 | See each step of the implementation |
| Moderate oversight | 5–10 | Regular check-ins without micromanagement |
| Full automation (default) | Off | Let Workshop complete tasks without interruption |
Thinking mode
Enable extended reasoning for better problem-solving and transparency.How it works
When enabled, Workshop works through problems step-by-step before jumping to solutions, showing its reasoning process. This includes problem analysis, consideration of different approaches, and reasoning behind technical decisions. Toggle Thinking On or Off with the switch. When enabled, select a Thinking Level with the slider:| Level | Label | Description |
|---|---|---|
| 1 | Light | Simple problem breakdown, quick decision explanations |
| 2 | Balanced (default) | Thorough analysis, multiple approaches considered |
| 3 | Deep | Comprehensive exploration, detailed trade-off analysis |
| 4 | Max | Extensive reasoning, multiple solution paths explored |
Why use thinking mode
- Better outcomes: Structured reasoning leads to more thoughtful solutions
- Learning opportunity: See how expert-level thinking approaches technical problems
- Quality assurance: Transparent reasoning helps you evaluate the approach before implementation
- Debugging aid: Reasoning traces help identify where issues occurred
For complex problems, pairing Genius model with Thinking Level 3–4 produces exceptional results, though at higher credit cost.
Long Context Mode
Extend the context window from the standard 200k tokens to 1M tokens for longer conversations and larger projects.When to enable
- Working on large projects with extensive codebases
- Planning extended development sessions
- Projects that require maintaining detailed context across many turns
Local model setup (Desktop only)
Connect Workshop Desktop to a local Anthropic Messages API-compatible server, such as llama.cpp or Ollama with an adapter.Set model name (optional)
Enter a display name for the model (e.g.,
qwen3-coder-30b). This is for your reference only.For a full guide on setting up and using local models, see Local Models.
Task Management (Beta)
An experimental feature that enables Workshop to create and maintain structured task lists when implementing project plans. When enabled, Workshop automatically breaks down plans into discrete, trackable tasks.Quick reference by experience level
Beginners
Beginners
- Custom Instructions:
"Explain technical concepts clearly and provide step-by-step guidance" - Code Execution: Manual approval for learning
- Max Turns: 3–5 for oversight
- Thinking Mode: Level 2 for educational benefit
Experienced developers
Experienced developers
- Custom Instructions: Focus on tech stack preferences and coding standards
- Code Execution: Automatic for speed
- Max Turns: 10+ or off
- Thinking Mode: Level 3–4 for complex problems only
Team projects
Team projects
- Custom Instructions: Include team coding standards and review practices
- Code Execution: Manual for shared environments
- Max Turns: 5–7 for reviewable progress
- Long Context: Enabled for project continuity