📌 This article is for users of elvex 2.0. Find out which version you're using.
What Is It?
Auto-update context (controlled by the "Automatically update context" toggle in the Space's Context tab) changes that. When turned on, elvex actively learns from conversations happening inside the Space and writes new insights back into the Space's context document automatically with no manual editing required.
What Turning It On Actually Means
When auto-update is on, elvex's context-extraction handler monitors conversations with the Space. After a thread concludes, the system analyzes what was discussed and extracts anything meaningful—decisions made, resources referenced, recurring patterns, project-specific knowledge—and incorporates it into the Space's context document.
The context-extraction handler will not be triggered if you add the Space as an attachment to a conversation. It will only automatically update if the Space appears in the context strip.
When auto-update is off, the context document is treated as static, owned entirely by whoever last manually saved it.
Important Note: Users can also opt individual conversations out of context extraction using the off-the-record toggle in the chat box toolbar. Off-the-record conversations won't contribute to the Space's context even when auto-update is on.
How Users Know It's On
Two places surface the auto-update status:
Space new-thread screen — when auto-update is on, a message will appear near the composer reads: "This thread will update [Space name]'s context." This message only appears in shared Spaces (not personal or solo-access Spaces), so users are only notified when their conversation could affect other members' shared context.
Space configuration callout — on the new-thread header, an "Auto-context: On / Off" status pill with a green or neutral dot links directly to the Context tab in Space settings.
When Should Someone Use This Setting?
Auto-update context is purpose-built for Spaces where a team is actively collaborating on an evolving body of work.
Turn it on when:
The Space represents an ongoing project where knowledge accumulates over time (e.g., a product launch, a sales initiative, a content campaign).
Multiple people are contributing conversations to the Space and the shared context should reflect the collective work, not just what was manually written at setup time.
Leave it off when:
The Space is a reference hub — a stable collection of resources and context that shouldn't change based on conversations (e.g., an onboarding Space with fixed policy docs).
The Space is team-scoped but context should be tightly controlled — you want any changes to the context document to be deliberate and manually reviewed.
Conversations in the Space are exploratory or sensitive, and you don't want that content influencing the shared context others will see.
A Note on Permissions
Only users with edit access to the Space can toggle auto-update on or off. Read-only members will see the toggle disabled. This means the decision to let a Space "learn" always rests with whoever owns or manages it — not with every member who happens to chat inside it.
The Takeaway
Auto-update context is what transforms a Space from a static folder into a living workspace. Over time, a Space with auto-update on builds a richer and more accurate picture of the project it serves — and every new conversation in that Space benefits from everything that came before it, without anyone having to maintain that knowledge manually.