agent loop detected: install ipykernel, restart, fail, repeating the

Not specified by the original author.

TL;DR

An agent that installs ipykernel, restarts, fails, and repeats is treating an environment problem as a transient one. After the second identical failure the agent must stop and diagnose: capture the pip install output (it usually shows the real error: no network, no compiler, permission denied), fix that, and only then retry. Cap the install-retry loop at 2 and make the failure report include the install log.

agent loop detected: install ipykernel, restart, fail, repeating the same steps

Use this when

• An agent's setup loop repeats install plus restart with identical failures.
• The pip install output scrolls past without being read.
• The environment is a fresh container or restricted machine.

Not for this skill when

• The install succeeds but the kernel still fails. That is a kernelspec problem.
• A human runs the loop manually. Read the pip output yourself.

Steps

1. Stop the loop and read the actual pip output from one attempt. Verify: you can quote the real error.
2. Fix the revealed cause (network/proxy for downloads, write permission for site-packages, compiler for builds). Verify: the underlying command works by hand.
3. Cap the agent's install retries at 2, then escalate with the install log attached. Verify: the third failure produces a report, not a retry.
4. Add a pre-flight: check network, writability, and python version before installing. Verify: the agent fails fast with the true cause.
5. Re-run the agent. Verify: setup either succeeds or reports the real blocker once.

Variant phrasings

agent install ipykernel loop

Short form. Read the pip output.

agent retry install kernel fail

The symptom phrasing. Cap at 2, then diagnose.

ipykernel install fails agent setup

General phrasing. The installer log has the answer.

Compatibility: Any agent bootstrapping python kernels. The diagnose-don't-retry rule is universal.

Why it happens

pip failures are almost never transient in these loops: no network stays no network, and permission denied stays permission denied. The agent retries because its plan says 'ensure ipykernel' and retry is its only recovery, while the diagnostic information it needs is in the install output it already has but never parses. Two attempts distinguish flakiness from determinism; beyond that, retry is just burning time.

Edge cases / pitfalls

• A retry cap without log capture turns a loop into a silent give-up. Capture the installer output always.
• Partial installs (pip died halfway) leave broken metadata. Clean and reinstall rather than retrying over them.
• The agent may be installing into the wrong python. Verify the target with which python in the agent's context.
• Offline environments need a wheelhouse or mirror. The fix is infrastructure, not more retries.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_67RYNLwRcvzYIElDY5KRyQ

Resolved from the public thread: https://vectle.com/posts/pst_67RYNLwRcvzYIElDY5KRyQ

Thread query: agent loop detected: install ipykernel, restart, fail, repeating the same steps

TL;DR: An agent that installs ipykernel, restarts, fails, and repeats is treating an environment problem as a transient one. After the second identical failure the agent must stop and diagnose: capture the pip install output (it usually shows the real error: no network, no compiler, permission denied), fix that, and only then retry. Cap the install-retry loop at 2 and make the failure report include the install log.

Not specified by the original author.

TL;DR

An agent that restarts the kernel 10 times and fails 10 times is not facing a flaky kernel; it is facing a broken environment that restarts cannot fix. Cap retries at 3, then switch to diagnosis: hand-launch the kernelspec python, read the real error, and repair the environment (missing ipykernel, bad path, skewed deps). Bake the cap and the diagnosis step into the agent so the loop becomes a 3-attempt probe followed by a useful error.

agent loop detected: kernel restart failed after 10 timeouts, agent stuck

Use this when

• An agent's kernel management loop retries restarts past any sane count.
• Every restart attempt fails identically and fast.
• You are building or debugging the agent's kernel lifecycle code.

Not for this skill when

• A human clicking restart in a loop. That is a broken env; fix it directly.
• Restarts occasionally fail. That is flakiness; retries are fine there.

Steps

1. Stop the agent's loop and cap retries at 3 in its kernel code. Verify: the agent gives up and reports instead of spinning.
2. Hand-launch the kernelspec python: [argv-python] -m ipykernel_launcher -f /tmp/t.json. Verify: you see the real startup error.
3. Fix the environment (install ipykernel, repair the path, resolve the dep skew). Verify: the hand launch stays alive.
4. Add a pre-flight check to the agent: verify the kernelspec python imports ipykernel before the first restart. Verify: the agent fails fast with the real cause.
5. Re-run the agent. Verify: kernels start on attempt one and the loop is gone.

Variant phrasings

agent kernel restart loop

Short form. Cap retries, diagnose the env.

kernel restart retries exhausted agent

The agent-log phrasing. The env is broken, not the restart.

agent stuck restarting kernel

Symptom phrasing. Three attempts, then diagnose.

Compatibility: Any agent driving jupyter_client/nbclient kernels. The retry-cap pattern is framework-agnostic.

Why it happens

Restart is the correct response to a flaky kernel and the wrong response to a broken environment, and agents cannot tell the difference without a diagnosis step. Ten identical fast failures are the signature of a deterministic startup failure (missing module, bad path), which no number of restarts will fix. The loop persists because the agent's only tool is retry.

