Practice — Claude Code Platforms and Interfaces (12 questions)

For each scenario below, name the Claude Code surface (or combination of surfaces) you'd recommend, and justify the choice using the concrete capabilities and limitations of that surface — not just a vibe.

1. A developer is on a train with only their phone, and needs to check whether a bug fix they kicked off before leaving the office has finished, and possibly redirect it if it went down the wrong path.
2. A teammate wants to review a large, multi-file refactor PR, leave comments on specific lines, and have Claude address them, all without leaving a GUI.
3. A CSS bug report says "the pricing table overlaps the footer on narrow viewports" with a screenshot attached.
4. An engineering lead wants to demo a newly finished feature live to non-technical stakeholders in a meeting, showing the working app, not code.

A developer runs a single Claude Code CLI session that does the following, in order:

1. Edits src/parser.ts using the Edit tool (prompt 1).
2. Runs rm -rf build/ via Bash to clear a stale build directory (prompt 2).
3. Edits src/parser.ts again, plus creates a new file src/parser.test.ts with the Write tool (prompt 3).
4. Spawns a background subagent that reviews the whole src/ folder and, using its own Edit tool, fixes a lint issue in src/utils.ts (prompt 4).

The developer decides prompt 3's approach was wrong and runs /rewind, selecting the checkpoint just before prompt 3 and choosing "Restore code and conversation."

1. Walk through what state each of the four changes above ends up in after this rewind: which are reverted, which survive, and why, referencing specifically what checkpointing does and does not track.
2. The developer is surprised that build/ is still missing after the rewind. Explain precisely why, and what they'd need to do instead to get it back.
3. Explain why /rewind is not a substitute for committing to git during this same session, using this exact scenario as the evidence.

Two engineers on the same team start fresh Claude Code sessions with default settings — one is on a Team plan, the other on a plan that isn't Pro/Max/Team.

What permission mode does each one actually start in?

You install the Claude Code VS Code extension and use its panel successfully. Then you open the integrated terminal and run claude mcp add, and the shell reports command not found: claude.

Why?

Both the VS Code extension and the JetBrains plugin run a local, hidden MCP server for IDE integration, exposing a diagnostics tool. VS Code additionally exposes a tool for running Python in an active Jupyter kernel.

What does the JetBrains plugin expose in that same slot?

Mid-session, Claude runs rm old-config.json via Bash to clean up, then makes several more changes to other files using the Edit tool. You open /rewind and restore code back to before all of this.

What happens to old-config.json?