You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/PRD.en.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ The implementation baseline comes primarily from:
23
23
24
24
Coder Studio is a Tauri-based desktop workbench that brings the following tasks into one operational surface:
25
25
26
-
- connecting local or remote Git repositories
26
+
- connecting local Git workspaces
27
27
- starting and managing Claude agent sessions
28
28
- splitting parallel agent workstreams
29
29
- browsing, editing, and saving code files
@@ -45,20 +45,21 @@ The current product position is:
45
45
## 4. Supported Environment
46
46
47
47
- runtime: desktop app built with Tauri
48
-
- workspace sources: `Remote Git` and `Local Folder`
48
+
- current workspace source: `Local Folder`
49
+
- remote Git: backend plumbing still exists, but the creation entry is hidden in the current release and deferred to the next phase
49
50
- execution targets: `Native`, plus `WSL` when available
50
51
- agent provider: currently `Claude` only
51
52
- languages: Chinese and English
52
53
- theme: dark-only in the current build
53
-
- storage: local-first, with frontend state in Local Storage and backend session/archive persistence in a local database
54
+
- storage: local-first, with workspace/session/layout/view persistence in backend SQLite and app settings plus language preference in browser local storage
54
55
55
56
## 5. Current Product Scope
56
57
57
58
### 5.1 Workspace Onboarding
58
59
59
60
- The app starts with a workspace launch overlay.
60
-
-Users can choose `Remote Git` or `Local Folder`.
61
-
-In remote mode, the app clones a repository URL into a temporary working directory inside the selected execution target.
61
+
-The current release only exposes `Local Folder` for workspace creation.
62
+
-The remote Git clone path still exists in backend code, but the UI entry is intentionally hidden and should not be described as a shipped feature.
62
63
- In local mode, the app uses a backend-backed directory browser that supports:
63
64
- current path display
64
65
- Home
@@ -204,12 +205,10 @@ The current product position is:
204
205
205
206
### 5.10 Local Persistence
206
207
207
-
- Workbench state is stored in Local Storage.
208
-
- Persisted frontend data includes:
209
-
- workspace and layout state
210
-
- app settings
211
-
- selected language
212
-
- The backend persists session and archive snapshots into a local database.
208
+
- Workbench state is no longer stored in Local Storage.
209
+
- Persisted data now includes:
210
+
- backend SQLite: workspaces, sessions, archives, workbench layout, and per-workspace view state
211
+
- browser local storage: app settings and selected language
213
212
- Closing a non-draft pane archives the related backend session.
214
213
- The UI can already render a read-only archive session view, but archive browsing is not yet exposed as a complete user-facing center.
215
214
@@ -219,9 +218,9 @@ The current product position is:
219
218
220
219
1. Open the app.
221
220
2. Enter the workspace launch overlay.
222
-
3. Choose `Remote Git` or `Local Folder`.
223
-
4.Choose `Native` or `WSL`.
224
-
5.Enter a Git URL or pick a local directory.
221
+
3. Choose `Native` or `WSL`.
222
+
4.Pick a local directory in the built-in directory browser.
223
+
5.Let the app resolve and attach the matching Git repository root.
225
224
6. After launch, the main workspace loads repository data, file tree, and Git information.
226
225
227
226
### 6.2 Start the First Agent Task
@@ -275,19 +274,20 @@ The following should not be presented as current shipped user-facing functionali
275
274
- a complete auto-suspend execution loop
276
275
- user-facing session mode switching between `branch` and `git_tree`
277
276
- MCP settings UI or advanced Claude configuration screens
277
+
- a user-visible remote Git workspace creation entry
278
278
279
279
## 8. Current Constraints
280
280
281
281
- Local folder onboarding depends on resolving a Git repository root rather than accepting arbitrary folders.
282
-
- Remote repositories are cloned into temporary directories whose location depends on the execution target.
282
+
- Remote Git still has backend plumbing, but the current release hides the entry point, so it must not be documented as a supported user flow.
283
283
- WSL support depends on `wsl.exe` and target-specific path resolution.
284
284
- The configured Claude launch command must exist in the selected runtime environment.
285
285
- Queue, archive, and worktree capabilities currently show a “backend first, UI surface incomplete” shape, so documentation must describe only what users can actually do in the interface.
286
286
287
287
## 9. Acceptance Criteria
288
288
289
289
1. The app must show the workspace launch overlay on first entry or when creating a new workspace.
290
-
2. Users must be able to start a workspace from either `Remote Git` or `Local Folder`.
290
+
2. Users must currently be able to start a workspace only through `Local Folder`, and the creation flow must not expose a remote Git option.
291
291
3. In supported environments, users must be able to choose `Native` or `WSL` execution.
292
292
4. Once a workspace loads, the main agent area must be visible and non-started panes must show the draft input field.
293
293
5. Submitting the first draft input must materialize a session, start the agent, generate the title, and switch the pane to interactive terminal mode.
0 commit comments