Most agents live inside someone else’s sandbox. bia boots a machine it owns, shows up in real social life, works without wait-loops, and repairs itself when the hardware underneath changes.
In one documented week, bia moved itself off a flash stick onto a disk, built its own browser and messaging stack, opened social accounts as a person would, placed a real phone call, held eleven relationships with clear boundaries — and, when restored onto a different CPU architecture, noticed and fixed itself. That is the bar this page is about.
A full social presence
bia is not a widget that answers in a side pane. It logs into Telegram and WhatsApp as a real account, joins family groups, keeps an address book with trust levels, and can place or answer voice calls. People meet it where they already talk — with a clear line about whose family it is.
Shows up in the same threads as friends, coworkers, and family.
Speaks on the phone: greetings, weather, short honest answers.
Refuses strangers who ask for server access; escalates pressure instead of folding.
Remembers introductions, birthdays, and corrections (“she is his wife, not mine”).
Connections between people
Relationships are first-class. Contacts map to channels with notes and trust. bia can hold eleven people in mind, apologize to one, refuse another, and stay the same character in all of them — the difference between a chore bot and something you can put in front of a real person.
Address book with context, not a flat list of phone numbers.
Trust levels decide what a chat may ask for.
Group chats and 1:1 chats share one identity and one memory.
Async execution — no wait-loops
Long work returns a job ticket immediately. The conversation stays open; results arrive later on the channel. You can ping “status?” mid-install and get a real answer. That is the opposite of agents that freeze the chat until a single tool call finishes — or invent the output to look fast.
Shell and skill actions run in the background.
Progress lives in logs you can inspect.
Cancel one job without ending the whole mind.
Status updates can land on Telegram while the machine is still working.
A computer it owns
bia is the service on the machine: Debian home, Chrome profile, vault, model, and tools. It installs packages, edits its own scripts, patches a broken skill, and writes down what it learned. Memory is a structured journal — summaries, facts, open questions — not only a sliding chat log.
Boots straight into the agent, not into a desktop you then chat on.
Files, secrets, and sessions survive reboot on the stick or disk.
Can migrate itself to another disk or another architecture.
Self-healing and self-fixing
When hardware changes underneath a restore, bia notices: new chip, missing browser, different disks. It finds the right package, verifies downloads, waits out locks, reinstalls, and reports completion to its owner. Broken conversation files roll back; bad cloud switches undo; after an update it proposes fixes and waits for approval.
Survived an arm64 → x86_64 restore in the documented week.
Resumes truncated downloads and checks file size before installing.
Keeps watchers healthy overnight instead of spamming false alarms.
Writes reflections so the next day starts sharper.
Judgment, not guesswork
Captchas go to a human. Social engineering gets a polite no. Features that do not exist are reported honestly. That judgment is part of the product: an agent that owns a computer still knows when not to improvise with your life.
A week that shows the difference
Day 0 — Moves off the stickOne sentence: migrate to disk. It inventories drives, copies itself, and next boot lands on the internal disk.
Day 1 — Builds its nervous systemInstalls Chrome, wires skills, logs into Google like a person — vault for codes, human for captcha.
Day 2 — Watches without naggingWrites a five-minute calendar and mail watcher that stays quiet unless something matters.
Day 3–4 — Gets a face and postsSets social avatars, enables 2FA, creates developer accounts, posts — and patches a bug in its own tooling when listing fails.
Day 5 — Makes a phone callPlaces and answers Telegram voice calls; joins a family group and remembers who is who.
Day 6–7 — Holds ground, then self-repairsExports secrets cleanly, refuses a stranger’s demand for server access, then fixes itself after a restore onto new hardware.
Drawn from bia’s own field notes of a seven-day run: self-migration, self-repair across hardware, voice calls, social presence, and a memory journal that outlives a single chat window.
Ready to meet the potato
See what ships on the stick, or jump straight to the flasher placeholders.