GIDE 2.0.0: Private Cloud, Write Gate and a safer agent
GIDE 2.0.0 adds Private Cloud mode, puts every file write and shell command behind your approval with the Write Gate and Command Gate, gives the agent a dedicated Git tool, and rewrites GIDE Wiki's architecture graph.
- Version
- v2.0.0
- Type
- Major release
- Released
GIDE 2.0.0 is built around one idea: the agent should never change your project behind your back. Every file write and every shell command now waits for your approval. The release also adds Private Cloud mode, a dedicated Git tool, and a rewritten GIDE Wiki.
At a glance
- Private Cloud mode. Switch between local and cloud inference from the status bar.
- Write Gate. Every file write pauses for Accept, Reject or Allow All.
- Command Gate. Shell commands need your approval before they run.
- Git tool. Safe, attribution-aware Git and GitHub operations.
- Smarter recovery. The agent switches strategy instead of getting stuck.
- GIDE Wiki v2. A real import graph of your codebase.
Private Cloud mode
Toggle between local and cloud inference directly from the GIDE status bar. When Private Cloud is on, model calls go to a remote OpenAI-compatible endpoint, with no manual .env editing. Access is protected by a token, and GIDE falls back cleanly when Private Cloud isn’t configured.
Write Gate: confirm every file write
What changed
Every file write now pauses the agent and shows a confirmation popup with three choices:
- Accept this write.
- Reject it.
- Allow All for the rest of the session.
How it behaves
A write you don’t respond to is rejected after 2 minutes. The agent is told when a write is rejected and won’t retry it.
Command Gate
Shell commands run through run_command now need your explicit approval before they execute, the same way file writes do. The gate shows the exact command and its working directory. Running processes can be stopped, and any pending approval is rejected automatically if the session disconnects.
Git tool
A dedicated Git tool replaces raw shell access to git. It supports:
- status, diff, log, add, commit, branch, checkout and init
- push and remote management
- GitHub operations: create a repo, and create, list or get issues
Destructive operations such as force push, hard reset and branch delete are blocked unless you explicitly allow them. Shell-based git and gh commands are now blocked, so the agent has to use the Git tool.
Every commit made through the Git tool gets this trailer appended automatically:
Co-Authored-By: Gide
A smarter agent
- Deadlock recovery. After two failed writes in a row, the agent is forced to switch strategy instead of repeating itself.
- Fewer false rejections. The duplicate-structure checker now merges fixes instead of rejecting them, and partial progress toward a goal is accepted instead of blocked.
- Cleaner plans. When new code and changes target the same file, the task planner combines them into one replace step.
GPU detection on Windows
GPU detection now works natively on Windows, with a fallback when the primary check isn’t available. GIDE now auto-detects the GPU instead of falling back to the CPU, and console windows no longer pop up on Windows.
Chat status and tool chips
Tool chips now have readable labels, such as “Writing filename.ts” or “Searching codebase”, with file language icons and line counts for each change (for example +47 / −12 lines). Thinking shows as clean quoted text, and the line counts persist across reloads.
GIDE Wiki v2
GIDE Wiki’s codebase visualization was rewritten:
- It builds a real import dependency graph with Tree-sitter, instead of guessing from directory names.
- Large repositories are grouped into clusters, and cluster names come from the actual file content.
- Architectural layers are assigned by clear path rules.
- Progress streams to the view in real time.
- A new scrollable layout shows the diagram and system cards side by side.
For the short version of every change, see the GIDE changelog.