labd
Your Dev Labs lab assistant, in the editor.
labd reads the screen you are actually looking at — the open file, what you have
selected, and the errors the editor is reporting — and answers the way a good lab
demonstrator would: what is actually happening, what to change, and the concept
behind the fix. It is the same assistant that sits beside every page on
learn.thedevlabs.io and runs in your terminal as
labd, so it behaves the same in all three places — and what it remembers about
you is shared between them.
What it does
- Explain this file — what it is for, how it is put together, and what a
newcomer would trip over
- What's wrong here? — walks through the problems the editor is reporting:
what each one means, what caused it, and how to fix it
- How would you improve this? — on the whole file, or just what you selected
- Ask anything —
⌘⌥L (Ctrl+Alt+L) from anywhere
When the answer depends on code labd has not been shown, it reads it: other
files, directory listings, and a workspace search. All of that runs locally in
the editor, never on a server. It also sees your branch and recent commits, your
project's AGENTS.md or CLAUDE.md, and the names of any skills it defines.
Where the chat lives
labd's chat opens in the secondary side bar, the one on the right where
other chat assistants sit, so the primary side bar can stay on the Explorer.
labd's icon in the activity bar still opens it: the chat comes up on the right
and the Explorer comes back on the left. To keep labd in the primary side bar
instead, run labd: Move chat to the primary side bar (or set
labd.chatLocation to primary); labd: Move chat to the secondary side
bar puts it back. Both are also in the chat's ... menu. Moving the chat
stops anything it is still answering or running, so labd asks first when
something is. Editing labd.chatLocation by hand in Settings moves the chat
without asking.
labd needs VS Code 1.106 or later. An older VS Code stays on labd 1.21.0,
which keeps the chat in the primary side bar.
Several conversations at once
A chat keeps answering when you start another one with + or open an older
one, and up to three answer at the same time. The list behind the clock icon
(or labd: Show conversations, also on the chat's title bar) shows every
conversation: first the ones running now, each saying whether it is
answering, queued, waiting for you to allow a change, or done, with the
helpers still working in it, then the earlier ones, with any that failed
marked. The arrow keys move through it, and Enter opens one. The chat's icon
carries a badge with how many are answering or waiting for you, so a
conversation that needs you is not lost behind a closed side bar.
When labd changes your project
Sometimes the answer is a change rather than a paragraph, so labd can edit,
create, move and delete files, and run commands — and it explains what it did
and why, because that is the part you keep.
Edits land unsaved. A change to a file is applied in the editor and left
dirty: you see it, the gutter shows what moved, and it only reaches disk when you
save. A move or a delete is different — those happen on disk — which is why
every answer that changed files carries a put back control that reverts
the whole turn in one go, moves and deletes included. Anything you have edited
since is left alone and listed, never overwritten.
Commands are the one thing put back cannot undo. A command runs in your
own shell at the project root; whatever it did has already happened. What you
get instead is the command shown in full before it runs, stop (or Escape in the
chat) to end it, a timeout as the backstop, and the complete output in the
labd - commands output channel.
You decide how much it asks. The mode is kept per workspace, in the editor's
own storage rather than your project's settings, so a choice made in a scratch
project doesn't follow you into your coursework or into your repository.
| Mode |
What happens |
ask |
labd asks before it changes a file and before it runs anything. Nothing happens without your say-so. |
auto (default) |
labd changes files on its own — every answer can be put back in one go — and still asks before running a command. |
agent |
labd changes files and runs commands on its own. A command can do anything your own terminal can, and cannot be put back. |
Switch from the bar under the composer, and hover a mode to read what it does.
The first time you switch to agent on a computer, labd asks once in a dialog;
Cancel keeps the mode you had. labd.mode in your user settings
still works; a switch to agent from there asks you first, and workspace
settings cannot set the mode at all.
Some things are refused outright, whatever the mode and whatever labd is asked:
writing to anything holding credentials (.env, keys, certificates — labd only
ever sees which keys are set, never their values, so a write would destroy them),
.git/, dependency and build directories, anything outside the folder you have
open, and commands that need sudo, deploy, publish, git push, wipe a disk, or
read a credentials file.
Getting set up
Run labd: Connect to The Dev Labs. It shows a short code; approve that code
at learn.thedevlabs.io and the editor is connected to your account, answering on
your monthly allowance. The token is stored in VS Code SecretStorage — never in
settings.json, which syncs and turns up in screenshares.
Commands
| Command |
What it does |
labd: Ask labd |
Ask a question about the current screen (⌘⌥L) |
labd: Focus chat |
Put the caret in the chat (⌘⌥K) |
labd: Show conversations |
Every conversation, what each is doing, and the way into it |
labd: Explain this file |
Explain the open file, or the selection |
labd: What's wrong here? |
Diagnose the reported problems (⌘⌥E) |
labd: How would you improve this? |
Suggest improvements |
labd: Open a chat in an editor tab |
A second chat, beside a file |
labd: Move chat to the secondary side bar |
Put the chat on the right (the default) |
labd: Move chat to the primary side bar |
Put the chat back on the left, under labd's icon |
labd: Connect to The Dev Labs |
Pair this editor with your account |
labd: Disconnect |
Sign out and revoke this editor's token |
Settings
All of these are user settings. A workspace's own settings cannot change them, because a project you clone must not be able to point labd and your token at another server, switch off snapshots, or lengthen how long a command may run.
| Setting |
Default |
What it is |
labd.mode |
auto |
How much labd does on its own: ask, auto or agent. See above. User settings only; the chat's own choice is kept outside settings. |
labd.checkpoints |
true |
Keep a snapshot of every file labd changes, so a whole answer can be put back from the chat. Held in the editor's own storage, never in your project. |
labd.commandTimeoutSeconds |
120 |
How long a command labd runs may take before it is stopped, if nobody stops it first. |
labd.chatLocation |
secondary |
Where the chat lives: secondary (the side bar on the right) or primary (under labd's icon on the left). |
labd.serverUrl |
https://agent.thedevlabs.io |
The labd agent server. Change only when running one locally. |
Privacy
The chat panel holds no credentials and makes no network calls of its own — the
extension host owns the token and every request, which is why the panel's content
security policy forbids outbound connections entirely.
What is sent when you ask a question: the lines of the open file you can see on
screen (not the whole file), your selection, the errors the editor is reporting,
the names of your other open files, your branch and last few commits, your
project's conventions file, and anything labd reads or runs while answering.
Nothing is sent unless you ask something.
Made by The Dev Labs.