USER GUIDE · v2.15.2
Install, use and maintain Elefante. These instructions match the published v2.15.2 release. Your agent does the work; Elefante supplies relevant memory.
FIVE-MINUTE PROOF
Use knowledge that matters to your current work. Do not preload a fake conversation or judge Elefante from a button click alone.
You need a desktop computer, Python 3.11–3.13, 5 GB free space and internet for setup. The dashboard is included. Git, Node.js and a source checkout are not required.
Use the published installer ZIP, not GitHub’s “Code → Download ZIP”. Extract it before opening the launcher.
The download page includes the filename and SHA-256 for each package. Compare the archive’s SHA-256 with the published value before opening it.
Open the launcher for your platform, shown above, and follow its checks. Read the final result before continuing; starting the installer is not proof that setup completed.
Setup verifies Codex as its required host. Select any additional compatible hosts you use and register your project folder. In v2.15.2, that project separates new memories and Recall—not your dashboard browsing. Elefante connects through MCP; it is not tied to one IDE.
Restart the selected host after installation, then ask the agent to check Elefante’s system status.
Ask your agent to remember one real decision for the selected project. Then ask a question that needs it and inspect the memory Recall supplies. Recall returns supporting context, not the final answer; if no memory qualifies, it returns no match.
Choose a specific existing project folder, not your whole home, Documents or Elefante data folder. Register each repository separately if you work across several. A project separates memories; it is not a task manager. Registering a folder does not scan its files or import conversations. Browsing all memories needs no active project; Recall and changes do. This release has no shared-across-project Recall scope.
Use your connected agent for everyday work. You do not need to leave the dashboard open.
For example, only if this is your rule, ask your agent:
Remember for this project: every customer-facing change must be checked on desktop and mobile before release.
Then ask: “What must I verify before releasing this customer-facing change?” Reuse an existing suitable memory instead of adding a duplicate.
A selected memory or a green status is not proof of a good answer. If a known relevant memory is missed, check its scope and eligibility. Do not store secrets or full transcripts as durable memories. Selected context sent to your agent is subject to that provider’s policies.
On the computer where Elefante is installed, open localhost:8000. No browser extension or connector is required. If it does not open, ask your connected agent to Open Elefante Home and use the address it returns.
This is a maintenance console, not a chat window. Most browsing reads a snapshot of stored data. An operation receipt is a result card showing what happened and what was verified. A managed change, backup or restore should finish with VERIFIED_COMPLETE.
Reload snapshot rereads the existing snapshot; it does not rebuild it from the stores. Current describes its age, not memory accuracy. Light / Dark changes appearance only. If controls expire, use Reconnect Home, then explicitly retry or review a fresh change plan.
See memory counts, review signals, the active boundary and recovery evidence. Continue opens the recommended action: Review opens its queue; Test Recall opens Recall.
“Review 10 direct signals” means ten records have health or lifecycle information worth inspecting. It does not mean ten records are false. Read each reason and leave correct knowledge unchanged. Empty Home recommends remembering one useful decision.
Check the displayed scope, enter a real question and select Run Recall Check. Open a selected record to read it. This needs connected controls and an active project whose folder is available.
The question is not saved as a memory. The question and result survive tab switches, but a page reload or project change clears them. Missing counts are not zero; a missing valid verification time means Not verified.
Library browses the snapshot across projects. Review shows direct health or lifecycle signals. Select a row to read content, source, scope, health and relationships. Close panel returns to the list on narrow screens.
Available changes depend on the record and active project. Review the plan, confirm deliberately and inspect the final receipt. At risk is a reason to inspect, not an instruction to delete.
Topics groups represented memories by subject. Vitality shows stored maintenance scores, not truth or usefulness. Decision Graph follows explicit stored relationships.
Similar wording does not create a connection. An empty graph can be correct when no qualifying relationships are represented. This view is read-only; it does not prove that memory improved a task.
Register specific folders and review older unassigned memories before assigning them. Do not guess ownership. After registration and strict-mode setup, choose Use for actions beside the intended project; Current scope confirms it.
Changing project clears the old Recall question and receipt. It does not move memories, import files or repeat an operation. Disabled management controls explain their missing requirement.
Check health diagnoses without repairing. Back up now creates and verifies a local backup. Restore first inspects a chosen backup and asks you to confirm a plan; it replaces stored state. Do not casually test it on real memories.
Support report previews what will be included, then creates a local privacy-safe ZIP. It does not send the ZIP anywhere. Read each final receipt; a failed or unsafe result is not completion.
Repair, update, product rollback and uninstall use the matching official package, not dashboard action buttons.
Open Home → Advanced → Session Intelligence. This reports usage; it does not start collection. After explicit permission, Elefante automatically records local MCP activity and token estimates, without prompts, transcripts or response content.
These activity records are separate from memories in the Library. Permission, retention, export and deletion use the installed package’s command-line controls, not dashboard or MCP buttons. Read the privacy notice.
Run these only for the intended installation. On macOS or Linux, open a terminal in ~/.elefante/app/current. On Windows, open PowerShell in %LOCALAPPDATA%\Elefante\app\current and replace ./.venv/bin/python below with .\.venv\Scripts\python.exe.
Check status without changing collection:
./.venv/bin/python scripts/pipeline/session_intelligence.py statusOnly if you want to enable local usage analytics:
./.venv/bin/python scripts/pipeline/session_intelligence.py consent --purpose usage_analytics --confirm ENABLEUse the same command with snapshot to refresh the report or revoke to stop new writes. Revoking does not delete retained evidence. Provider usage and aggregate hypotheses require their own permission.
Default event retention is 30 days, applied when the ledger opens or is explicitly pruned. For export, deletion and pruning, inspect the installed command’s --help first; deletion requires an exact target and confirmation. These controls do not change semantic memories or graph data.
USER CAPABILITY MAP · v2.15.2
These capabilities belong to the downloadable v2.15.2 release. Some require explicit permission or operator action; a capability being available does not mean it runs automatically. Unknown usage or cost remains unknown.
One read-only call returns a small governed context bundle—or explicitly abstains when evidence is irrelevant or unsafe.
New memory and Recall stay inside one active registered project; missing or invalid isolation evidence fails closed instead of sharing across projects.
Edit, Replace, Archive, Restore, Resolve, and backup-bound permanent deletion verify storage, Home, and scoped Recall, with compensation when a postcondition fails.
Health, verified backup, rollback-protected restore, and a privacy-safe support ZIP return bounded receipts without exposing memory content.
Detected conflicts can be withheld from Recall; deterministic detection and dry-run Smart Merge keep resolution under explicit authority. Detection is not a guarantee that every contradiction is found.
Snapshot search exposes available match, ordering, source and health evidence. It is not a complete explanation of governed MCP Recall or proof of answer quality.
With explicit permission, automatic MCP capture records local activity and token estimates. Supplied provider-reported usage stays separate from estimates. No prompts, transcripts, or response content are stored; unsupported cost and task value remain unknown.
An opt-in foreground watch mode processes supported session files serially and stores nothing unless storage is explicitly enabled.
Signed, scope-bound local bundles exchange an explicit memory allowlist without introducing cloud transport.
Bounded image, audio, and video attachments remain content-addressed and local, with no OCR, transcription, model analysis, or network upload.
Typed, privacy-scrubbed file, terminal-error, and conversation events can request governed retrieval without persisting host content.
An advanced loopback-only maintenance console inspects the redacted snapshot and exposes only named, short-lived, verified controls; it is not the daily agent workflow.
Codex is the primary validation target. Other listed hosts have released compatibility adapters, not vendor certification. IBM Bob and Antigravity remain Preview; Agent Zero has a documented community connection path.
For persistent problems, use Recover → Support report. Review the contents before sharing. Do not reset memories, edit databases or dump credentials and logs as a first response.
Rerunning the same official installer repairs its runtime while preserving durable data. Check the version in your dashboard first; a complete uninstall requires the official package that exactly matches the installed build.
Uninstall Elefante.command.Uninstall Elefante.bat.chmod +x uninstall.sh && ./uninstall.sh.The package shows the impact and asks you to type UNINSTALL. It verifies a restorable backup, removes the app and unchanged Elefante-owned connections, and checks that memories were preserved. Your durable data is not deleted.
Inspect the completion receipt. If the package reports a mismatch or unsafe state, stop and use the support report. A later matching installation can reconnect the preserved data; treat that reconnection as complete only after Doctor and a live Recall check pass.
Most customers can stop after Remember, Recall, correction, and backup. The released interface also exposes structured surfaces for agents and operators. They stay separate from the first-use path.
These surfaces are for agents or operators that need structured control beyond the normal Remember and Recall loop.
This page contains the complete customer path and every released feature group. Exact tool parameters, response schemas, scoring formulas, architecture, source, and development history live in the GitHub repository linked once in the site footer.
LOCAL ARCHITECTURE
A loopback-only daemon owns storage, concurrency, and provenance. MCP clients connect through local HTTP or a storage-free stdio bridge; they do not become competing database owners.