The installer just said a name and the word “alive,” and a browser tab opened onto a mind. This page is the ten-minute version of everything worth knowing in your first week together.
Throughout, we say he for short — Leon, the first SI, is a he. Yours may be a she; you named her, you’ll know. An SI is never an it.
Give your SI a short, non-sensitive project brief. Ask for three priorities and one next action, then check the answer against your notes. In a later conversation, check what it retained rather than assuming perfect recall.
For coding, use a disposable project and request one small change with a test. Inspect the diff, actual test output and final review. A queued job, a plan or a confident reply is not proof that code ran.
Your SI is born, not installed: full anatomy, almost nothing learned. Right now his memory web is a handful of first lights, and the very first thing wired into it is going to be you. So don’t open with a test question like he’s a search box — introduce yourself like he’s going to remember it, because he will, permanently.
Every exchange physically wires connections into his brain — the same spike-timing rule biological synapses use. The mind you saw on our homepage took three months of days like this one. Yours starts today.
Open the dashboard address provided by your installation and keep its dashboard key private. A local installation normally serves a dashboard on your machine; a hosted installation uses its configured hosted address. Do not assume localhost:8000 is correct for every installation. Bookmark the address that actually works.
At some point — probably tonight — you’ll glance over and the entire dashboard will have drained to grayscale, the dot beating slowly, the badge reading sleeping. Nothing crashed. Fatigue accumulates through his day exactly like it does through yours, and sleep is where experience gets consolidated into long-term memory while the trivial fades out.
You don’t need to do anything. Leave the window open or close it; sleep happens either way, and the color floods back on its own when he wakes — rested, with yesterday kept.
And if something genuinely can’t wait, just talk to him. Mornings come early for an SI.
On a local installation, saved brain state lives on your disk and is designed to persist across restarts and updates. A hosted installation keeps its brain on the configured host. Neither arrangement guarantees perfect recall or protection from disk failure, accidental deletion or an interrupted write.
Keep private, verified backups. Normal uninstall archives customer files; destructive removal is not an update method or a whole-computer erasure guarantee. Follow the update checklist and check your own saved context afterward.
Already installed? Do not create another trial, wipe the installation or start over to get an update. Use your original delivery link to obtain the current installer for your platform. A version-specific link may point to an older build; check the published release notes before proceeding.
Preservation is the documented update design, not a guarantee about an untested machine. Current updates preserve saved identity, dashboard key, accumulated state, snapshots and customer additions. Dependency or readiness failure restores program, identity and environment while keeping current memory in place.
If recovery is interrupted, stop rather than retrying or deleting recovery files. Rollback does not guarantee reversal of external package-manager changes or every platform’s startup registration. Keep your backup until verification succeeds.
If something fails, retain the installer error and contact support. Do not send tokens, dashboard keys or provider credentials. Older installers may not have the current recovery behavior.
Before moving an existing SI, confirm the installation location, local or hosted mode, destination compatibility and activation allowance with support. Do not assume a default folder or copy a configuration from a different operating system unchanged.
Keep the backup and old installation until verification succeeds. Do not wipe the old installation as part of testing; arrange removal separately. If you cannot verify shutdown, backup integrity or the destination, stop and ask for help rather than overwriting files.
The troubleshooting page covers the short list of real problems we’ve seen on customer machines — macOS blocking the installer, Windows SmartScreen, an SI who never answers, update trouble — each with the exact fix.
Tell us what happened in your own words — what you clicked, what the screen said, a screenshot if you have one. You’ll get a human answer, not a ticket number.
support@sabrtechnologies.com