Repository navigation
Connapse v0.4.2
Connapse v0.4.2
Approve an agent's delete and Connapse carries it out. The agent no longer has to repeat it.
If your agent waits with approval_status and then repeats a held delete, change it to read the batch with deletion_status instead and not repeat the call.
What's changed
- Every held delete is a batch Connapse carries out. When an agent's token asks before deleting, a single delete now works like
request_deletions: deleting a file, a folder, an empty container, a memory space or a memory fact, or up to 50 files at once, puts a batch on the Approvals page. Once you approve it, Connapse deletes the approved items itself, skipping anything that changed since the agent asked, and the agent reads each outcome withdeletion_status. In v0.4.1 the agent had to wait for your approval and then repeat the call. request_deletionsalso takes empty containers and memory facts.- Held calls that aren't deletions of your knowledge, such as setting a credential or removing a user, still work as before: the agent waits with
approval_statusand repeats the call once you approve it. - One tool each for reading, uploading and deleting files, one file or many.
get_documentnow reads up to 50 documents at once,upload_fileuploads up to 100 files, anddelete_filedeletes up to 100, or up to 50 when the delete is held for approval, since a batch holds at most 50 items. They replaceget_documents,bulk_uploadandbulk_delete, which still work and give the same results but no longer appear in the tool list an agent loads. Those three old names will be removed after the 0.4.x releases, so switch any scripts or agent prompts that use them. - A memory save now also lists the current facts with the same subject and attribute, so an agent sees what's already there; nothing is refused.
Fixed
- Approving a held delete now skips a file that was replaced after the request, even with the same size and type.
- The warning "Could not check memory sources" no longer appears in the log after startup when a memory space page opens (#1201, reported by @marcusyoung). The counts you saw were never wrong.
deletion_statusnow shows a token its own batch as its own ("isYours": true); it saidfalsebefore.upload_fileacceptsfilesas a list, not only as a string holding one, and a wrongly shapedfilesgets an error that shows the expected shape.
Dependencies
- PDFium, which renders PDF pages, 159.0.8138 → 159.0.8152.
- Anthropic SDK 13.3.0 → 13.8.0.
- AngleSharp, the HTML parser, 1.9.0 → 1.10.3.
- AWS SDK 4.1.0, which Connapse uses for S3 and MinIO storage and AWS sign-in.
- ASP.NET Core JwtBearer, which checks sign-in tokens, 10.0.7 → 10.0.15 (a servicing patch), with the Microsoft.IdentityModel packages 8.18.0 → 8.19.2.
For MCP clients that hardcode tool names
upload_file, get_document and delete_file keep their names. Only the multi-file tools changed:
| Old name | Use now |
|---|---|
get_documents |
get_document with files (up to 50) |
bulk_upload |
upload_file with files (up to 100) |
bulk_delete |
delete_file with fileIds (up to 100, or 50 when the delete is held for approval) |
The old names still work in v0.4.2 and return the same results, but they are no longer in tools/list, so a client that checks the list before calling won't find them. They will be removed after the 0.4.x releases.
Upgrade
If you started Connapse with the README's one-command start (docker compose -f oci://ghcr.io/destrayon/connapse:compose up -d -y), follow Upgrade Connapse instead of the steps below. If you run a downloaded docker-compose.yml, first make a backup with Back up and restore Connapse, since this release runs a migration and rolling back means restoring it. Then:
# in .env
CONNAPSE_VERSION=v0.4.2docker compose pull web
docker compose up -dFrom v0.4.1 there is no change to docker-compose.yml. One migration adds a column to the documents table; it runs when the app starts. From an older version, follow Upgrade Connapse, which covers each release in between.
Every change is in the changelog.
Full changelog: v0.4.1...v0.4.2