Skip to content

Commit

Permalink
Adding emphasis to steps
Browse files Browse the repository at this point in the history
A couple customers are getting confused and using both env vars and cody auth login to authenticate with the CLI leading to undesirable effects. This change adds emphasis for customers getting started with CLI
  • Loading branch information
airamare01 authored Dec 23, 2024
1 parent aaa1d78 commit 1cad93d
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions docs/cody/clients/install-cli.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -98,8 +98,8 @@ export SRC_ENDPOINT=ENDPOINT
export SRC_ACCESS_TOKEN=ACCESS_TOKEN
cody auth login # stores the access token securely
```
You don't need to export `SRC_ENDPOINT` or `SRC_ACCESS_TOKEN` after running `cody auth login`.
Subsequent command invocation will use the stored access token.
<Callout type="info">You don't need to export `SRC_ENDPOINT` or `SRC_ACCESS_TOKEN` after running `cody auth login`.
Subsequent command invocation will use the stored access token.</Callout>
</Tab>
</Tabs>

Expand All @@ -112,7 +112,8 @@ cody auth whoami

## Authenticate with only environment variables

Skip this step if you have already authenticated with the `cody auth login` command.
**Skip this step if you have already authenticated with the `cody auth login` command.**


If you prefer not to let Cody CLI store your access token, you can also pass the endpoint URL and access token through the environment variables `SRC_ENDPOINT` and `SRC_ACCESS_TOKEN`.

Expand Down

0 comments on commit 1cad93d

Please sign in to comment.