# magi-code 0.101.0
## New features
### Background shell jobs
Agents can run development servers, watchers, and long builds without blocking a turn.
**How to use:** Ask the agent to start a background job. It uses `bash` with `background: true` and manages output and termination through `bash_job`. Each session supports four running jobs. Jobs survive Esc and turn completion but stop when their owning session ends.
In the primary conversation, open `/background-jobs`, select a job with Up/Down, and press `k` to stop it.
### Concurrent Code Mode batches
Code Mode can run independent inspection calls concurrently while returning results in input order.
**How to use:** With Code Mode enabled, use `tools.callAll([{name, args}, ...])` for up to 32 calls. Each call needs its own `args.intent`. Eligible inspection tools share four workers. Mutations and other tools remain sequential; configured hooks keep the entire batch sequential.
### Settings navigation and skill controls
`/settings` now opens on Agent settings. Categories start collapsed; select one and press Enter or Space to expand it. Collapsing preserves unsaved edits.
**How to use:** Open Knowledge → Skill Directories for **Refresh Skills** and **Enable/Disable Skills**. Refresh rescans saved directories without restarting; save directory changes first and wait for active agent work to finish. Save or discard drafts before opening Enable/Disable Skills.
Compaction and fallback context settings now sit under Agent settings, Subagents under Tools, and summaries, session titles, and integrations under Optional Features.
## Fixes
- Retry transient provider overloads before response progress and honor server-requested waits up to 60 seconds. Cancellation remains responsive, and partial output is preserved.
- Answer MCP server pings and refresh tool lists at user-turn boundaries when supported by the server. Failed refreshes retain previous tools.
## Other changes
- Hide verbose metadata rows in Bash, Code Mode, Read, Find, Grep, and Magi Control transcript cards. Tool output and underlying metadata remain available.
- Reserve session event IDs in blocks to reduce counter-file writes. IDs remain unique but are not chronological.