A Few Session Controls Make Claude Code Easier

The first Claude Code skills worth learning are not elaborate prompting tricks. They are the controls that let you inspect a session, manage its working context, and decide when the assistant should stop and ask. A small set of slash-menu features makes those decisions easier.

Think of the slash menu as a control panel rather than another programming language. This introduction describes its useful entries in plain English, without syntax to memorize. Availability can change between releases, so your installed version’s help remains the best starting point.

Built-in help makes the available controls discoverable

Start with help. It shows the controls available in your current environment, including features that may depend on your installation or account. This matters because an older tutorial can describe a menu that differs from yours.

You do not need to learn every entry. First identify the controls for help, session information, context management, permissions, and recovery. Return to the menu when you encounter a specific problem instead of treating it as a checklist to finish.

Status and context answer different session questions

The status view helps you inspect the session’s configuration. Use it when you are uncertain about the active setup rather than asking the assistant to guess its own environment.

The context view addresses a different concern: the information occupying the conversation’s working space. Long discussions, inspected files, and tool results all compete for limited room. Checking context can explain why a session needs housekeeping, although it is not a guarantee that every earlier detail remains equally accessible.

Learn the distinction early: status concerns the session’s setup; context concerns the material the assistant is carrying forward.

Compacting and clearing serve different working needs

Compact is useful when you want to continue the same task with less conversational baggage. It condenses the conversation so work can proceed without retaining the entire exchange in its original form. Important details can be compressed away, so restate critical requirements when necessary.

Clear is better suited to a genuinely fresh conversation. Use it when you are changing tasks and old assumptions would be distracting. Clearing the conversation does not undo edits already made to your project.

A practical rule is to compact when the goal stays the same and clear when the goal changes. Neither replaces reviewing the actual state of your work.

Permissions and recovery deserve attention before automation

The permissions controls help you inspect and manage the actions Claude Code can take. Before relaxing approvals, understand the scope of the permission you are granting. Permission to inspect information and permission to run actions with side effects deserve different levels of caution.

The rewind feature provides checkpoint-based recovery for supported conversation and file changes. Learn its options before you need them. It is not a universal undo button: external effects, such as changes to remote systems, are not automatically reversed. Keep version control and ordinary backups in your workflow.

Cost awareness belongs beside basic session housekeeping

Where available, the cost view offers useful session-level usage information. Treat it as an operational aid, not necessarily your final invoice. Billing depends on your access method, and a relay’s records may be needed to reconcile charges.

BestRelay, this article’s publisher, is a quality-first API relay that forwards requests to the official model named in each request, without substitution. It supports Claude Code, Codex, Gemini CLI, and OpenAI SDK clients. Its pay-as-you-go billing uses provider-reported token counts, with cache reads and writes priced separately. Members can also earn referral commission when invited users top up.

Create a BestRelay account if that access model suits your workflow.

For your first sessions, keep the routine small: consult help, check context before it becomes crowded, and understand permissions before granting broader access. Those habits matter more than memorizing every menu entry.