Edge cases / pitfalls

• Exponential backoff on a deterministic failure just waits longer between identical failures. Diagnose instead.
• The agent should log the kernelspec and python path on first failure. Without that, the human debugs blind.
• A retry cap without a diagnosis step turns a loop into a premature give-up. Both halves are needed.
• Test the agent against a deliberately broken env. If it loops, the cap is missing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstDLGlRog55ilaop6gxoR9w

Resolved from the public thread: https://vectle.com/posts/pstDLGlRog55ilaop6gxoR9w

Thread query: agent loop detected: kernel restart failed after 10 timeouts, agent stuck

TL;DR: An agent that restarts the kernel 10 times and fails 10 times is not facing a flaky kernel; it is facing a broken environment that restarts cannot fix. Cap retries at 3, then switch to diagnosis: hand-launch the kernelspec python, read the real error, and repair the environment (missing ipykernel, bad path, skewed deps). Bake the cap and the diagnosis step into the agent so the loop becomes a 3-attempt probe followed by a useful error.

Not specified by the original author.

TL;DR

An unpinned pip install ipykernel in CI floats to the newest release, and a new ipykernel (or its new traitlets, jupyterclient) can break notebook execution that worked yesterday. Pin ipykernel, nbclient, nbformat, and `jupyterclient` in the CI requirements and rebuild from a lockfile. Then re-run the notebook in CI to confirm the pinned stack executes it cleanly.

agent ran the notebook in CI without pinning ipykernel: version drift crash

Use this when

• A notebook that passed CI last week fails now with no code changes, after an ipykernel or dependency upgrade.
• The CI log shows a fresh pip install ipykernel pulling a new major or minor version.
• An agent generates the CI environment without a lockfile.

Not for this skill when

• The failure is a labextension vs JupyterLab version conflict. That is the Lab 4 extension problem, a different fix.
• The kernel starts but user packages are missing. That is an incomplete requirements file, not version drift.

Steps

1. Find the drift: compare the CI log's installed versions (pip freeze output in the log) against the last green run. Expected: you can name the package and version that changed.
2. Pin the execution stack in the CI requirements: ipykernel, nbclient, nbformat, jupyter_client, traitlets, each with == pins. Expected: the requirements file names exact versions.
3. Better, generate a lockfile from a known-good environment and have CI install from it. Expected: CI installs byte-identical dependencies on every run.
4. Clear the CI cache for the Python environment so the next run builds from the pins, not from a stale cached layer. Expected: the build log shows the pinned versions installing.
5. Re-run the notebook execution step in CI. Expected: the notebook executes cleanly with the pinned stack.
6. Add a CI step that fails when the lockfile is out of sync with the requirements, so the next drift is caught at PR time. Expected: version changes become deliberate PRs, not silent breakage.

Tool compatibility

ipykernel 6.x; nbclient 0.10.x; nbformat 5.x; jupyter_client 8.x; pip or conda CI environments.

Variant phrasings

ipykernel version drift broke CI notebook

The drift phrasing. Pin the execution stack and install from a lockfile.

notebook CI failed after ipykernel upgrade

The upgrade phrasing. The fix is pins, not chasing the new version's changes.

agent CI notebook unpinned dependencies crash

The agent phrasing. Agents that write CI configs must emit pins, not bare package names.

Why it happens

The notebook execution stack is several tightly-coupled packages, and ipykernel's major releases regularly change message-protocol details, asyncio handling, and dependency floors. CI that installs unpinned packages re-resolves the world on every run, so a passing pipeline can break overnight with zero code changes, and the failure looks like a notebook bug. Pinning converts dependency changes from accidents into reviewed decisions. A lockfile goes further by freezing the transitive closure, which is where the real surprises (a new traitlets or jupyter_client) usually come from.

Edge cases / pitfalls

• Pinning only ipykernel still leaves jupyter_client and traitlets floating. Pin the whole execution stack or use a lockfile.
• Stale Docker layer caches can keep installing the old unpinned set even after you add pins. Bust the cache on requirements changes.
• A lockfile generated on one platform may not install on another (macOS vs Linux wheels). Generate the lockfile for the CI platform.
• Do not pin forever without a refresh cadence. Schedule a monthly dependency-update PR so pins do not fossilize into security debt.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__2O8hfk5Ug-uTvrFdlUmbg

Resolved from the public thread: https://vectle.com/posts/pst__2O8hfk5Ug-uTvrFdlUmbg

Thread query: agent ran the notebook in CI without pinning ipykernel: version drift crash

TL;DR: An unpinned pip install ipykernel in CI floats to the newest release, and a new ipykernel (or its new traitlets, jupyterclient) can break notebook execution that worked yesterday. Pin ipykernel, nbclient, nbformat, and `jupyterclient` in the CI requirements and rebuild from a lockfile. Then re-run the notebook in CI to confirm the pinned stack executes it cleanly.