Recoverable Long Tasks and Persistent Python Tools in Aiden

Major Update: Merged Aiden Firmware changes now give your Agent more ways to preserve continuity when a long task reaches a Provider context limit, a tool returns a large saved result, or Python dependencies need to survive beyond one session. Together, these changes reduce avoidable repeated work and help retain useful task state without overstating what recovery can guarantee.

When long tasks reach a Provider context limit

A long-running task can accumulate enough conversation and tool context to exceed a Provider’s context limit. With PR #497 and PR #498, the Agent now has a defined response to that specific interruption.

When a Provider returns a context-limit error, the Agent can compress its working context, move to a new session, and retry the work once. Instead of immediately ending the task at the limit, your Agent has an opportunity to resume with a more manageable context.

This recovery path is intentionally bounded and does not guarantee that every interrupted task will finish. The Provider response, the state of the work, and other errors still determine what happens next. The merged changes simply provide a structured way to attempt continuation after the context-limit case they address.

How large tool result recovery preserves completed work

A tool can finish meaningful work before its output becomes difficult to carry forward in a single context. PR #530 introduces large tool result recovery so the Agent can use saved result details instead of automatically repeating an operation that has already run.

The Agent can recover a saved large tool result’s continuation ID, status, error details, and output tail. These fields give it practical information for deciding what to do next: a continuation identifier where the underlying operation supports one, the prior result state, relevant error context, and the final portion of output that shows the most recent activity.

For your workflows, that can mean a recovery attempt starts from what the tool already accomplished rather than reflexively invoking the same work again. This is particularly useful when repeating an action would be slow, costly, or disruptive.

It also supports more recoverable AI agent tasks by retaining the state your Agent needs to make a better continuation decision. The recovered fields may still be incomplete for a particular Provider or failure mode, but they can help avoid duplicate work when the result supports a continuation path.

Persistent Python dependencies across sessions and restarts

Continuity also depends on whether the working environment remains available after a session ends. PR #505 changes the location for Python packages installed through Aiden’s existing Shell tool. Packages are stored under /userdata/agent/python.

That location allows the Agent service and the login shell to reuse installed packages across Agent sessions and device restarts. You can avoid reinstalling the same dependencies solely because a session closed or the device restarted, making repeat work more consistent when your task depends on Python tooling.

The Shell tool remains the installation path. This merged firmware change does not add a package-install tool, virtual environments, or lock files. It focuses on retaining the user-level Python package base so dependencies can remain usable under normal conditions.

There is an important boundary to plan for: StorageMonitor may clear the Python user base in an emergency. The packages are persistent when storage permits, not immutable. If a workflow relies on particular dependencies, you should account for the possibility that emergency cleanup may require reinstallation.

Three connected improvements to Aiden Firmware continuity

These changes address different points where an otherwise useful task can lose momentum. Context compression and a one-time retry address a defined Provider limit. Saved-result state helps the Agent avoid repeating completed tool work. Persistent Python packages keep more of the task environment available across sessions and restarts.

They are merged Aiden Firmware changes, not a universal production rollout or a guarantee of completion on every device. Their practical value is more measured: when the relevant conditions are present, your Agent has better state to work from and a clearer path to continue.

Follow Aiden’s project progress for future firmware updates and the next set of reliability improvements.