Run and control tasks
A task is one Claude Code session with its own workspace and conversation. This page covers the choices you make when starting a task and the controls you use while it runs.
#Start a task
Select New, choose a Repository task or a Scratch task (an empty folder), describe the outcome you want and how Claude should check it, then choose:
- Permissions for this task: how much Claude may do without asking you.
- Response style: how much Claude writes while it works.
- Model access (when a CCR gateway is configured): your Claude account or the CCR gateway. See Switch models with CCR.
Permissions and response style are fixed for the life of the task, including after Stop and Resume; to change them, start a new task. Model access can change when you resume a stopped task.
Tasks are new Claude Code sessions. You can't attach a Claude session you started yourself in a terminal; start a new task instead.
#Permissions
| Choice | Behavior |
|---|---|
| Ask for approval | Claude's normal permission rules. Actions that need a decision appear in the app. |
| Accept edits | File edits and common filesystem commands run without asking. Other actions may ask. |
| Auto | Claude reviews actions itself, where your Claude version, model, account and policy support it. It can fall back to asking. |
| Plan only | Claude explores and plans before making changes. |
| Bypass permissions | Skips most checks. You must confirm a warning first. Use only in an isolated environment. |
Permissions reset to Ask for approval for every new task. The task shows Requested permissions, because Claude can still apply its own rules or fall back from Auto. For details on each mode, see Claude Code's permission modes.
Host tasks run with your server user's access. A worktree doesn't limit that, and Bypass is not a read-only mode.
Tasks created before permissions were recorded, and tasks created from Discord, show Host default.
#Response style
| Choice | Behavior |
|---|---|
| Default | Claude Code's normal style, or your server's own outputStyle setting if it has one. Claude explains its work as it goes. |
| Concise | Claude Code's built-in Concise style: leads with the result, skips narration and recaps, keeps simple answers short. The work itself is unchanged. |
Response style is independent of permissions; Concise with Auto is a useful combination. Unlike permissions, your browser remembers your last choice.
#Find what needs you
The task list puts what needs you first:
- Tasks waiting for your approval.
- Tasks that finished a turn or failed since you last opened them on this device.
- Tasks that are working.
- Everything else, such as tasks you've already seen or stopped.
Within each group, the most recently active task comes first. The list shows how many tasks need you, and the installed app shows the same number on its icon where the browser supports it. Opening a task marks it as seen on that device; the first time you open the app on a device, earlier activity counts as seen.
#Answer approvals
When Claude needs permission, the task shows Needs approval and a notice appears above the message box. Select Review request to jump to the request.
Each request shows the tool, Claude's description and the exact command or input. Commands are shown literally, never reformatted. Copy command copies them exactly, and Raw input shows the original JSON.
- Allow once runs that one request.
- Deny refuses it, and Claude continues without it.
After you decide, the notice shows that the decision is waiting for the task to confirm it, then disappears. Interrupting, stopping or restarting a task cancels any open requests.
Pending tool approvals appear directly above the follow-up composer, with the request details and Allow once / Deny buttons together. Multiple requests scroll within that area so the message box stays reachable.
When several requests are waiting, Approve all pending lists each tool and its command, path or query before you confirm the current batch for this session. It skips decisions already queued or being submitted and does not approve requests that arrive later.
#Review changes
For a repository task, select Changes (on the phone, View changes in the task menu) to see what the task changed since it started: commits on its branch, edits not yet committed, and new files, file by file with added and removed lines. Open a file to see its diff, which wraps to fit a phone screen; Copy diff copies it.
The task reports its changes after each turn, and the latest summary stays available after the task stops. Files listed in .gitignore aren't included. Binary files, very large diffs and anything beyond the first 300 files are listed as a summary only, so review those on the server or in the task's branch.
#Open a pull request
When a repository task is idle and has changes, select Create PR. The form starts with the task's title and Claude's latest reply as the description; edit both.
- Commit uncommitted changes first (on by default) commits everything in the task's workspace, using the title as the commit message.
- Open as a draft (on by default).
ccr-cloud then pushes the task's branch, ccr/SESSION_ID, to the repository's origin and runs gh pr create. The task shows the pull request's link, and each task opens one pull request.
This uses the credentials the task already has: in host mode, your server account's Git credentials and gh auth login; in Docker mode, GH_TOKEN. Install the GitHub CLI on the server for host mode. If something fails, such as missing push access, the error appears in the task's activity.
#Send follow-ups
Type in the message box and select Send, or press Ctrl+Enter (⌘+Enter on a Mac). A message sent while Claude is working waits until the current turn ends.
#Stop, resume and delete
| Control | Effect |
|---|---|
| Interrupt turn | Stops the current turn. The task stays ready for your next message. |
| Stop session | Stops Claude and the task's runner. The workspace and conversation are kept. |
| Resume session | Restarts a stopped task, continuing the same conversation and files. With a CCR gateway configured, Resume on can move it to the other model route. |
| Delete | Removes the task, its workspace and its history. The browser app has no delete control yet; use DELETE /api/sessions/:id. |
Closing the browser or the SSH tunnel doesn't stop a task. A server reboot does; see Operate your server.
#Read and copy output
Claude's replies render Markdown: headings, lists, tables, code blocks, quotes and links. Raw HTML is shown as text and remote images aren't loaded. Your messages and tool output are always plain text.
- Copy Markdown copies a reply's original text.
- Copy code copies one code block.
- Copy output copies a tool's full output, even when the screen shows a shortened version. Images in tool output appear as
[image].
If your browser blocks clipboard access, the app tells you to select and copy the text manually.
#Next steps
- Notifications: get approval requests on your phone.
- Switch models with CCR: keep working while you're at a Claude usage limit.
- Access from your phone
- HTTP API: start and control tasks from scripts.