# CLAUDE_CODE_DISABLE_BACKGROUND_TASKS

> Set to 1, it keeps each command and helper in front.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1

## Think of it like

It is like you ask a helper to finish one job. Then they start the next.

## Definition

CLAUDE_CODE_DISABLE_BACKGROUND_TASKS set to 1 stops Claude from running shell commands and subagents in the back. Ctrl+B stops working, and slow jobs are no longer moved to the back on their own. MCP tasks and the Monitor tool still run in the back. Background sessions have their own switch.

## Example

Lucy's CI logs got confusing when jobs ran in the back. She sets this, and every step now finishes in order.

## Example code

```bash
export CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1
claude
```

Run every job in front, one at a time.

## Why it matters

Jobs in the back are fast but hard to follow. In some places, order matters more.

## Common mistake

Expecting it to stop background sessions too. Those have their own switch.

## Three principles

- **No background shells.** Or subagents.
- **No Ctrl+B.** When set.
- **MCP tasks still run.** In the back.

## Related terms

- [Bash Tool](https://learn.benibix.com/term/ai/bash-tool)
- [/background Command](https://learn.benibix.com/term/ai/background-command)
- [Monitor Tool](https://learn.benibix.com/term/ai/monitor-tool)

---

Source: https://learn.benibix.com/term/ai/claude-code-disable-background-tasks-variable
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-16
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
