feat: rename /directory to /workspace and unify terminology (v2)#20774
Closed
keithguerin wants to merge 11 commits into
Closed
feat: rename /directory to /workspace and unify terminology (v2)#20774keithguerin wants to merge 11 commits into
keithguerin wants to merge 11 commits into
Conversation
Renames the /directory command to /workspace, adds aliases for backward compatibility, and updates UI strings, settings, and prompts to use 'workspace' terminology consistently. Linked to #20737. Per Core/UX chat on 2/18.
Contributor
|
Hi @keithguerin, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
|
You already have 7 pull requests open. Please work on getting existing PRs merged before opening more. |
Contributor
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a significant terminology refactor, standardizing the use of 'workspace' in place of 'directory' and 'project' throughout the application. This change aims to improve conceptual clarity and consistency, particularly in how users interact with commands, configure settings, and understand the scope of operations within the CLI. The update encompasses command names, configuration files, internal APIs, and all relevant documentation and user interface elements, ensuring a cohesive user experience. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request primarily renames all instances of 'project' to 'workspace' across the codebase, including documentation, CLI commands, configuration settings, UI elements, and internal services. Key changes involve updating command names (e.g., /directory to /workspace), configuration scopes, file paths, temporary directories, and prompt contexts to reflect a 'workspace'-centric terminology. Deprecated 'project' references are often replaced with 'workspace' equivalents, sometimes with backward compatibility. The change aims to standardize the terminology used throughout the application.
gemini-cli
Bot
added
the
area/core
| const client = config.getBaseLlmClient(); | ||
| const prompt = ` | ||
| I am triaging GitHub issues for the Gemini CLI project. I need to identify issues that should be closed because they are: | ||
| I am triaging GitHub issues for the Gemini CLI workspace. I need to identify issues that should be closed because they are: |
Collaborator
There was a problem hiding this comment.
not sure about this one...
| - Abusive or offensive | ||
| - Gibberish (nonsense text) | ||
| - Clearly out of scope for this project | ||
| - Clearly out of scope for this workspace |
Collaborator
There was a problem hiding this comment.
ditto here, leave as project.
|
Size Change: +3.98 kB (+0.02%) Total Size: 25.8 MB
ℹ️ View Unchanged
|
6 tasks
This was referenced Mar 2, 2026
gemini-cli
Bot
added
priority/p1
…orkspace # Conflicts: # docs/cli/settings.md # docs/reference/configuration.md # packages/cli/src/config/settings.test.ts # packages/cli/src/config/settingsSchema.ts # packages/cli/src/services/CommandService.test.ts # packages/cli/src/services/FileCommandLoader.ts # packages/cli/src/ui/components/RewindViewer.test.tsx # packages/cli/src/ui/constants/tips.ts # packages/cli/src/ui/utils/borderStyles.test.tsx # packages/cli/src/utils/processUtils.test.ts # packages/cli/src/utils/sessionUtils.ts # packages/core/src/commands/memory.test.ts # packages/core/src/config/config.ts # packages/core/src/config/storage.test.ts # packages/core/src/core/__snapshots__/prompts.test.ts.snap # packages/core/src/scheduler/tool-executor.ts # packages/core/src/services/contextManager.ts # packages/core/src/utils/memoryDiscovery.test.ts # packages/core/src/utils/memoryDiscovery.ts # schemas/settings.schema.json
This was referenced Mar 10, 2026
Collaborator
|
This PR is resolved by #21877 that took inspiration from this original change. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rename the
/directorycommand to/workspaceand standardize on 'workspace' terminology (instead of 'project') across the CLI, UI, MCP, settings, and prompts.Details
/directoryand/dirto/workspace, keeping old names as aliases for backward compatibility.packages/cliandpackages/coreto use "workspace" terminology.workspaceHashinstead ofprojectHash).packages/clicaused by snapshot mismatches, terminology updates, and missing custom matchers.docs/.projectId).Per Core/UX chat on 2/18.
Related Issues
Linked to #20737
How to Validate
npm run start/workspaceand verify it shows the workspace status./directoryand/dirand verify they still work as aliases.npm run testacross the monorepo to ensure all fixes are passing.Pre-Merge Checklist