Devotd Github
NewAI agents

abacusai/abacusai-bot — Restoring routine/bot folder kinds and reclaiming stale records

abacusai/abacusai-bot adds a patch that restores the kinds of the routine/bot folders that used to vanish on every restart, and moves routine run records that had gone stale into another folder back to their original location.

Repositoryabacusai/abacusai-bot ↗

abacusai/abacusai-bot adds a patch that restores the kinds of the routine/bot folders that used to vanish on every restart, and moves routine run records that had gone stale into another folder back to their original location.

GitHub description: 100% free, open-source personal agents for your messaging apps, tools, and services

stars
★ 217
Forks
35
Language
TypeScript
License
MIT
Latest release
v1.1.5
Read original source ↗View on GitHub ↗

abacusai/abacusai-bot is a desktop project that distributes personal agents for messaging apps, tools, and services as free open source. The commit of November 5, 2026 (e1ccbb7, pull request #676) deals with the problem of the kinds of the folders the app manages for itself disappearing on every restart. Unless a workspace's kind is 'auto', it is discarded each time it runs and is stored in that state in the listing, so routine folders and bot folders read like projects the user picked directly.

The flow of the bug is this. The first run of one routine made its own folder the active workspace, and the next routine created in the still-open conversation inherited that identifier unchanged. After a restart, this routine ran inside another routine's folder and was recorded as if it were running for the first time, and the run history and notes split into two places. This patch preserves the kind and restores folders that have already lost their kind from their path. Routine folders and bot folders no longer occupy the active workspace slot.

The newly added reclaimRoutineRecords moves the run record file of a stale folder back to its original home, concatenates the note files on both sides, keeps only the newer of the last run records, and then deletes the stale folder. If it fails, it leaves only a warning and retries on the next run. The changes are limited to the desktop app's workspace service and the routine store, and amount to 213 added lines and 6 deleted lines across 5 files in total. Verification was added as vitest tests.

That said, the commit message cites the Windows file-name restriction as the reason for not putting a colon in the session identifier of run records. What results this produces in an actual Windows environment is not in this commit's information. No user counts or performance figures are given either. It is close to a bug fix that narrows and corrects one type of folder misidentification.