Layouts that remember
Terminal groups, open files, preview state, and panel geometry return with the workspace.
All product areas
02 / Workspaces
A local command center for the whole project.
Sourceweave keeps the surfaces that make a project understandable in one durable workspace: files, terminals, branches, editors, processes, browser previews, and agent threads that stay attached to their work.
Actual desktop workspace capture
WHAT IT CHANGES
Less reconstruction.
More visible progress.
Processes stay attached
Launch the project once, inspect its output, and keep the browser connected while you review changes.
Git stays visible
Branches, changed files, diffs, and apply actions sit beside the work instead of behind a second tool.
Real CLI terminals
Run Codex, Claude Code, OpenCode, and other supported CLIs in resizable grid, row, or column groups.
Editing without a handoff
Use Monaco, Markdown preview, dirty-state protection, and file-level Git diffs without leaving the project.
A browser made for local apps
Open Chromium previews, switch responsive viewports, inspect DOM and styles, and turn a selection into an agent task.
Threads that retain the work
Keep the prompt, reasoning, tool activity, file changes, checks, and final handoff together in an isolated workspace conversation.
WHAT IS BUILT IN
The working surfaces behind Workspaces.
Arrange the actual tools you use
Add, rename, resize, maximize, stop, and restart terminal groups. Save quick commands globally or per workspace and drag file paths directly into an agent session.
Browse, search, edit, and compare
Use recursive file browsing, quick open, recent files, Monaco editing, Markdown source or split preview, external-change warnings, and unsaved-close protection.
Preview the project inside the environment
Sourceweave discovers local URLs, keeps the preview attached to its process, supports responsive sizes, and captures visual context for a follow-up agent.
Move from local change to pull request
Stage, commit, pull, push, publish branches, connect repositories, create ready or draft pull requests, and inspect checks and merge state.
Keep agent conversations beside the project
Open an isolated thread in the workspace, follow its reasoning and tool activity, inspect changed files and checks, then apply the result only when it is ready.
THREADS LIVE INSIDE WORKSPACES
A durable conversation, attached to the project.
Start a thread without leaving the workspace. The request, reasoning, commands, changed files, checks, and final response remain in one inspectable transcript, isolated until you decide the result is ready.
- 01Context stays attachedContinue the same task without reconstructing the project state.
- 02Activity stays visibleRead tool calls, file changes, and verification beside the chat.
- 03You control the handoffReview the isolated result before it reaches the workspace.
WORKSPACE THREAD
HOW IT WORKS
A deliberate path through Workspaces.
- 01
Open a folder
Sourceweave detects the repository, available CLIs, and the commands the project already exposes.
- 02
Arrange the surfaces
Pin terminals, editor panes, file trees, and previews into the layout that fits the job.
- 03
Work manually or open a thread
Stay hands-on in the editor and terminals, or start a durable agent conversation with the workspace context already attached.
- 04
Keep the context
Return later without reconstructing the same debugging environment from scratch.
KEEP EXPLORING