new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

LangChain & LangGraph · all subjects

memory & persistence

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Agent Auth token stored and refreshed

OAuth tokens are stored and automatically refreshed so future uses of the service by either the user or agent do not require another OAuth flow.

Thread state persistence and TTL support

Threads support time-to-live (TTL) configuration for automatic expiration. The Agent Server tracks meaningful state changes via `state_updated_at` field, enabling filtering and sorting. TTL information is returned via `?include=ttl` query parameter on GET /threads/{thread_id}. The 'keep_latest' TTL strategy preserves only the latest state while pruning older checkpoints. Store HTTP API endpoints support `ttl`, `index`, and `refresh_ttl` parameters.

Store API key-value operations

The Store API provides `put_item`, `get_item`, `delete_item` operations for key-value storage with namespace isolation. Custom encryption is supported for Store API `value` fields with configurable key allowlisting. The Store supports transactions, with core authentication and OR/AND filter support. The `get_store()` function works in custom routes, enabling Store access from user-defined Starlette endpoints.

Give your agent this brain