---
name: long-command-check
description: Audit how an agent harness runs long shell commands, covering foreground wait limits, moving to background without re-running, timeouts, completion notification, polling, output size, cleanup and behaviour after compaction. Use when building or reviewing an agent's shell or background-task tool, or when an agent hangs on dev servers, long builds or test runs.
title: long-command-check
canonical_url: https://skilld.dev/gh/minimax-ai/mcode-stack/long-command-check
last_updated: 2026-10-29T09:48:02.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install minimax-ai/mcode-stack/long-command-check`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/long-command-check`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/minimax-ai/mcode-stack/long-command-check) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/long-command-check`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/long-command-check --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/long-command-check --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Long Command Check

For people building agents. The question is simple: when the agent runs a
shell command, should it wait for it to finish? Following that question leads
to a chain of design decisions. Foreground is for fast commands, background is
for long ones, and ideally the same process connects the two.

Companion to MCode Engineering Notes 04, "How long should one bash command
wait". Plain-text checklist: `checklists/long-command.md`.

## Why waiting is expensive

Two costs while the agent blocks on a command:

- The visible one: the user waits and nothing else happens.
- The hidden one: the provider's **prompt cache can expire**. While a command
  runs in the foreground there are no new model requests. If the wait is
  longer than the cache lifetime of the model service you use, the next
  request re-processes the whole prefix: slower first token, higher cost.
  Look up the cache lifetime in your provider's documentation.

Moving work to the background does not keep the cache warm forever. It saves
the time the agent would otherwise spend idle when it had other work to do.

## How to run the audit

Read the shell tool and background-task code of the target agent. For each
item, record the answer with evidence (file and function, config, or a test
you ran). Do not guess; write "unknown" if the code does not show it.

| # | Item | Question |
| --- | --- | --- |
| 1 | Foreground limit | How long does the foreground wait at most? Is that comfortably below the cache lifetime of your model service, leaving room for generation time? |
| 2 | No re-run | When a command moves from foreground to background, is it the same process, or is it killed and started again? |
| 3 | Timeout accounting | After moving to background and reading output, is the deadline reset? (It should not be, or a stuck command can run forever.) |
| 4 | Result delivery | When a background task finishes, does the model learn it from a notification, or only by polling? |
| 5 | Notification position | Is the notification appended at the end, or does it modify an already cached prefix? |
| 6 | Anti-polling | Is blocking wait time capped, and does repeated reading with no change produce a hint to stop polling? |
| 7 | Output size | Is large output truncated or written to a file and read incrementally, rather than pasted whole into context? Is incomplete output labelled as incomplete? |
| 8 | Cleanup | Who stops background tasks when the user stops the agent, when a one-shot headless run exits, and when the process restarts? Are orphaned tasks marked instead of showing "running" forever? |
| 9 | After compaction | Is "a task finished and its result was not read" tracked outside the conversation history (for example a task table), so it survives compaction? |
| 10 | Precondition | If the current environment cannot read background results, is backgrounding disabled? |

## Quick behavioural tests

If you can run the agent, try these and record what actually happened:

1. Ask it to start a dev server and then do something else. Does it hang?
2. Run a command that takes several minutes. Does it move to the background
   without starting a second copy?
3. Start a background task, then stop the agent. Is the task stopped?
4. Let a background task finish, then trigger compaction before reading the
   result. Is the unread result still surfaced afterwards?

## Output

A table of the ten items with pass / fail / unknown and evidence, the results
of any behavioural tests, and the top three fixes.
