The AI keyboard for Telegram messages.

Telegram is where power users park long threads, bots, topics, Saved Messages, and private chats that they do not want mixed into Meta's household graph. The reply problem is not story-length wit. It is thread literacy: answering the right message in a hundred-line technical or community scroll without sounding like you skimmed. KOPY for Telegram is a keyboard for that density, plus a privacy-conscious user who notices what Full Access implies.

We still cannot see Telegram's servers. We see clipboard text you copy. That is the same iOS bridge as everywhere else. The difference is what people copy: a 400-word argument, a code error, a channel comment, a secret-chat line they want to answer carefully.

Power-user surfaces that are not WhatsApp groups

Topics in groups, comment threads on channels, Saved Messages as a staging area, bots that expect commands, and folders that split work from friends — these change how a draft should behave. A topic reply that ignores the topic title looks incompetent. A channel comment that reads like a DM looks needy. Saved Messages is where people outline; generating into Saved Messages is a drafting table, not a send.

• Long group topics: copy the specific message you are answering, not the topic's first post from Tuesday.
• Channel comments: public-enough to be careful, short-enough to not essay-post. Closer to X than to a family chat, but the audience is subscribers, not the whole timeline.
• Saved Messages: generate, edit, then paste into the real chat. Useful when you need a second pass without performing live.
• Bots: do not run KOPY on slash commands unless you are writing natural language the bot accepts. Command syntax is not a tone problem.

Privacy-conscious users pick Telegram for default cloud chats with client-side extras, secret chats, and less family-graph entanglement. We will not claim Telegram is untraceable. We will claim that this audience reads keyboard permission copy. They should. Apple's model is explicit that open access expands the sandbox to network and pasteboard. Read custom keyboard docs and the extension programming guide before you enable Full Access. If you will not enable it, KOPY cannot condition on copied thread text. That is a honest trade, not a dark pattern.

Longer threads need a different copy strategy

WhatsApp copy-the-ask still works, but Telegram threads often have nested replies. Copy the message with the reply-to context if the UI gives you text. If you only copy the last line, the model will miss the referent. Power users already reply-to a specific bubble; keep that bubble as clipboard context even if you then type in a different field.

Technical communities on Telegram write in a dry register. Funny Social drafts can sound like a tourist. Insight or Work plus Question is usually the better pair: name the constraint, ask for the missing log, propose a rollback. We built Insight for this shape. It is a poor fit for Instagram stories and a good fit for a self-hosted-software group that is mid-outage.

Secret chats and clipboard risk

Secret chats are a user-trust feature in Telegram. They are not a reason to disable thinking. They are a reason to treat pasteboard as hostile. If you copy a secret-chat message, that plaintext sits on the system pasteboard until something else overwrites it. KOPY will read it if Full Access is on, because that is how we get context. Then we send it to generate a reply. If that is unacceptable, do not copy the message. Type a paraphrase stub instead: they asked if we can move the call, generate against the stub, keep the secret wording off the pasteboard.

We run in a 70MB extension. We are not storing Telegram's local database. We are not indexing your folders. Ephemeral session, generate, insert. If you want zero network, this product cannot do cloud generation. A local-only keyboard would be a different architecture and a different quality bar.

Privacy-conscious does not mean anti-AI. It means explicit pipes.

The people who complain about keyboard Full Access are often correct about the category. A keyboard that can read pasteboard and hit the network is a privileged pipe. We keep the pipe narrow: copied context in, draft text out, no chat history product. Telegram users should still decide whether a given thread is too sensitive for that pipe. Legal, medical, and activist threads may belong in typed-by-hand land. KOPY is for the other ninety percent of messages that are still cognitively expensive: scheduling, technical clarification, community moderation, and friend chat that ran long.

Moderation in Telegram groups is a tone minefield. You need firm plus specific. Disagree or Neutral in Social, or Professional in Work if the group is a company internal. Funny while banning someone is a style you should not outsource by accident.

KPI table: thread depth versus draft effort

Editorial KPIs for Telegram. Not a user study. Not Telegram's published metrics.

