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
feat: Complete Orcide rebrand with SSO, user profiles, collaboration, and Orcest AI API integration
- Complete rebrand from Void to Orcide across all user-facing strings, configs, and messages
- Add SSO authentication service (OIDC/OAuth2) with login.orcest.ai integration
- PKCE-based authorization flow with popup and redirect support
- Automatic token refresh, secure storage, and session management
- Add SSO browser service with popup window management and command palette actions
- Sign In, Sign Out, SSO Status, and Refresh Token commands
- Add user profile service with SSO-based identity isolation
- Per-user preferences, repositories, and active session tracking
- Add collaboration service for resource sharing and team management
- Share workspaces, chat threads, model configs, and MCP servers
- Team member invitation and role-based access control
- Add orcestAI as new API provider with RainyModel as default
- Pre-configured endpoint: https://rm.orcest.ai/v1
- Default models: rainymodel-pro, gpt-4o, claude-3.5-sonnet, etc.
- Update product.json with SSO config, default API, and Orcest ecosystem URLs
- Update storage keys, metrics, file transfer paths, and build configs
https://claude.ai/code/session_01CjDqzV3ECQxE1g4jFn7PBu
Copy file name to clipboardExpand all lines: VOID_CODEBASE_GUIDE.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
-
# Void Codebase Guide
1
+
# Orcide Codebase Guide
2
2
3
-
The Void codebase is not as intimidating as it seems!
3
+
The Orcide codebase is not as intimidating as it seems!
4
4
5
-
Most of Void's code lives in the folder `src/vs/workbench/contrib/void/`.
5
+
Most of Orcide's code lives in the folder `src/vs/workbench/contrib/void/`.
6
6
7
-
The purpose of this document is to explain how Void's codebase works. If you want build instructions instead, see [Contributing](https://github.com/orcest-ai/Orcide/blob/main/HOW_TO_CONTRIBUTE.md).
7
+
The purpose of this document is to explain how Orcide's codebase works. If you want build instructions instead, see [Contributing](https://github.com/orcest-ai/Orcide/blob/main/HOW_TO_CONTRIBUTE.md).
8
8
9
9
10
10
@@ -14,10 +14,10 @@ The purpose of this document is to explain how Void's codebase works. If you wan
14
14
15
15
16
16
17
-
## Void Codebase Guide
17
+
## Orcide Codebase Guide
18
18
19
19
### VSCode Rundown
20
-
Here's a VSCode rundown if you're just getting started with Void. You can also see Microsoft's [wiki](https://github.com/microsoft/vscode/wiki/Source-Code-Organization) for some pictures. VSCode is an Electron app. Electron runs two processes: a **main** process (for internals) and a **browser** process (browser means HTML in general, not just "web browser").
20
+
Here's a VSCode rundown if you're just getting started with Orcide. You can also see Microsoft's [wiki](https://github.com/microsoft/vscode/wiki/Source-Code-Organization) for some pictures. VSCode is an Electron app. Electron runs two processes: a **main** process (for internals) and a **browser** process (browser means HTML in general, not just "web browser").
@@ -54,7 +54,7 @@ Here's some terminology you might want to know about when working inside VSCode:
54
54
55
55
### Internal LLM Message Pipeline
56
56
57
-
Here's a picture of all the dependencies that are relevent between the time you first send a message through Void's sidebar, and the time a request is sent to your provider.
57
+
Here's a picture of all the dependencies that are relevent between the time you first send a message through Orcide's sidebar, and the time a request is sent to your provider.
58
58
Sending LLM messages from the main process avoids CSP issues with local providers and lets us use node_modules more easily.
59
59
60
60
@@ -69,7 +69,7 @@ Sending LLM messages from the main process avoids CSP issues with local provider
69
69
70
70
### Apply
71
71
72
-
Void has two types of Apply: **Fast Apply** (uses Search/Replace, see below), and **Slow Apply** (rewrites whole file).
72
+
Orcide has two types of Apply: **Fast Apply** (uses Search/Replace, see below), and **Slow Apply** (rewrites whole file).
73
73
74
74
When you click Apply and Fast Apply is enabled, we prompt the LLM to output Search/Replace block(s) like this:
75
75
```
@@ -79,7 +79,7 @@ When you click Apply and Fast Apply is enabled, we prompt the LLM to output Sear
79
79
// replaced code goes here
80
80
>>>>>>> UPDATED
81
81
```
82
-
This is what allows Void to quickly apply code even on 1000-line files. It's the same as asking the LLM to press Ctrl+F and enter in a search/replace query.
82
+
This is what allows Orcide to quickly apply code even on 1000-line files. It's the same as asking the LLM to press Ctrl+F and enter in a search/replace query.
83
83
84
84
### Apply Inner Workings
85
85
@@ -97,10 +97,10 @@ How Apply works:
97
97
98
98
99
99
### Writing Files Inner Workings
100
-
When Void wants to change your code, it just writes to a text model. This means all you need to know to write to a file is its URI - you don't have to load it, save it, etc. There are some annoying background URI/model things to think about to get this to work, but we handled them all in `voidModelService`.
100
+
When Orcide wants to change your code, it just writes to a text model. This means all you need to know to write to a file is its URI - you don't have to load it, save it, etc. There are some annoying background URI/model things to think about to get this to work, but we handled them all in `voidModelService`.
101
101
102
-
### Void Settings Inner Workings
103
-
We have a service `voidSettingsService` that stores all your Void settings (providers, models, global Void settings, etc). Imagine this as an implicit dependency for any of the core Void services:
102
+
### Orcide Settings Inner Workings
103
+
We have a service `voidSettingsService` that stores all your Orcide settings (providers, models, global Orcide settings, etc). Imagine this as an implicit dependency for any of the core Orcide services:
0 commit comments