Work with files
Read, search, create, edit, and patch selected workspace files when file tools are installed and allowed.
AI agent package family for Sunder
Sunder Agent runs inside Sunder App. Add the model providers and tool packages you choose, then let the agent read selected files, edit projects, run commands, search the web, call MCP tools, remember context, delegate to subagents, use local models, or build Sunder packages with Agent Builder.
Practical tools
Agent starts as chat, but the useful part is the tool layer you decide to install around it.
Read, search, create, edit, and patch selected workspace files when file tools are installed and allowed.
Use shell tools with a selected execution target for builds, scripts, tests, imports, exports, and local workflows.
Search the web or fetch pages as markdown, text, or HTML for grounded project work.
Connect local or remote MCP servers so Agent can call external tools and services.
Recall project notes, preferences, standing instructions, and facts that matter across sessions.
Use specialist subagents for focused tasks while the main agent coordinates the work.
Run workflows against LM Studio models when you want a local model surface.
Use Agent Builder to create, edit, build, and test Sunder packages from inside the app.
Agent Builder
Agent Builder is the crucial non-manual path: create a new Sunder package inside Sunder, then ask Agent Chat to build it. The agent can generate files, edit code, run commands, test builds, inspect errors, and keep iterating without you starting from a blank desktop app setup.
Install flow
Agent is modular because local tool access should be explicit. Start with the core package, add a model provider, then add file, shell, web, MCP, memory, execution, or Builder packages as needed.
Install the desktop app where Agent runs.
Add sunder.package.agent from the Registry.
Use OpenAI, Anthropic, Gemini, LM Studio, or future providers.
Allow files, shell, web, MCP, memory, subagents, execution, or Builder only when you need them.
Ask questions, edit projects, run tasks, use tools, or build a new Sunder package.
sunder install sunder.package.agentPlain answers
Short definitions for people comparing chatbots, coding agents, local agents, MCP tools, and package builders.
Sunder Agent is a first-party package family that adds AI chat sessions, model providers, file tools, shell tools, web tools, MCP, memory, subagents, execution targets, and Agent Builder to Sunder App.
Install Sunder App, open the public Registry, then install the Agent core package. Add only the model provider, tool, workflow, execution, or Builder packages you need.
sunder install sunder.package.agentYes. The LM Studio provider connects Sunder Agent to local OpenAI-compatible LM Studio endpoints and discovers available local models.
Agent tool packages can add file read/write/edit/apply_patch, grep, glob, shell execution, web search, URL fetch, MCP server tools, local execution, Docker-backed execution, and package-building workflows.
Yes. Sunder Agent Builder lets Agent help create, edit, build, test, and iterate on Sunder package projects from inside Sunder App.
Sunder.Package.Agent.Contracts is a NuGet contracts package used by Agent extensions. It is not itself a Sunder runtime package.
Product proof
Agent profiles, sessions, tools, package panels, and workspace context live inside Sunder App. The screenshot shows Agent installed as a Sunder package, alongside package panels and chat.
Package map
Agent is a package family. The core handles profiles and sessions; separate packages add models, files, shell, web, MCP, memory, subagents, execution, and Builder.
sunder.package.agent
Adds AI chat sessions, profiles, permissions, and tool orchestration inside Sunder.
sunder.package.agent.provider.openai
Lets Agent use OpenAI chat, embeddings, streaming, images, PDFs, and tool calls.
sunder.package.agent.provider.anthropic
Lets Agent use Claude models with streaming, images, PDFs, and tool use.
sunder.package.agent.provider.gemini
Lets Agent use Gemini chat, embeddings, and multimodal input.
sunder.package.agent.provider.lmstudio
Connects Agent to local models served by LM Studio.
sunder.package.agent.tools.files
Lets Agent read, search, create, edit, and patch selected workspace files.
sunder.package.agent.tools.shell
Lets Agent run approved non-interactive commands through a selected execution target.
sunder.package.agent.tools.web
Lets Agent search the web and fetch pages as markdown, text, or HTML.
sunder.package.agent.mcp
Connects Agent profiles to tools exposed by local or remote MCP servers.
sunder.package.agent.skills
Adds reusable instructions and workflows from local paths or GitHub URLs.
sunder.package.agent.subagents
Lets a main agent delegate focused work to specialist child agents.
sunder.package.agent.memory.semantic
Helps Agent recall relevant notes, preferences, project facts, and standing instructions.
sunder.package.agent.execution.local
Runs file and shell tools on the local machine when you allow it.
sunder.package.agent.execution.docker
Runs workspace tasks inside Docker-backed execution targets.
sunder.package.agent.builder
Lets Agent help create, edit, build, and test Sunder packages from inside Sunder.
Model providers
Use hosted models, local models, or a mix depending on the task and your setup.
Use OpenAI models for chat, embeddings, streaming, image/PDF input, and tool calling.
Use Claude models for chat, streaming, image/PDF input, and tool use.
Use Gemini for chat, embeddings, and image, PDF, audio, or video input.
Use local models through LM Studio and discover available local models from Sunder.
Use cases
Sunder Agent is strongest when the model can use installed tools: files, commands, web pages, MCP servers, local models, memory, subagents, execution targets, and Builder.
Safety model
Agent does not need every local capability by default. You decide which provider, file, shell, web, MCP, execution, memory, subagent, or Builder surfaces are installed and configured.
Start modular
Install from the Sunder Registry or use the CLI.
Backed by

No. Sunder Agent is a package family installed into Sunder App.
No. Install the Agent core, then add only the providers and tools you want: files, shell, web, MCP, memory, subagents, local execution, Docker execution, or Builder.
Yes. With Sunder Agent Builder, Agent can help create, edit, build, and test Sunder package projects from inside Sunder App.
Yes. The LM Studio provider connects to a local OpenAI-compatible endpoint and lists local models.
Yes. The MCP extension supports configured MCP servers and exposes MCP tools through Agent profiles.
Only through installed tool packages and configured access. File tools, shell tools, web tools, MCP, and execution targets are separate capabilities you choose to add.