Agent Settings
Access Agent Settings by clicking the wrench icon in the interface. These affect how Workshop operates during conversations.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.- 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
.workshop/rules.md. - Match your skill level. Beginners:
"Explain technical concepts in simple terms."Advanced:"Focus on efficiency and assume familiarity with development tools."
Model selector
Choose which AI model powers your conversations. The model selector appears as a chip in the message input toolbar.| Tier | Best for | Credit cost |
|---|---|---|
| Fast | Quick tasks, simple questions, rapid iteration | $ |
| Balanced | Most everyday development work | $$ |
| Genius | Complex problems requiring deep reasoning | $$$ |
Code execution control
Control when Workshop executes code on your system.- Automatic (default)
- Manual approval
Workshop executes code blocks automatically without asking. Recommended once you’re comfortable with Workshop’s behavior.
Max turns
Limit how many autonomous actions Workshop takes before stopping for your input. By default, Workshop continues working until it completes your request. When enabled, use the slider to set a limit from 1 to 25 turns.| 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
When enabled, Workshop works through problems step-by-step before jumping to solutions, showing its reasoning process.| Level | Label | Description |
|---|---|---|
| 1 | Light | Simple problem breakdown, quick decision explanations |
| 2 | Balanced | Thorough analysis, multiple approaches considered |
| 3 | Deep | Comprehensive exploration, detailed trade-off analysis |
| 4 | Max | Extensive reasoning, multiple solution paths explored |
For complex problems, pairing Genius model with Thinking Level 3–4 produces exceptional results, though at higher credit cost.
Long Context Mode
Extends the context window from the standard 200k tokens to 1M tokens for longer conversations and larger projects.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
App Settings
Access App Settings through the main Settings menu (gear icon). These apply across all projects and conversations.Secrets management
Secrets are sensitive values like API keys, database passwords, or access tokens that your applications need. Workshop provides a built-in system to store and use them securely. How secrets work:- Secure storage: Workshop uses your operating system’s native keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service) to store values. Raw values are never stored in Workshop’s own files.
- Local access: Secrets remain on your machine and are only accessed when needed by processes Workshop initiates on your behalf.
- Key tracking: Workshop maintains a list of secret names you’ve stored, but actual values are encrypted and managed by your system’s secure storage.
Add a secret
Enter a descriptive key name (e.g.,
OPENAI_API_KEY, DATABASE_PASSWORD), enter the value, and click Add Secret.- Case insensitive: Workshop finds secrets regardless of case —
OPENAI_API_KEY,openai_api_key, andOpenAI_API_Keyall work. - Permission prompts: The first time Workshop accesses a secret, your OS may ask for permission. You can approve permanently or per-session.
- Scope: Secrets are available to all projects within Workshop on that machine.
MCP servers (Desktop only)
The Model Context Protocol is a standard for connecting AI models to tools, data sources, and services. Workshop supports both using and building MCP servers. Managing MCP servers: Go to Settings (gear icon) > MCP tab to browse three sections:| Section | Description |
|---|---|
| Configured Servers | View, enable/disable, and manage your installed MCP servers |
| Server Directory | Browse and install curated, Workshop-tested servers (Neon, Netlify, GitHub, Context7, and more) |
| Add Custom Server | Install any MCP server from the broader ecosystem via GitHub URL or local path |
- Only enable servers you’re actively using to reduce context overhead
- Test new servers in non-critical projects first
- Use Secrets for server authentication credentials
- Disable unused tools within servers to keep context focused
Control Center
The Control Center provides quick-action buttons for common development tasks, accessible from within your project. Version control — Initialize Git, make commits, and manage your repository with single clicks. Workshop often handles this automatically during development; the Control Center lets you trigger it at specific moments. Application management — Start, stop, and monitor your applications. Workshop analyzes your project structure and creates custom startup scripts, handling environment activation, dependency loading, and complex startup sequences. Documentation generation — Generate or improve your project’sREADME.md from the current project structure with one click.
Interactive Terminal — Workshop handles command-line tools that require interactive input — scaffolding wizards, interactive installers, deployment setup. Terminal sessions are visible in the Control Center.