The AI keyboard for Discord chats.

Discord splits into servers and DMs, and those are different countries. A server channel has an audience, a topic, a joke layer, and sometimes a moderation layer. A DM has consequences for one relationship and no crowd to absorb a miss. Gaming and community tone sit on top of both. KOPY for Discord is a keyboard for register switching at that border, not for WhatsApp family logistics and not for X's global ratio.

We still only see clipboard text. Discord's reply-to a message is useful: copy that message so the draft answers the right person in a fast raid-night scroll. If you copy the wrong line, you will generate a ghost reply that looks like you were not in voice with them five minutes ago.

Servers versus DMs is the whole product split

In a server, you are joining a chorus. In-jokes, pings, and thread channels punish people who write like email. In a DM, the same Funny draft can feel like you are performing a bit at a friend. Default Social plus Continue in DMs. Default Social plus Funny in casual gaming channels, unless the channel is actually #ops or #mod-log.

• #general / memes: short, referential, optional emoji you add yourself. Do not generate emoji walls.
• #help / tech: Insight or Work. Paste the error in clipboard. Ask for the missing version.
• Stage or announcement comments: closer to a channel comment on Telegram. Careful, screenshotable inside the community.
• Friend DM: drop the server persona. If you just roasted them in public, the DM should not continue the roast unless that is the friendship.
• Mod DM: Neutral or Professional. People screenshot mod DMs into tickets.

Gaming voice-plus-chat is a timing problem. The raid is moving. You are on a phone because you stepped away from the desk. A keyboard that needs a 30-second app switch is useless. We stay in Discord's field. Generate in a couple of seconds, edit the callout name, send. That is the job.

Community tone is local law

Every server has a constitution nobody wrote down. Some want AAVE-adjacent casual. Some want corporate-amateur. Some want 2007 forum formal. KOPY will not learn the constitution from one copied line. You pick mode. If the server is dry, Insight. If it is chaotic, Funny. If you are new, Agree and short until you have earned a bit. A generated roast in a server you joined yesterday is a self-kick.

Threads inside channels are Telegram-like: copy the thread parent plus the last ask if both matter. Discord will show a reply reference in the UI even if the model only saw the copied child. Align those. Mismatch is how you answer last week's argument.

70MB, Full Access, and a gamer who will not read Settings

Discord users skip onboarding. Then they wonder why the keyboard has no context. Allow Full Access is required for UIPasteboard, which is how we read the copied message. Apple documents pasteboard as an open-access capability in the App Extension Programming Guide and in custom keyboard documentation. Without it, you are improvising in a fast channel with zero prompt context. Enable it once in iOS Settings, not inside Discord.

The extension still has a 70MB RAM budget. We do not embed a game wiki. We do not keep your server list. Ephemeral network generate, insert text, done. If Discord is in a secure field (rare), the system keyboard takes over. Nitro, stickers, and slash commands are not keyboard jobs. Do not generate a slash command unless you are writing its natural-language argument.

KPI table: channel register versus DM register

Editorial KPIs. Not Discord's member counts. Not a raid success rate.

Place	Audience	Default pair	Pass condition
Casual gaming channel	Server	Social + Funny	References the last play, not a TED talk
Help channel	Server	Insight + Question	Names software plus the missing log
Off-topic	Server	Social + Continue	Does not ping everyone
Friend DM	One person	Social + Continue	No crowd-performance leftover
Moderation DM	One person plus logs	Work + Neutral	Rule cited without humiliation

Pings, replies, and the screenshot culture inside servers

A @here in a generated draft is a defect. Strip mentions you did not intend. KOPY should not invent pings. If a name appears, check it. Wrong callouts start fights. Reply-to in Discord already attaches; you do not need to paste their username in the body unless the channel is chaotic and the reference will break.

Community servers leak into LinkedIn. People get hired from Discord. Write help-channel answers like they might be forwarded. That is not Work-mode stiffness. That is Insight without insults. Funny belongs in the meme channel. Cross-posting a meme-channel voice into #help is how you get ignored when you actually need an answer.

A raid-night phone session

You copy where were you we started without you. Funny, one line, send. You copy a paste of an add-on error. Insight, ask for the version, send. You get a DM that is actually about a fight in the last voice session. You do not use Funny. Neutral, name the issue, offer a time to talk. That DM is not a channel. Treating it like a channel is the Discord-specific failure.

Roles and color names are not context we receive. If you copy a message from someone with a Mod role, the model still only sees words. You must choose Neutral or Professional yourself. Generating Funny at a mod is a self-own. Generating Professional in a shitpost channel is how you get clown-reacted. The accept gate is local law, not a global tone named Social.

Forum posts can run for weeks. Copy the latest constraint, not the original manifesto, unless you are answering the manifesto. People bump forums with +1. A generated +1 is a waste of a generate call. Type it. Save the keyboard for the answer that needs a missing log or a calm de-escalation.

Event servers for conferences have a 48-hour culture. People are tired and drunk on hallway-track. Keep drafts short and logistical: room name, time, whether you are coming. Funny at 1am in an event server reads differently at 9am when organizers scrape the channel. Assume scrape.

Partnership servers and vendor Discords sit on the Work border. Professional, then strip jargon. Do not generate a meme in #billing. Do not generate a contract clause in #memes. Channel names are a hint you can see and the model cannot, unless you copied the channel name into the stub. A five-word stub that says this is #billing, they asked for a PO is legal context. Use it.

Slowmode channels punish regeneration. You get one send per interval. Cap at one generate. Edit. Send. A second generate after slowmode is how you miss the window and look like you ignored a question you actually answered in a draft you never committed.

Voice-text hybrid: if they asked in voice and you only have a friend's summary in clipboard, say that you are answering a summary. Inventing details they said in voice is a Discord-specific lie. The keyboard cannot hear the channel.

Forum channels and post tags add another copy rule: copy the post body if you are the first reply, copy the last clarifying question if you are late. Generating against a tag name alone produces empty text. The keyboard cannot see the tag UI.

Voice activity status is not context we receive. If they are in voice, a long generated paragraph is rude. Keep it to one sentence they can glance at. That is a Discord timing KPI you will never see on Instagram stories.

If you needed public brevity and ratio caution, that is Twitter/X. If you needed long technical threads with a privacy-conscious audience, that is also Telegram, but Telegram folders are not Discord roles. Discord is servers versus DMs plus gaming/community register. Stay in that split.

Onboarding screens in Discord are not composers. The keyboard appears when there is a field. If you are picking a server from the rail, there is nothing to generate. Do not hunt for a generate button in the KOPY UI while you are still in the server list. Open the channel, copy a message, then globe-switch.

NSFW channels have a consent and tone problem the model will not see. If the channel is marked NSFW, Funny can still be fine and Professional is usually comedy. If you are unsure, you do not have enough context for a generate. Type by hand or ask a human. A keyboard stub is the wrong tool for consent edges.

Clan schedules, LFG posts, and looking-for-group channels want times and roles, not vibes. Work plus Question: which difficulty, which start time, which voice. Then you add the role name by hand because clipboard often holds a half-updated embed. Embeds copy poorly. If pasteboard is a mess of markdown, write a stub in plain language and generate against that, not against the broken embed soup.

Ban appeals and ticket bots deserve Neutral and short. They are closer to email than to raid chat. Do not generate a bit. Mods forward these. Your future self is in that forward. If the ticket asks for logs, attach the logs in Discord; do not ask the keyboard to invent a stack trace you never copied. Copy the bot's question, not the whole ticket history. Answer that question only.