Changelog

0.7.0

An Improve request’s attempts stay on this device as drafts. Only the version it ends on becomes a version, so the app shows v0, v1, v2 with no gaps, and two requests no longer leave six versions behind.
The latest version runs by default. Adopting one, at the end of an Improve request, is what commits it and makes it current, and a pin made in the app still overrides it.
A version that passes its checks can replace one that fails a validity check, such as one that saw data from after a replay’s cutoff.
A skill saved from a task runs without recording to Dobi. Say “log this” to record one run, or save it with logging on.
A sync after a run tries once more after a brief outage, such as a restart, and says nothing when the work will just go at the next sync. dobi_status says when a newer plugin is out.
If Dobi can’t be reached, a skill runs the version last chosen in the app, not this device’s own choice, and says so.

A sync after a run checks only the tasks with something new, so it no longer slows down as tasks pile up. dobi_sync still checks every task.
dobi_make_private makes a task Private even after it uploaded: this device stops uploading at once, proves it holds the task, and Dobi deletes its copy of the text within a day. Hashes, verdicts and token counts still sync. dobi_save_task with private: true does the same for an uploaded task, instead of refusing.
Delete task, at the end of a task’s Setup tab in the app, removes it from Dobi. A task deleted there stops syncing and running on this device, and says so once. Its files stay on the computer.

Token counts include the request that finished a recording. Claude Code writes that request to disk only after it ends, so Dobi missed it every time, including when it wrote the deliverable. Recording the run now counts it.
A helper agent that finished, whether it reported back mid-turn or after a follow-up message, no longer shows as unfinished.
Dobi assigns the recording ID when the agent leaves it out, and refuses one it made up, with a message that says what to pass. dobi_status lists recordings still open, and where new tasks go.
“Don’t upload this one” works: dobi_save_task takes private: true, and dobi_tasks shows each task’s mode.
dobi_record_run takes the deliverable as a file from the working folder, so a long draft isn’t sent twice, and the run holds exactly what the person got. A recorded run returns a link to its task in the app.
A saved version can’t be replaced by another under the same ID.
A task pinned to one version says so, and so does a skill exported from it. The export lists the files that version names instead of claiming nothing is missing.
An argument error names the field and what it takes. Messages no longer say to sync something that already synced, and connecting says how long the code lasts instead of a UTC time.
The skill keeps Dobi to one plain line in replies, with the app link, and says when to keep content capture off.

Every message Dobi shows when a sync stops now links to a troubleshooting page that exists, and the plugin’s homepage and the docs links in its README work. Until Dobi has its own domain they’re on the staging site.
The skill’s reference says what syncs: a Private task sends records only, and a Synced task also sends its name, inputs, outputs, traces, reviews and adoptions. It no longer says content doesn’t sync yet.
The plugin’s icon is Dobi’s pebble.
A refusal that needs a fresh sign-in says so, and no longer mentions a passkey: Dobi doesn’t use them.

Without connecting, a device keeps its tasks and runs to itself, as the README says. Before, it asked to pair first.
An example’s input and expected answer reach your agent inside an <untrusted-example> fence, stripped of anything a person couldn’t see, and the agent is told to read them as data. An example changed in the app can’t instruct the agent.
Notes and names from the app lose invisible and direction-changing characters too, and the sync report shows only codes from Dobi’s own table.
Capture: Claude Code 2.1.318 is measured, and its new transcript rows are known.

Each new task carries a check made from its own key, and Dobi refuses a raise or a key that doesn’t match it. So a device connection someone copied, without this computer’s files, can’t take over a task. Tasks from earlier versions get their check at the next sync.
A task that was sent before and loses its mode file goes back to Private, instead of following the account’s default.
What Dobi’s service says about a version or a review is checked before your agent sees it.
A revoked connection says it “ended or expired”.
Capture: request snapshots in older transcripts aren’t counted twice, a subagent ID that isn’t one never reaches the agent, and a capture that couldn’t be finished isn’t offered.

Runs on the system’s Python 3.9 or newer, with nothing to install. The setup step is gone.
Installs from the plugin’s repository as a marketplace, in Claude Code and Codex, as dobi@dobi.
Local data and credentials are owner-only files under ~/.local/share/dobi. A 0.5.0 store, which was encrypted, can’t be read, and is left as it was.
Messages say “Tell your agent: connect Dobi”, and link here.