Skip to content

docs: cover AI SDK flag and background job polling in CLI #11357

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.

Sign up for GitHub

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

Open
fahe1em1 wants to merge 1 commit into
base: main
Choose a base branch
from
+19 −0
Open

docs: cover AI SDK flag and background job polling in CLI #11357

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/cli/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,3 +75,16 @@ Store sensitive values (API keys, tokens) in [Continue → Settings → Secrets]
```yaml
${{ secrets.MY_API_KEY }}
```

## Advanced environment flags

### `CONTINUE_USE_AI_SDK`

Set `CONTINUE_USE_AI_SDK=1` to route `openai` and `anthropic` provider requests through Continue's Vercel AI SDK adapter instead of the default provider clients:

```bash
export CONTINUE_USE_AI_SDK=1
cn
```

This is useful when you want to test the AI SDK-backed request path without changing your `config.yaml`. The flag only changes `openai` and `anthropic` providers; all other providers continue using their standard adapters.
6 changes: 6 additions & 0 deletions docs/cli/headless-mode.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,12 @@ cn -p "Set up the project" --allow "*"

See [tool permissions](/cli/tool-permissions) for the full policy system.

Read-only helpers such as `CheckBackgroundJob` remain allowed by default, so the agent can safely inspect long-running work without additional approval.

## Background jobs

If a shell command is moved to the background, Continue returns a job id and the output collected so far. The agent can then call `CheckBackgroundJob("<job-id>")` to fetch the current status, exit code, and accumulated output while the job continues running.
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Clarify headless background-job polling prerequisite

This headless-mode section describes a polling flow that cannot currently be initiated in cn -p runs: Bash only returns a Continue job id when runTerminalCommand receives a backgroundRequested signal, and the only signal source in the repo is the Ctrl+B TUI input handler (extensions/cli/src/ui/hooks/useUserInput.ts). In headless CI usage there is no interactive key handler, so commands cannot be moved into Continue-managed background jobs and users will not get the job id needed for CheckBackgroundJob polling.

Useful? React with 👍 / 👎.


## Authentication in CI

Set `CONTINUE_API_KEY` instead of running `cn login`:
Expand Down
Loading