code-agent — LM Studio Plugin

A context-light coding toolkit for LM Studio chat agents: eight focused tools, a mandatory user-defined working folder, and sub-agents that do smaller tasks in the background so the main chat stays light on context.

Working folder first — every file tool refuses to run until set_workspace pins a project folder (the one you define). All paths resolve inside it; traversal outside is blocked.
Light on context — reads are line-numbered and capped, search output is bounded, and bulky subtasks can be delegated to a subagent, which returns only a short summary.
Safe by default — there is no delete tool anywhere in the plugin (by design), and sub-agents have no shell access at all.

Requirements

LM Studio with plugins enabled (node runner)
A chat agent with this plugin attached
Node.js + npm only for development/publishing, not for use

Installation

Local / development mode

lms dev compiles src/index.ts, registers the plugin with LM Studio, and hot-reloads on changes. Enable code-agent for your chat agent in LM Studio's plugin settings. Stop it again with Ctrl+C when done.

From the Hub (after publishing)

Usage

Tell the agent your project folder — an absolute path, e.g. "My project is in D:\AI stuff\myapp, work there." The agent calls set_workspace first; all file tools error until that succeeds. The workspace persists across chats for the lifetime of the LM Studio process (re-set it after a restart or plugin reload).

Tool reference

Tool	Parameters	What it does
`set_workspace`	`path`	Set the project working folder (must exist). Must be called before any other tool.
`list_dir`	`path?` (default `.`)	List a directory; lines start with `D=` (folder) or `F=` (file), folders first.
`read_file`	`path`, `start?`, `lines?` (≤ 400)	Read part of a text file, line-numbered. Defaults to 100 lines; pass `start` to continue.
`write_file`	`path`, `content`	Create or overwrite a file; missing parent folders are created.
`edit_file`	`path`, `find`, `replace?`	Replace an exact, unique text match (error if it matches 0 or >1 times). Omit `replace` to delete the matched text.

Sub-agent limits (deliberate)

Only the five file tools: list_dir, read_file, search, write_file, .

Safety notes

All paths resolve under the working folder; absolute-path and .. escapes are rejected (case-insensitively on Windows).
Nothing in the plugin deletes files or folders — if a change requires deletion, do it yourself or ask for a run command you approve.
run executes arbitrary shell commands inside the workspace; that is the only unconfined surface and exists because builds/tests need it.

Development

Type-check and build to dist/: npm run build (tsc). Not needed for normal use — LM Studio compiles src/index.ts itself via esbuild when you run lms dev or install from the Hub.
tsconfig.json targets CommonJS/ES2021 into dist/.

Publishing to the Hub

Set "owner" in manifest.json to your LM Studio username (the one shown by lms whoami).

.gitignore keeps node_modules/, dist/ and .lmstudio/ out of the upload — that's intentional; installers compile src/ on their own machine at install time.

code-agent — LM Studio Plugin

Working folder first — every file tool refuses to run until set_workspace pins a project folder (the one you define). All paths resolve inside it; traversal outside is blocked.

Light on context — reads are line-numbered and capped, search output is bounded, and bulky subtasks can be delegated to a subagent, which returns only a short summary.

Safe by default — there is no delete tool anywhere in the plugin (by design), and sub-agents have no shell access at all.

Usage

Tell the agent your project folder — an absolute path, e.g. "My project is in D:\AI stuff\myapp, work there." The agent calls set_workspace first; all file tools error until that succeeds. The workspace persists across chats for the lifetime of the LM Studio process (re-set it after a restart or plugin reload).

Tool reference

Tool

Parameters

What it does

set_workspace

path

Set the project working folder (must exist). Must be called before any other tool.

list_dir

path? (default .)

List a directory; lines start with D= (folder) or F= (file), folders first.

read_file

path, start?, lines? (≤ 400)

Read part of a text file, line-numbered. Defaults to 100 lines; pass start to continue.

write_file

path, content

Create or overwrite a file; missing parent folders are created.

edit_file

path, find, replace?

Replace an exact, unique text match (error if it matches 0 or >1 times). Omit replace to delete the matched text.

Sub-agent limits (deliberate)

Only the five file tools: list_dir, read_file, search, write_file, .

Safety notes

All paths resolve under the working folder; absolute-path and .. escapes are rejected (case-insensitively on Windows).

Nothing in the plugin deletes files or folders — if a change requires deletion, do it yourself or ask for a run command you approve.

run executes arbitrary shell commands inside the workspace; that is the only unconfined surface and exists because builds/tests need it.