Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Aider error

Aider: Exception: Application is not running. Application.exit() failed

Error message
Exception: Application is not running. Application.exit() failed.

Status: Fixed in releaseLast verified 1 documented fix2 sources

What it means

With --watch-files, the file-watcher thread crashed while trying to interrupt the input prompt. In issue #2716 the reporter traced it to TERM=dumb, for example when running aider inside an Emacs interface. The maintainer explained that watching for file changes needs to be able to interrupt the input prompt.

Causes

  • Running --watch-files in a dumb terminal (TERM=dumb), where the prompt cannot be interrupted (issue #2716).

How to fix it

  1. Fix 1.

    Upgrade to v0.71.0 or later. The v0.71.0 release notes say: "Turn off fancy input and watch files if terminal is dumb." The issue was marked fixed on Jan 10, 2025.

    Terminal
    python -m pip install --upgrade aider-chat

More Aider errors

All 17 Aider errors

FAQ

What does "Exception: Application is not running. Application.exit() failed" mean in Aider?

With --watch-files, the file-watcher thread crashed while trying to interrupt the input prompt. In issue #2716 the reporter traced it to TERM=dumb, for example when running aider inside an Emacs interface. The maintainer explained that watching for file changes needs to be able to interrupt the input prompt.

How do I fix "Exception: Application is not running. Application.exit() failed"?

Upgrade to v0.71.0 or later. The v0.71.0 release notes say: "Turn off fancy input and watch files if terminal is dumb." The issue was marked fixed on Jan 10, 2025.

Is this Aider error fixed?

Status: Fixed in release. A release fixed this. The affected versions note says where the fix landed. Affected versions: Reported on v0.70.0 and v0.70.1.dev; addressed in v0.71.0.

Sources

Last verified against 2 sources: official docs, maintainer replies and release notes.

Newsletter

Fixes for the tools you use, weekly

One email per week. New coding agent releases, what broke, and how developers are working around it.