-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Agentic Chat) Deep Cody docs #841
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
### Enable Agentic Chat access to CLI | ||
|
||
Update the `cody.agentic.context` setting to `allow` or `block` specific commands: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@graceshih-sg I need to double-check this section with you. Is it factually correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left some comments inline for the changes
|
||
### Configure shell command execution | ||
|
||
You can configure shell command execution via the `cody.agentic.context` setting in your editor: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### Enable Agentic Chat access to CLI | ||
|
||
Update the `cody.agentic.context` setting to `allow` or `block` specific commands: | ||
|
||
```json | ||
{ | ||
"cody.agentic.context": { | ||
"shell": { | ||
// Array of allowed command prefixes, or ["*"] for all commands | ||
"allow": ["git", "gh", "ls"], | ||
"block": ["git"] // Additional commands to block | ||
} | ||
} | ||
} | ||
``` | ||
|
||
#### Disable Agentic Chat access to CLI | ||
|
||
To disable the feature, navigate to your user settings and set `cody.agentic.context` to an empty value. When disabled, the chat agent cannot access the CLI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MaedahBatool we have moved the settings out of the json file into the UI:
#### Enable Agentic Chat access to CLI | |
Update the `cody.agentic.context` setting to `allow` or `block` specific commands: | |
```json | |
{ | |
"cody.agentic.context": { | |
"shell": { | |
// Array of allowed command prefixes, or ["*"] for all commands | |
"allow": ["git", "gh", "ls"], | |
"block": ["git"] // Additional commands to block | |
} | |
} | |
} | |
``` | |
#### Disable Agentic Chat access to CLI | |
To disable the feature, navigate to your user settings and set `cody.agentic.context` to an empty value. When disabled, the chat agent cannot access the CLI. |
|
||
### Security concerns | ||
|
||
As mentioned above, Agentic Chat's ability to execute terminal commands enhances its context-gathering capabilities. However, it’s essential to understand that any information accessible via your terminal could be shared with the LLM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should mention how they can disable this feature by setting agentic-chat-cli-tool-experimental
to false
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: graceshih-sg <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: graceshih-sg <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Co-authored-by: Beatrix <[email protected]>
Docs for Agentic chat experience (Deep Cody).
Preview URL: https://sourcegraph-docs-git-deep-cody-docs-sourcegraph-f8c71130.vercel.app/docs/cody/capabilities/deep-cody