Files beside the session
Keep the workspace, conversation, and context together instead of stitching windows.
Checking sign-in status
01DESKTOP / GUI 04
A desktop AI coding workspace where changes stay visible
Cocode GUI puts sessions, files, terminals, runtime state, and diff previews on one workbench so you can see what the agent did before you confirm it.
Capabilities and limits follow the current release
02Direct answer
Start with what it is.
Cocode GUI is a desktop AI coding workspace that keeps Sessions, files, terminals, runtime state, and diffs in one interface. It is for developers who want to inspect real impact before an agent writes files, runs commands, or continues a task.
- Product shape
- Desktop GUI AI coding client
- Visible context
- Sessions, files, terminal, attachments, diffs, and runtime state
- Platform entry
- macOS, Linux, and Windows; installers follow the current release
- Remote continuity
- Continue through TUI or SSH within the same Host scope
Review before confirm
Open code changes, attachments, and results in a preview surface.
The terminal is still there
Run commands without leaving the task context.
02Why it matters
A desktop workspace you can inspect
The GUI puts task conversation, file tree, terminal, and runtime state together so the agent’s explanation and the repository’s actual changes can be compared.
For developers who need visible feedback
If you want to see the impact before files are written, commands run, or network tools are used, the GUI provides the strongest visual context.
↗
Clear boundaries make real development work easier to trust.
Start on desktop, continue in terminal
GUI and TUI are not separate products. With the same Host scope, both clients can continue the same session.
↗
Clear boundaries make real development work easier to trust.
05Working flow
Move from setup to verification with a clear result at every step.
This is an executable, reviewable path through a real repository—not an abstract feature list.
- 01
Choose a project and Session
Start from the workspace so the file tree, conversation, and runtime state share one context.
- 02
Describe the task in the main panel
Set goals, acceptance criteria, and protected areas, then inspect the agent plan and tool actions.
- 03
Review files and diffs
Check actual changes, attachments, command output, and tests before continuing.
- 04
Move to terminal when needed
Use the integrated terminal or continue the same Host and Session through TUI or SSH.
06Use cases
Decide by the work you actually need to finish.
Developers who need visual context
See files, conversation, terminal, and results together with fewer window switches.
Review-first repository work
Understand the impact before writes or further execution in higher-risk codebases.
Hybrid desktop and remote work
Organize the task in GUI, then finish remote verification through TUI or SSH.
07Before you start
Runtime requirements and compatibility boundaries
- A matching macOS, Linux, or Windows installer from the current release
- Read access to the workspace and write access when changes are required
- A reachable model service or self-hosted endpoint
- The same Host, Profile, and Session scope for terminal continuation
08Try it
Continue from GUI to TUI
After creating the task on desktop, open TUI in the same environment to continue.
cocode://workspaceREADY
cocode doctor
cocode09Facts and boundaries
Desktop visibility helps review but does not replace verification.
GUI makes context and impact easier to inspect. Actual behavior still depends on the workspace, Host, model, and permissions.
| Capability | Status | Conditions and evidence scope |
|---|---|---|
| Files and diffs | Visible | Inspect workspace files and agent changes within the current task scope. |
| Terminal workflow | Integrated | View and run commands without leaving the task context. |
| Cross-client continuity | Same-scope support | GUI and TUI must connect to the same Host, Profile, and Session. |
| Automatic safety | Not implied | A visible interface cannot replace permissions, confirmation, backups, and real tests. |
10Cocode perspective
Visibility is an entry point for review, not a safety verdict.
Cocode GUI puts model explanations, file diffs, terminal output, and runtime state where they can be compared. Whether to continue depends on actual impact and task risk.
- Maintained by
- Cocode Agency
- Last reviewed
- 2026-08-25
- Scope
- Cocode GUI workspace, diffs, terminal, and cross-client continuity
- Verification
- Maintained against the current desktop interface, Host connection, and visible workflow
06FAQ
Before you start, make the boundaries clear.
Which platforms does Cocode GUI support?
The website provides download entry points for macOS, Linux, and Windows. The exact installers depend on the matching GitHub Release.
Can I inspect file changes in the GUI?
Yes. Files, diffs, attachments, and terminal state are presented in the visible workspace.
Is the desktop client safer than the terminal client?
Interface shape alone cannot decide safety. GUI provides more visible context, while both clients still require correct permissions, confirmation, and verification.
Can GUI and TUI open the same task at the same time?
They can connect to the same task within the same Host and Session scope. Check active state before acting to avoid concurrent-edit conflicts.