Surface	Context you must copy	Default mode/tone	Pass condition
Topic in a large group	The exact bubble, not the topic root	Insight or Work + Question	Refers to the missing fact
Friend one-to-one	The ask sentence	Social + Continue	Sounds like you, not a changelog
Channel comment	The post hook plus the comment you answer	Social + Insight or Disagree	No subscriber-bait insult
Work group on Telegram	Deadline plus owner line	Work + Professional	Next action is unambiguous
Secret chat	Paraphrase stub preferred	Social + Neutral	No extra facts invented

Bots, Mini Apps, and fields that reject custom keyboards

Some Telegram fields are closer to a phone pad or a password. Apple already replaces custom keyboards on secureTextEntry. If a Mini App uses a secure field, KOPY will vanish and that is correct. Do not fight it. For normal composers, globe-switch as usual.

People also draft in Saved Messages, then forward. That is a legitimate power-user flow. Generate in Saved Messages with Insight, edit, forward to the group. You get a second pass without an audience watching you type. That is the opposite of X, where the first send is public.

Folders, unread, and the backlog that is not ADHD

Telegram folders create a false sense of zero inbox. Unread is hidden, not gone. The reply problem for power users is often prioritization: which folder is actually on fire. KOPY does not sort folders. It lowers the cost of answering the thread you already opened. If your issue is initiation across dozens of unread chats, that is closer to the ADHD page as a related executive-function job, or the introvert page if the cost is social, not initiation. Telegram-specific work is: copy the right bubble in a long thread.

A power-user hour

You open a self-hosting topic. Someone pasted a stack trace. Copy the error, Insight plus Question, generate, then you paste the actual version number by hand. Next, a friend chat that went philosophical for three days. Social plus Continue, cut the essay, leave one question. Next, a channel you admin. A comment is wrong on a factual claim. Disagree, short, cite the number you actually have. Do not generate a dunk. Channel comments screenshot well. You will live with that sentence.

Then a secret chat. You skip copy. You type they want Thursday not Friday, generate Neutral, send. Pasteboard never held their names. That is the privacy-conscious loop we respect.

Forwarded messages are a Telegram-specific trap. The clipboard may hold a forward from a channel, complete with a signature that is not the person you are chatting with. Generate against the forwarded claim, then address the friend who sent it: do you want a fact-check or are you just dumping this. Two jobs in one bubble is how drafts get muddy. Split them if the stakes are high.

Replies in comment threads under a mega-channel have an audience of lurkers. Write like a public note, then stop. Insight plus one number you actually possess. If you do not possess a number, Question. Inventing a benchmark to sound senior is how privacy-conscious communities correctly lose trust in you and, by extension, in any AI-shaped sentence you send.

Default cloud chats sync. That is a user choice Telegram makes obvious. It does not change our pipe: we only receive what you copy. Still, treat a copied cloud-chat message as data you elected to put on the pasteboard and on the generate endpoint. The conservative habit is the paraphrase stub for anything you would not paste into a search bar. Power users already think this way about screenshots. Apply it to keyboard context too.

Language mixing is common in Telegram power-user groups. If the copied message is in one language and you want to answer in another, say so in a short prefix you type: reply in English. We do not auto-detect your preferred language from the OS keyboard layout. The 70MB extension is not a translation suite. If the draft comes back in the wrong language, that prefix is cheaper than three regenerations.

Admin announcements should be boring. Use Work plus Professional, then delete any sentence that sounds like a startup changelog. People in a city housing group need the date the water shuts off. People in a dealer-to-dealer chat need the SKU. Specificity is the respect. Length is not.

Scheduled sends and silent sends are Telegram habits. The keyboard inserts text now. It does not own Telegram's schedule UI. Generate, then use Telegram's clock if you must delay. Do not leave a perfect draft sitting in the composer as a fake schedule. That is how power users still ghost a thread they meant to answer at 18:00.

Telegram will keep attracting people who write longer than Instagram and more technically than WhatsApp family groups. Meet them with thread-accurate clipboard use, conservative secret-chat hygiene, and modes that can go dry. Leave story-reply culture and public-ratio culture on their own pages.