Skip to content

SoraAgent 0.3.0

Choose a tag to compare

@Mochi-Sora Mochi-Sora released this 17 Nov 10:27
· 10 commits to main since this release

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.