mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-05-18 07:43:00 -07:00
mkorwel
36 lines
1.8 KiB
Markdown
36 lines
1.8 KiB
Markdown
# Future State: Gemini Workspaces Platform
|
|
|
|
This document outlines the long-term architectural evolution of the Workspaces feature (formerly "Workspace").
|
|
|
|
## 🎯 Vision
|
|
Transform Workspaces into a first-class platform capability that allows developers to seamlessly move intensive workloads (AI reasoning, complex builds, parallel testing) to any compute environment (Cloud or Local).
|
|
|
|
## 🗺️ Evolutionary Roadmap
|
|
|
|
### Phase 1: Generalization & Renaming (Current)
|
|
- **Goal**: Make the feature useful for any repository, not just Gemini CLI.
|
|
- **Action**: Rename to "Workspaces."
|
|
- **Action**: Implement dynamic repository detection via Git.
|
|
- **Action**: Isolate all state into `.gemini/workspaces/`.
|
|
|
|
### Phase 2: Pluggable Compute Extensions
|
|
- **Goal**: Decouple the infrastructure logic from the core CLI.
|
|
- **Action**: Move `WorkerProviders` into a dedicated **Workspaces Extension**.
|
|
- **Action**: Support multiple providers (GCP, AWS, Local Docker).
|
|
- **Action**: Define a standard API for Workspace Providers.
|
|
|
|
### Phase 3: Core Integration
|
|
- **Goal**: Standardize the user experience.
|
|
- **Action**: Move the high-level `gemini workspace` command into the core `gemini` binary.
|
|
- **Action**: Implement automated "Environment Hand-off" where the local agent can automatically spin up a remote workspace when it detects a heavy task.
|
|
|
|
### Phase 4: Public Marketplace
|
|
- **Goal**: Community adoption.
|
|
- **Action**: Publish the official GCP Workspace Extension.
|
|
- **Action**: Provide a "Zero-Config" public base image for standard Node/TS development.
|
|
|
|
## 🏗️ Architectural Principles
|
|
1. **BYOC (Bring Your Own Cloud)**: Users connect their own infrastructure.
|
|
2. **Nested Persistence**: Keep the environment in the container, but manage the lifecycle with the host.
|
|
3. **Repo-Agnostic**: One set of tools should work for any project.
|