Integrations: VS Code, JetBrains, Slack and CI/CD

You will connect the editor integration, understand shared settings and scope CI automation before installing anything. Outputs are illustrations.

VS Code, JetBrains and CI sources checked September 30, 2026 describe extensions sharing the CLI's configuration, and GitHub/GitLab integrations that let Claude act on your repositories. A pipeline that can push commits is a production system, not a toy.

The VS Code and JetBrains integrations use the same ~/.claude/settings.json as the CLI: allowed commands, hooks, MCP servers and permissions are shared. A rule you added for terminal safety applies in the editor too, and vice versa. Sign-in prompts in the IDE can mean the editor did not inherit your shell environment.

The IDE adds review affordances: inline diffs, plan review before accepting, @-mentions with line ranges. Use plan review on anything that edits; auto-accept modes remove the checkpoint.

The GitHub Action responds to @claude mentions, turns issues into pull requests and can run on any GitHub event. Setup needs repo admin access, the Claude GitHub App and an auth secret: ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN from claude setup-token.

Before installing, plan the boundary:

Plan a GitHub Action setup for the course repository without running it.
List app permissions, secret type, trigger events and what Claude may push.
Review-only first: comments on PRs, no automatic merges or branch protection changes.

Illustrative scope decision:

Trigger: @claude mentions in issues/PRs only.
Writes: commits to claude/* branches, PR comments.
Not granted: protected branch writes, secrets access beyond the auth secret.
Auth: OAuth token from this subscription (single repo).

An OAuth token is tied to the subscription of the person who generated it; an organization-wide rollout should use an API key or workload identity federation instead.

The ready review workflow posts inline PR comments and skips drafts. Your own claude.yml can respond to mentions or run on a schedule. Treat its prompt as code: anyone who can trigger the event can influence what Claude is asked to do, so review what triggers are enabled and what tools the job allows.

Removing the action means deleting workflow files, deleting the repo or org secret and uninstalling the GitHub App when no other Claude feature needs it. Deleting a secret does not invalidate the credential; retire the key or token itself to fully revoke.

Easy: shared settings

Find one CLI rule that also governs the IDE. Success: settings path identified.

Intermediate: trigger review

Classify three workflow triggers by risk. Success: mention-triggered vs scheduled distinguished.

Challenging: secret choice

Pick auth for one repo vs an organization. Success: OAuth vs API key tradeoff stated.

IDE asks to sign in: launch from a terminal so it inherits the environment.

Job does nothing: check trigger event and app installation on the repo.

Claude pushed too far: inspect branch protections and allowed tools in the workflow.

Secret leaked: delete the secret and rotate the underlying credential.

Old review workflow: rerun /install-github-app and choose update.