bzcode
The bzcode coding agent in VS Code: chats in editor tabs that read, edit and run code
in your workspace, and the workspace's sessions in the sidebar.
Open a chat from the bzcode icon at the top right of an editor, or bzcode: Open
Chat. Each tab is its own agent and session, so several can run side by side.
The sidebar lists this workspace's sessions, newest first: click one to open it
in a tab (or to go to its tab), or start a New Chat.
MCP Servers, in the sidebar, lists the servers your settings name: add, remove,
disable or enable one, for every chat (open chats reload on it). In a chat, /mcp shows
how each is doing there, with Connect, Disconnect and Sign in for that chat.
Send with Enter; steer a running agent with Ctrl/Cmd+Enter; interrupt
with Esc, which hands back anything still queued.
/ lists commands: the session's own, plus /new and /resume.
@ lists the workspace's files: a file or folder named with @path (or
@path#L5-10 for lines) is attached to the message when it is sent.
+ in the message box: Upload image…, or Add context, which starts an
@. Images can also be pasted or dropped into the box.
Add to bzcode Chat, on a file or folder in the explorer, an editor's tab, or in
an editor, mentions it in the message box; Add Selection to bzcode Chat mentions
the selected lines (@path#L5-10), or puts the code itself in when the file has
unsaved changes or is not saved anywhere yet.
bzcode: Sign In to Boltzbit takes an API key, checks it with Boltzbit and keeps it
in the OS keychain; the account then shows in VS Code's Accounts menu. BZ_API_KEY
in VS Code's environment, when set, is used instead. The agent reads its settings
from ~/.bzcode/settings.json (or $BZ_HOME) and the workspace's .bzcode/, as the
bzcode CLI does.
The extension runs the bzcode bundled with it, else bzcode on the PATH;
bzcode.binaryPath (a User setting) runs another, or a .ts entry through Bun for
working on bzcode. The bzcode Output channel logs how the agent was started, what
it wrote to stderr, and why it stopped.
| |
