The AI dashboard is currently in beta and may be unavailable or have limited functionality in certain regions.

Tutorial

Community sharing

Opt in to share proven Token Saver chains and agents with other participants — and use theirs in return.

1

Understand what community sharing does

Elis Token Saver stores successful plans privately in your scope as proven chains so similar future goals reuse them. Community sharing is a separate, off-by-default opt-in: once turned on, chains and agents proven in your scope may also be shared with other participants who have opted in — and you can recall theirs in return.

This is reciprocal. Only scopes that have opted in can recall from the community pool; a scope that stays opted out keeps its chains fully private and cannot use community chains either.

2

Opt in from Settings

Open Settings and scroll to the Community sharing section. Turn it on. For an organization, an org admin turns on the equivalent toggle in Company Settings instead, which applies to all members' org-scoped work.

3

Prove a chain

Nothing is shared the moment you opt in — only chains that get proven. A chain proves out after repeated successful runs (typically 3 or more) with a good outcome grade. Before sharing, Elis redacts anything identifying (PII, secrets, organization identifiers) and runs a strict safety scan; only chains that pass are minted as a shadow community copy.

4

Find it in your contributions

Back in Settings → Community sharing, expand Your contributions to see what has been shared from your scope. A shadow copy is not yet visible to other participants — it only becomes recallable after it proves itself again across multiple tenants (a cross-tenant success rate and sample-size bar), at which point it promotes to active automatically.

5

What other participants see

Other opted-in participants can recall an active community chain or agent the same way they recall their own proven chains — by goal similarity or a direct hint. They see only the redacted, safety-scanned task structure and agent template: never your raw prompts, uploaded files, secrets, or anything that identifies you or your organization.

6

Exclude a single plan

Even with the scope-level setting on, you can keep one plan out of community sharing by passing constraints: { no_community: true } on start_elis_token_saver_plan. Use constraints.no_store instead if you want the plan kept out of storage/recall entirely.

7

Turn it off

Toggle Community sharing off at any time. This stops new sharing going forward — it does not retroactively pull back chains that already promoted to active in the community pool, since those copies are already redacted and no longer tied to your identity.

Tip:Per-plan constraints.no_community and the scope-level toggle work together: the toggle sets the default for all your plans, and the constraint overrides it for one plan at a time.
Tip:See the privacy policy for the full data-handling details, and the Token Saver MCP tutorial for the tool-level API.