News includes Quickbeam bringing a full #JS runtime into the #BEAM, Elixir’s type system inspiring #Python’s Ruff, LiveView Debugger v0.7, Oban v2.21, and more! #ElixirLang @elixir-lang.org www.youtube.com/watch?v=FfB0...
New "default: true" option on FileSystemConfig. A single catch-all config handles all paths, ideal for database backends that don't care about directory structure. Specific configs still take priority. hexdocs.pm/sagents/Sage...
MessagePreprocessor behaviour lets you split messages before they hit state. User sends @-mentions. The UI gets a styled chip, the LLM gets the full document context. Zero overhead when not configured. hexdocs.pm/sagents/Sage...
New tool_context field on Agent. Pass user IDs, tenant info, or Phoenix scopes. It merges into custom_context so tool functions can access caller data cleanly. Making it easy to scope an action to the user's data and permissions. hexdocs.pm/sagents/Sage...
Upgrade: mix deps.update sagents.
Breaking changes in FileEntry field names and return types. See the changelog for migration steps.
github.com/sagents-ai/s...
Metadata-only changes (tags, title) no longer rewrite the full file to storage. A new dirty_non_content flag routes to update_metadata_in_storage when the backend supports it, falling back to full write transparently.
Is it just me? Or does it feel like the safest way to protect yourself from JavaScript and Python supply chain attacks is to just not use them? #ElixirLang
The agents_demo app has been updated to work with Sagents v0.4.0. Full-featured chat UI with real-time agent execution, file browsing, and conversation persistence -- all running on the latest release. #ElixirLang #MyElixirStatus
The Sagents demo project can be found here. github.com/sagents-ai/a...
move_file/3 atomically renames or moves files and directories. It re-keys all entries, transfers debounce timers, and calls the new move_in_storage/3 persistence callback so backends can handle path changes efficiently. hexdocs.pm/sagents/Sage...
