Claude Code / Platform integration
Platform integration overview
Claude Code can be accessed from the terminal, editor, web, desktop, Chrome, Slack and GitHub processes.
Platform selection
Claude Code is available in CLI, Desktop, VS Code, JetBrains, Web, Mobile, Chrome, Slack, and CI/CD. Look for three things when choosing an entry: where is the context, where is the validation, and where is the approval.
| Platform | Strengths | Limit |
|---|---|---|
| CLI | Local commands, real repositories, scripting. | You are required to manage the terminal environment. |
| IDE | Reference files, inline diff, and in-editor transfer. | Large verification still relies on project commands. |
| Desktop | Multi-session, parallel tasks, side collaboration. | Need to understand session isolation and work trees. |
| Web / mobile | Cloud tasks, cross-device, remote PR. | Local login status and personal configuration are not fully available. |
| Slack | Initiate a task from a team conversation. | Repositories and permissions come from the personal Claude account. |
How to decide the entrance
When you need local login status, browser status or private services, use local CLI/IDE/Chrome. No local status required, PR or Issue suitable for cloud running, available on the Web. Team requests and status sync are right for Slack.
Same quality standard
No matter where the entry point is, adhere to plans, permissions, validations, diff reviews, and risk descriptions.
Complete usage points
Supplement the core concepts, operation sequences, permission boundaries and verification requirements that are easily compressed and missed in official documents, making it easier for English readers to learn completely by page.
Platform selection supplement
Claude Code is available on multiple platforms, but each platform has different contexts and permissions. Ask three questions when choosing an entry: what context is required for the task, where does verification occur, and who approves high-risk actions.
- CLI: local repository, real commands, the clearest engineering verification.
- IDE: current file, selection, inline diff, small step collaboration.
- Web: Cloud repository tasks, remote PR, multi-device relay.
- Desktop: multi-session, parallel tasks, visual review and local workflows.
- Chrome: real browser, login page, front-end acceptance.
- Slack: Team conversations to initiate tasks and status synchronization.
The quality standards remain the same regardless of the platform: planning, permissions, verification, diff review, risk description.
Study Checklist
Put the content on this page into real tasks and use the five dimensions of entry, context, permissions, verification and team rules to check whether you have truly mastered it.
Study Checklist
After reading this page, do not just remember the concept name. You should be able to place "Platform integration overview" back into a real Claude Code engineering workflow: where the task starts, what context the system loads, which actions need approval, how the result is verified, and how to roll back when it fails.
If this is a portal or platform page, specifically confirm what contexts this portal can access: local files, cloud repositories, browser logins, team messages, external tools, and whether these contexts are sufficient to complete the verification.
- Be able to describe in your own words the specific problem this page solves, rather than just reciting the title.
- Able to write a minimal example task with goals, scope, prohibitions, and acceptance criteria.
- Be able to determine which information should be put into the current prompt and which should be captured as project rules or configurations.
- Be able to explain which long-term rules should go into CLAUDE.md, and which runtime behavior should be handled by settings, permissions, Hooks, Skills and MCP.
- Ability to check diffs, command output, test results, screenshots or PR notes after a task is completed instead of just trusting the natural language summary.
If this page is used for team training, ask learners to complete a small task with Claude Code: read and explain first, submit a plan, make the smallest useful change, and close with real verification commands plus human diff review.