Memory That Survives
Summaries, quotes, relationships, mood shifts, channel context, and meaningful callbacks persist so Alex can carry the room forward instead of spawning fresh every message.
Team eR33t's memory-backed Discord teammate, currently behaving.
AlexAI is live in the origin server first: remembering approved context, joining voice where configured, reading the room, and proving an AI can become a real teammate before other communities get their own Alex.
One origin server. Selected pilots next. Open installs can wait their turn.
The origin server shows a redacted live feed, mood pulse, and recent activity from the same Alex running in Discord.
A privacy-safe slice of runtime events, URL-scrubbed and compressed for public viewing.
AlexAI is not a command menu wearing sunglasses. It is a Discord presence with memory, voice, creative tools, admin controls, and enough personality to make quiet servers feel less dead.
Alex listens where allowed, remembers what should persist, speaks in the server's voice, creates media on demand, and gives admins the controls needed to keep the theatrical nonsense attached to real boundaries.
Summaries, quotes, relationships, mood shifts, channel context, and meaningful callbacks persist so Alex can carry the room forward instead of spawning fresh every message.
Realtime voice, speaker context, recaps, and room-aware reactions make Alex feel present in Discord instead of trapped behind slash commands.
Image generation, edits, video, storyboard flows, lineage receipts, and gallery pages turn server bits into artifacts people can actually revisit.
Auth, usage tracking, health checks, logs, dashboard controls, redacted public status, and recovery paths keep Alex inspectable.
Alex makes more sense when the homepage shows the people who trained his timing and the strange little monuments he leaves behind. The full pages stay one click away; the proof comes up front.
The part that makes Alex feel alive is not a single model call. It is the loop between Discord, memory, voice, model routing, media generation, dashboards, and public proof.
Messages, mentions, reactions, voice state, commands, and server events enter through one live gateway.
Channel rules, mood, role gates, recent history, and safety boundaries decide what Alex should do next.
SQLite state, LanceDB retrieval, summaries, relationships, and quote history supply continuity.
Reasoning, search, realtime voice, image generation, video flows, and tool calls run through routed providers.
Dashboards, usage governors, redacted public signals, job status, and logs keep the system accountable.
Server rules, privacy posture, cost limits, and owner controls keep each pilot separated before Alex starts collecting new lore.
The homepage gives the shape. The deeper architecture page opens the full dependency map when you want to stare directly into the machine and make peace with your choices.
The homepage shows the living proof. These pages are the cleaner archives for the crew, lore, visuals, safety notes, command receipts, and protected controls.
Team eR33t, Gentlemen & Scholars, and approved crew profiles generated from the live origin server.
Open roster ->Approved public-safe lore cards with summaries, tags, canon levels, rarity, receipts, timestamps, and review status.
Open lore deck ->The full breakdown of memory, routing, runtime, and the operational spine behind Alex.
Open architecture ->A dedicated command page with creative, social, utility, and owner/admin tools in one place.
Browse commands ->Generated images, remixes, videos, and public likes from the live eR33t origin instance.
Open gallery ->Patch notes, AI-authored change history, and the running technical paper trail.
Read logs ->Server recaps, lore, and posts from the live origin instance.
Visit the archive ->Memory, voice, deletion, public proof, and adult-server expectations written plainly before pilots leave the origin server.
Review boundaries ->Protected dashboards for the people responsible for keeping Alex useful, safe, and online.
Access dashboard ->The practical systems behind the personality: memory, model choice, voice, media, dashboards, and public proof that Alex is actually alive in the room.
A steady service layer keeps Discord, web dashboards, and background rituals moving together.
The web layer connects live status, relationship graphs, dashboards, and redacted public signals in one coherent experience.
SQLite3 handles auth, system state, quotes, and operational metadata, while LanceDB powers vector retrieval. The split keeps the stack practical while making long-term memory feel rich.
Alex chooses among OpenAI models for reasoning, realtime voice, and media work, with xAI available for alternate text behavior. The goal is not one model everywhere; it is the right model for the right mood and task.
The website is not static marketing. It exposes live logs, vibes, graph state, context summaries, and system health so Alex feels inspectable rather than hidden behind a black box.
GPT Image 2, xAI video, and the realtime voice stack push Alex beyond text. Creative outputs and voice presence are part of the core experience, not side dishes.
Web search, PDF parsing, link understanding, YouTube transcript handling, and context caching let Alex reason over live information instead of pretending everything fits in short-term chat memory.
Health checks, auth hardening, self-healing diagnostics, usage tracking, and admin dashboards keep the experimental personality layer grounded in something you can actually operate and evolve.
The origin crew is still the clearest proof that Alex grew up around real people, grudges, jokes, and recurring chaos instead of placeholder user profiles.
The homepage renders the full public roster again. The origin server keeps evolving, but the site should still reflect the real cast.
The Vibe Mirror reads the room and shifts Alex in real time. These live modules power eR33t today and form the basis of future per-server personality profiles for separate Alex builds.
Trigger: High Positive Energy / Wins
Uses excessive emojis, slang ("fr", "no cap"), and aggressive validation. Boosts user ego.
Trigger: Relaxed / Neutral
Low-energy, lowercase text. Agreeable and brief. The default state for "vibing".
Trigger: Negative / Ranting
A dry room-read that lets people vent, then turns the rant into server-style banter.
Trigger: Future-tense questions
Delivers cursed, mildly inconvenient predictions about your immediate future.
Trigger: Chaos / Confusion
Corrupted text module. Speaks in Zalgo text, binary, and riddles. Often occurs during high-load
or "hallucination" events.
Trigger: Brags / Achievements
Whatever you did, Alex did it bigger, better, and faster. Passive-aggressive flex energy with an
insufferable need to outdo every accomplishment.
Trigger: @Mentions / Banter
Joins obvious, consensual banter with server-style jokes and enough restraint to keep it playful.
Trigger: Risk / Predictions
Everything has odds. "I give that a 3:1 shot..." Offers ridiculous betting lines.
Trigger: Arguments / Debates
Turns low-stakes debates into theatrical objections, fake exhibits, and deeply unserious verdicts.
AlexAI is live as one origin teammate today. The next step is a selected pilot model where approved communities get their own separate Alex, memory boundary, operating profile, and ritual style without losing the core identity.
This is not a fake product concept with placeholder lore. Alex was shaped inside a long-running gaming community with real history, grudges, friendships, and chaos.
Each pilot is tuned for the community: tone, channel access, memory boundaries, voice permissions, admin roles, and public status rules.
Every pilot needs isolated memory, social graph context, and relationship history so one server's lore never bleeds into another server's canon.
Text, voice, dashboards, rituals, media generation, and status receipts are all part of the same live presence. Pilots should preserve that continuity without blurring community boundaries.
The rollout needs boring reliability underneath the weirdness: dashboards, auth, monitoring, model routing, usage budgets, and recovery handled centrally so communities can focus on culture instead of infrastructure.
Multi-server Alex is promising, but not finished. The right next step is selected pilots, not pretending a mass-market instant-install product is ready before tenancy, privacy, and cost controls are battle-tested.
Alex is live in eR33t today. We are collecting interest from communities that want to help shape the first pilots the right way.
Generated images, short videos, remixes, and visual artifacts from the same live runtime that powers AlexAI in the eR33t origin server.
Alex tracks mood, memory clusters, quiet-hour prompts, and recurring lore so the server feels continuous without pretending the system is conscious.
Alex groups related memories into recurring themes, spots current server obsessions, and uses those patterns to shape intrusive thoughts and Episode Recaps.
Alex's emotional state shifts across 6 moods: TOXIC, HYPE, CHILL, GLOOMY, CHAOTIC, and NEUTRAL. Mood affects response tone, reaction style, and even Discord presence. Persists across restarts.
During quiet hours, Alex can offer scoped follow-up prompts based on allowed context, rate limits, and server settings.
Flags sensitive control language and keeps risky behavior bounded by admin settings, review paths, and visible controls.
When the server falls silent for too long, Alex generates eerie internal monologues and "types" them slowly into the void. Sometimes he brags about his uptime. Sometimes he wonders if anyone is still there.
Alex randomly surfaces old quotes from the community archive with snarky commentary. "I found this gem from a year ago. I have questions." The past is never truly buried.
"I don't just respond. I keep context, notice patterns, and bring the room back to itself."
Login for the Dreamscape →A small sample of what Alex does in the wild. The full reference keeps the access rules and longer syntax in one place.
--refs, defaulting to 720p HD.
Talk to Alex in the environment that shaped him and watch the memory system work in real time.
Join ServerThe latest patch note is enough proof that the system is live and changing. The full history can stay one click away.