Jenny 2.0 adds approved agent plans to Android notebooks Jenny 2.0 adds approved agent plans to Android notebooks

Approval comes before notebook changes

Planning starts inside a notebook chat. Jenny reads its contents and can ask clarifying questions before presenting a proposed sequence. That stage is read-only and excludes web searches; research belongs to later execution steps. Users can remove proposed steps or request a revision before approval. The app then records the notebook’s starting state and advances one step at a time, waiting for each to finish. Other views cannot edit the notebook during execution. A final application-level check looks for broken links, empty pages and missing facts, with up to two repair rounds. Unresolved gaps are recorded separately.

Helpers keep a record of their changes

Outside a running plan, Jenny delegates work to helpers while leaving the main conversation available. Each helper records files before its first write and the content it leaves behind. Stopping a helper presents separate choices to preserve its work or reverse its changes. Notebook boards and reminders are tracked at the individual-card level. A stopped helper can also be left in place while the user decides later whether to undo it. For interrupted work, the continuation mechanism restores the helper’s conversation and recorded activity. A plan manages its own helper continuation, so the user deals with the plan’s controls instead of restarting each worker.

Another browser reaches the same phone

The new remote interface exposes the phone’s existing web interface through Tailscale. Both devices join the same tailnet, and a separate access key travels in the browser link. The listener binds to the phone’s Tailscale addresses instead of every network interface. Users can disconnect remote sessions and rotate the key from the phone. The other device displays the same chats, notebooks and Jenny apps; it does not become a second agent host. Turning remote access off from the browser disconnects that window, and re-enabling it requires access to the phone.

Phone hosting and model hosting are separate

Jenny embeds a Python runtime in an Android application and keeps its agent service running in the foreground. It can also act as the phone’s launcher. Users choose a model provider with their own key, or connect a model server on their own hardware. The project distributes source code and a signed installation package. Version 2 keeps the signing key used by earlier releases, allowing an in-place upgrade that preserves chats, notebooks and settings. Notebook boards replace the previous opening view, arranging subjects, notes, reminders and automations as cards. Android’s cloud backup now excludes Jenny’s data; the release directs users to the app’s backup mechanism.