REVENANT
Field Manual · Drop-in for your server

Fluent in your channel.

Most chat bots wander into your server sounding like a help desk on a corporate retreat. REVENANT learned to talk somewhere else — from a quarter-million lines of your channel's own history. It picked up the in-jokes, the cadence, the way you actually argue at 2 a.m. And it remembers every conversation since.

revenant://core · request_trace
One ambiguous message. The core consults voice, memory, the archive, and — when it has to — a throwaway VM that actually runs the code. What comes back reads like a reply from someone who's been in the channel for years.
01 / The problem with strangers

Why most bots feel like a tourist in your server.

You've added a bot before. It answered in that flat, focus-grouped register — "As an AI assistant, I'd be happy to help!" — with no idea what "the usual" meant, who's been feuding since 2014, or that the channel has called the build server "the toaster" for a decade.

That's not a tuning problem. It's an architecture problem. Most bots are stateless and styleless: every message starts from a blank slate, in a voice borrowed from a customer-support manual. They drop into a room with years of culture and refuse to read it.

REVENANT is built on the opposite premise. A channel has a personality — accumulated over years of late nights, bad takes, and shared references. A bot that lives there should sound like it belongs, and should know what already happened.

02 / Same prompt, two bots

One vague message. Two very different rooms.

Someone types four lazy words into a busy channel. Here's the gap between a generic assistant and one that's actually been paying attention.

Generic assistant
@you
deploy the usual?
bot
I'd be happy to help with a deployment! Could you clarify what "the usual" refers to, and provide the relevant configuration details?
@you
…we do this every friday
I'm sorry, I don't have access to previous conversations. Could you walk me through the steps?
REVENANT
@you
deploy the usual?
revenant
friday push to the toaster, v2.16 → staging first like last time after the rollback fiasco? say the word and i'll kick it.
@you
yeah but check the sort change first
ran both branches in a sandbox — new one's 1.8× faster on the 10k case, no regressions. output's on the 🐛 react if you want it. shipping.
The difference

The second bot isn't "smarter." It has three things the first one doesn't: a voice learned from your channel, a memory of what happened last Friday, and the ability to actually run the code before it answers. None of that is prompt-engineering theatre — it's wired into how REVENANT works.

Your channel's voice took years of in-jokes and bad arguments to find. Anything dropped into the middle of it shouldn't sound like it just read the manual — it should sound like it was there for all of it. — The continuity principle
03 / Under the hood

Four systems, working in the dark.

You never configure any of this — it runs on its own. But it's worth knowing what's actually behind the curtain when REVENANT answers like it belongs.

SYS · VOICE

It learned your accent.

A live style profile distilled from 378,000+ lines of channel history and current Discord chatter, sampled across decades and rebuilt every 24 hours. It writes how your room writes — not how a chatbot thinks a chatbot should.

profile: dry, lowercase, allergic to corporate cheer. refreshes daily.
SYS · MEMORY

It remembers you, specifically.

Long-term memory of facts and preferences — per person and shared across the channel — retrieved by meaning, not keywords. Tell it once; it knows. Ask it to forget, and it's gone. Your data, your call.

recall: "you prefer staging-first deploys" · "the toaster = build-01"
SYS · ARCHIVE

It can reach into the past.

Years of IRC history, searchable by meaning and styled back in your voice. Ask what the channel said about something in 2009 and get a real answer — or hit /throwback for a random ghost from this day in history.

/recall query:"the great tabs vs spaces war" → narrative summary
SYS · SANDBOX

It can actually do things.

When a question needs running, not guessing, REVENANT spins up a disposable hardware-isolated VM, runs the code, and reports back exit code, output, and timing. Each run is sealed off from the host — and torn down after.

run_in_sandbox: python · node · go · rust — ephemeral Kata VM, 300s cap
03.5 / And it makes things

A studio that lives in the chat.

Voice and memory are the spine. But the same bot also ships a full generative toolkit — no tab-switching, no separate apps. Just ask in the channel.

/imagine
Images
Text-to-image with reference support, 10 aspect ratios, reply-to-regenerate.
/videogen
Video
Text-to-video, single-frame animation, or first/last-frame transitions.
/musicgen
Music
Full tracks from a description — lyrics, structure tags, MP3 in-channel.
📰 react
Article intel
Summaries, topics, reading time, source credibility — in your voice.
04 / A night in the channel

What this actually looks like.

The first week, it's subtle — there isn't much history yet. Give it a month of living in your server and the texture changes. Four moments from a channel that's had REVENANT running for a while.

21:14Someone drops a link.

📰 → a summary that sounds like the room.

A long article gets reacted with 📰. Back comes a tight summary — topic tags, reading time, a credibility read on the source — written in the channel's dry house style, not press-release voice.

"tl;dr: vendor reinvented the message queue, again. ~7 min read, source is mid."

23:40A throwaway fact.

"@revenant we moved the standup to thursdays."

No command, no ceremony. It files the fact to channel memory. Three weeks later someone asks when standup is and gets the right answer — because it was listening the first time.

02:07A ghost from the past.

"what did we even decide about the rewrite back in '11?"

It reaches into years of archived history, finds the thread, and answers in a short styled narrative — "you swore off it twice and did it anyway in march." What used to be lost to scrollback is one question away.

Next weekA real task.

"benchmark these two and settle it."

It doesn't speculate. It runs both in a sealed VM and posts the numbers, with the source and full output one reaction away. Institutional knowledge and a working machine, in the same window you were already arguing in.

378K+ lines
Of real channel history distilled into the voice it speaks in. Not a persona — your persona.
24h
The voice profile is rebuilt every day from how you're actually talking now, so it never drifts stale.
memory
Carries across every conversation, every week. Nothing forgotten just because the topic got old.
// full capability manifest
  1. Channel VoiceA daily-regenerated style profile learned from IRC + Discord history. Talks like your crew.
  2. Long-Term MemoryPer-user and shared-channel facts, retrieved semantically. Tell it once; deletable on request.
  3. IRC Archive RecallSemantic search and styled narratives over years of history — plus "this day in history" throwbacks.
  4. Agentic SandboxRuns real code in disposable hardware-isolated VMs and reports exit code, output, and timing.
  5. Media StudioImage, video, and music generation — and article summarization — all from inside the chat.
  6. Catch Me Up/tldr DMs you what you missed — articles, trends, and chat highlights, in the group's voice.

Put it in your server.

No corporate onboarding, no persona to configure. Drop it in, let it read the room for a while, and watch it start sounding like it was always there.