Local Code by Draw Things
How Local Code works
Reference pages for when you want the details: what a project keeps on disk, what each setting changes, what the agent can reach, and how to connect it to other tools.
Updated
Project files
A project is a folder. Put instructions and skills in it for the agent, and Local Code keeps the project's memory, threads and packages there too.
Agent settings
The Settings tab holds the choices that change how the agent thinks and works. They apply to every project, from your next message.
Machine settings
Machine Settings hold the choices about the device itself: how models use its memory, when it stays awake, and how the app looks.
Weights Streaming
Weights Streaming is the SSD streaming that lets DeepSeek and GLM run on a Mac with less memory than the model. It keeps the experts the model uses most in memory and reads the rest from the SSD.
Permissions
The agent works inside your workspace. Anything beyond it, from another folder to your calendar, needs a permission you can see and change in the app.
Browser
The agent can drive a real WebKit browser to test the pages it builds and to use sites that need a sign-in. You can watch any tab, take it over, and sign in yourself.
MCP servers
The agent talks to Model Context Protocol servers through MCPorter, a command-line MCP client it installs in your project. Ask for a server, and the agent sets it up, inspects its tools and calls them.
Serve
Turn on the Responses API, and apps on your Mac can send requests to the model Local Code runs, the same way they would call a cloud API.