Repository navigation
Support Dakera 0.12.4 - #157
Draft
ferhimedamine wants to merge 2 commits into
Draft
ferhimedamine wants to merge 2 commits into
ferhimedamine wants to merge 2 commits into
Conversation
- dk memory forget: --about, --request, --until, --min-score, --limit, --restorable, --dry-run; several ids; refused before sending on a server older than 0.12.4, which would ignore them and delete - dk memory forget-detect, dk memory trash, dk memory restore - store / batch-store report requests to forget and near-duplicates - recall shows standing instructions, associated memories and degraded parts; --include-associated[=BOOL] - memory get --projection-days, session end --auto-summarize with summary_pending, extract shows the extractor and its warnings - 202 "applied, not stored yet" answers reported by keys delete|deactivate, admin quotas-set and backup-delete; keys delete no longer claims success before the answer - consolidate: --dry-run and --type were never read by the server (a "dry run" merged); both refused, --ids/--threshold/--target-type sent instead - hints for the new 503/409 answers and Dakera Cloud key refusals - dakera-client 0.12.3; version 0.8.3 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DKmYrmGxPEHfmA624vFLcd
…e 0.12.3 dk memory forget now prints "Forgot N memories of '<agent>'"; the container test still looked for "Deleted" and failed on the self-hosted runner. The integration service moves from engine 0.12.0 to 0.12.3, the newest released image (0.12.4 once it is published). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support for Dakera server 0.12.4 in
dk(0.8.3). Draft: do not merge before the 0.12.4 engine release.Added
dk memory forgetby description (--about,--min-score) and by a user's request to forget, in any language (--request, shows how the server read it), with--until,--limit,--restorable,--dry-run; several ids allowed. On a server older than 0.12.4 these options are refused before anything is sent (an older server ignores them and would delete).dk memory forget-detect <message>...(POST /v1/memory/forget/detect,--file).dk memory trash <agent>/dk memory restore <agent> <id>(restorable deletions).memory store/batch-storereport texts that read as requests to forget and near-duplicates not stored.memory recall: standing instructions, associated memories (on by default since 0.12.4) anddegradedparts;--include-associated[=BOOL].memory get --projection-days,session end --auto-summarize(+summary_pending),memory extractshows the extractor and its warnings,namespace policy getnotesstored: false.Fixed
dk memory consolidate --dry-runmerged the memories: the server never readdry_run(normemory_type). Both are now refused;--ids,--threshold(sent only when given) and--target-typeare sent and the result is read from the server's answer.dk keys deleteprinted "deleted" before checking the answer.202"applied, not stored yet" answers are reported for key delete/deactivate, quotas-set and backup-delete.memory store/batch-storeis one document; notes go to stderr.Other
dakera-client0.12.2 → 0.12.3. This supersedes Dependabot chore(deps): bump dakera-client from 0.11.102 to 0.11.106 #145 (0.11.102 → 0.11.106, older than whatmainalready uses).POST /v1/memory/forget/detect); a test asserts no command calls the Dakera Cloud tenant routes.Tests
cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo test: 187 unit, 48 integration (26 live-server tests ignored), 3 route audit, 84 + 26 + 18 earlier version suites, 21 newtests/v0124.rs(mock server). Not run against a live 0.12.4 server.Update (2026-11-04)
Forgot 1 memory, and CI's server image moved from engine 0.12.0 to 0.12.3 (the newest released). Every job that runs on the self-hosted runner passes, the container integration test included;plan(cargo-dist) is refused by GitHub before starting (billing lock).dk0.8.3 builds ondakera-client0.12.3 and calls the 0.12.4 routes over raw HTTP. Oncedakera-client0.12.4 (dakera-rs #172) is on crates.io, moving to it can replace those raw calls (a follow-up, not needed for this release).🤖 Generated with Claude Code