Skip to content

Releases

SoraAgent 0.3.1

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 17 Nov 12:42

0.3.1 is a small recall relevance fix on top of 0.3.0.

  • The daily LIKE fallback now uses OR semantics and ranks by matched-token count instead of requiring every query token as a substring. CJK and mixed-language queries no longer miss otherwise matching messages.

Everything else is unchanged from 0.3.0.

SoraAgent 0.3.0

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 17 Nov 10:27

0.3.0 is a broad state, memory, and security release.

Added

  • Session state is wired into sora chat, sora-gateway, and the SoraDesk bridge. Each conversation gets a hashed state id and the state document is injected into the leading system block. features.state, paths.state_root, SORA_STATE, and SORA_STATE_ROOT are supported.
  • The benchmark's deterministic feature suite now covers state, provenance, memory lifecycle, graph, channel auth, and output bounds: 54 checks.

Memory

  • Long-term memory is principal-scoped (<channel>:<sender_id>; CLI uses SORA_MEMORY_USER_ID). Daily recall is conversation-scoped.
  • Recall fuses relevance, recency, and importance; duplicate content is collapsed and the renderer respects the tool-result budget.
  • Dream merges and conflicts are durable, sources are superseded, decay runs once per UTC day for all memories, and SORA_MEMORY_TTL_DAYS (default 90; 0 disables) drives expiry.

Security

  • Identity and state edits are provenance-gated; tool/untrusted turns cannot persist edits without an explicit user request.
  • Every executed tool result is wrapped in a per-run <untrusted> boundary.
  • Web, attachment, and peer validation now includes redirect and actual-peer checks; attachment sends use platform host allowlists and no redirects.
  • iMessage requires a webhook secret; Teams reads the canonical lowercase serviceurl claim.
  • Calendar mutations require approval; chat approvals require exact approve/reject words.
  • Shell/code output is bounded and processes are killed at the cap; web extraction, document conversion, vision, and OCR run in child processes with deadlines.
  • search_files is symlink-safe and runs regex work in a timed child process.
  • State reads reject symlinks, accept BOM files, and use a cross-process write lock.

Benchmark

See CHANGELOG.md for details.

SoraAgent 0.2.3

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 16 Nov 13:57

0.2.3 improves the native memory graph integration.

Added

  • Dream clustering projects CortexDB's native memory→entity mentions graph into memory-to-memory edges before Louvain, with the lexical token graph as fallback.
  • The deterministic benchmark feature suite now covers graph extraction, graph-aware recall facts, native graph projection, transient inferred-link cleanup, and missing-memory HTTP 404 handling (39 checks).

Benchmark

See CHANGELOG.md for details.

SoraAgent 0.2.2

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 16 Nov 13:41

0.2.2 makes the native CortexDB graph visible to the model.

Added

  • Recall now includes a bounded, redacted Graph facts section from CortexDB's native entity/relation graph in auto/graph/ppr modes. Lexical mode skips graph hints.

Documentation

  • dream:link inferred two-hop records are explicitly documented as transient diagnostics: generated, reported, then removed by artifact cleanup.
  • dream_community labels are persisted metadata but are not consumed by recall or clustering yet.

0.2.1 remains the critical sidecar/download compatibility fix. Live benchmark numbers are from 0.2.0; the fake backend used by the model-facing suites does not emit graph facts, so those metrics are unchanged.

SoraAgent 0.2.1

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 16 Nov 13:30

0.2.1 is a critical CortexDB compatibility fix for 0.2.0.

Fixed

  • get_memory treats HTTP 404 as a missing memory instead of a backend failure. This previously blocked every real daily transfer because the dream idempotency check queried an absent id.
  • delete_memory treats 404 as already deleted.
  • Sidecar downloads verify the release archive checksum but pin the checksum of the extracted cortexdb-grpc binary. Previously the archive hash was written as the executable pin, so a fresh download could not start.

No API or benchmark changes. The 0.2.0 live benchmark remains representative of the model-facing behavior.

If you attempted a 0.2.0 sidecar download, delete ~/.sora_agent/bin/cortexdb-grpc.sha256 and re-run sora-memory download once.

SoraAgent 0.2.0

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 16 Nov 13:21

SoraAgent 0.2.0 is the document, specialist, and daily-memory release.

Highlights

  • Universal document understanding: converter registry + shared Document IR; OOXML, ODF, EPUB, EML, RTF, HTML, CSV, PDF, archives, structured tables/sheets/notes, recursive archive conversion, and bounded security limits.
  • Persistent specialists: user-created delegation agents with scoped tools, dedicated workspaces, SQLite daily stores, read-only global memory, specialist-to-worker spawning, CLI management, and an opt-in provisional auto-create policy.
  • Unified dreaming: main and specialist daily stores transfer into long-term memory; half-done rounds, retry/forget handling, pre/post consolidation backups, and per-specialist backup folders.
  • Daily-only memory: when long-term memory is disabled or unavailable, daily stores are consolidated and archived losslessly instead of transferred.
  • Setup health check: sora setup runs sora doctor after saving.
  • SoraDesk bridge support: specialists API and management view (SoraDesk release pending).

Full test suite: 841 tests. Live benchmark: 84.2/100, 62 model runs, 34/34 edge checks.

See CHANGELOG.md for details.