Claude handles long-form nuance. KOPY handles instant replies.

Claude is the assistant I want when the sentence has to survive a lawyer, a founder, or a tired friend who will screenshot it. KOPY is the keyboard I want when the sentence has to exist in two seconds inside iMessage. Anthropic’s Claude product is built for long context, careful tone, and back-and-forth revision. Our extension is built for a height-constrained input view and a user who will not wait for a Socratic seminar.

That is not an insult to Claude. It is a job split. In 2025 the Work Trend Index clocked interruptions every two minutes in core hours (275/day on the high-ping cohort). Claude rewards uninterrupted attention. Mobile messaging punishes it. Grammarly and Harris Poll’s 2022 estimate that U.S. businesses lose $1.2 trillion a year to poor communication is about failed alignment, not missing Oxford commas. Speed without a usable sentence is also a communication failure. You need both, in different surfaces.

• Claude wins when you will reread the output.
• KOPY wins when the recipient is waiting in a live thread.
• Do not grade a keyboard on essay quality, or an assistant on insert latency.

Latency budget for a 2-second reply

A thoughtful Claude chat often takes minutes: you paste context, you add constraints, you ask it to be less stiff, you ask it to be less cute, you copy. That loop is the product. It is also lethal in dating apps and Slack huddles. Our generation target is under two seconds because the social clock is not the model clock. People assume you saw the message. They do not assume you opened a second AI and held a workshop.

Work unit	Claude (assistant UI)	KOPY (iPhone keyboard)
800-word memo with sources in mind	Correct tool — sit down	Wrong tool
2-sentence Slack answer	7–9 steps, 1–3 minutes	3 steps, ~2s generate
Context switches	2	0
Revision style	Multi-turn, high nuance	One-tap tone, then you edit in-thread
Long-context documents	Native strength	Not what we ship
Where it lives	Claude app / web	Custom keyboard extension

I have used Claude to rewrite a sensitive “we’re not moving forward” note and meant every extra minute. I have also watched people paste a dating message into Claude, get a beautiful paragraph, and miss the reply window. Nuance that arrives after the other person left is not nuance. It is a diary entry.

What “nuance” costs on a phone

Claude’s brand of nuance is conversational: you can say “sharper, but keep the apology, drop the joke about the deadline.” That is a desktop motion. On a phone, that same motion is thumb hell. You will under-specify. Then you will blame the model for being generic. The model did what under-specified prompts do.

KOPY compresses nuance into mode × tone. Work + Professional is a different prior than Dating + Funny. Insight + Disagree is not Social + Agree. Is that as rich as a 12-turn Claude thread? No. Is it richer than a blank field while your manager waits? Yes. I would rather ship a constrained prior that fits in an extension than pretend a 70MB-class keyboard can host Claude’s whole product.

Apple’s custom keyboard documentation is blunt about the sandbox. Network needs Full Access. You do not get to become a mini iOS. I learned that by failing: too much UI, too much state, keyboard jank, host apps fighting for first responder. Claude’s UI can be generous. Ours cannot.

The infinite workday is a Claude problem and a KOPY problem

Microsoft’s infinite workday report (2025) describes 40% of people in email before 6 a.m. and a triple-peak day that leaks into 10 p.m. That person still has to answer “can you take this?” from a phone in a rideshare. Claude is the wrong ritual for that ping even if Claude would write a better paragraph at a desk.

Use Claude in the 9–11 a.m. focus block for the thing that will be screenshotted. Use KOPY for the 40 smaller messages that keep the block from collapsing. If you route every ping into Claude, you will protect prose quality and destroy calendar quality. I did this for a week while building the extension. My writing got prettier. My response times got embarrassing.

Pricing shape, not fake stickers

Claude’s public product includes a free experience and paid individual / team / enterprise shapes. I am not going to mint a fake monthly price that Anthropic can change tomorrow. Read Anthropic’s Claude page (Sources) for current tiers. KOPY is simpler and less generous: Pro is $12.99/mo, no free trial, generation is paid. The keyboard binary can sit on your phone for $0. Replies are the SKU.

If you already pay for Claude and you draft long, keep paying. Adding KOPY is not “another chatbot.” It is an input method. If you only buy one paid AI and your life is mobile threads, buy the keyboard. If you only buy one and your life is documents, buy Claude.

Failure modes I will not hide

KOPY will sometimes be too brisk for a breakup text or a performance review. That is a feature of the latency budget. Take those to Claude (or a human). Claude will sometimes be too essayistic for “on my way.” That is a feature of a model trained to be thorough. Take those to a keyboard with a Continue or Agree tone.

Neither product should auto-send. I have seen people treat assistant output as speech. Don’t. The point of a 2-second draft is more glances per hour, not zero judgment.

Using both without dual-prompting yourself to death

My rule: if I will still be in the document in ten minutes, Claude. If I will have hit send in ten seconds, KOPY. I do not “Claude-ify” a KOPY draft unless the recipient is a customer, a reporter, or someone I have already hurt with a sloppy message. Escalation should be rare or you built a process that never ships.

Sibling comparisons: KOPY vs ChatGPT is the research-versus-reply version of this essay with a different assistant. KOPY vs Gemini is the ecosystem version. If your other tab is an editor, KOPY vs Grammarly. If it is swipe typing, KOPY vs Gboard. Category reading: keyboard vs chatbot vs app, plus robotic replies if Claude’s careful voice is what you are trying to protect on mobile.

Long context is a superpower that does not fit in a bubble

Claude can hold a repo’s worth of prose and still remember the constraint you stated 40 turns ago. A dating chat is 12 bubbles, a photo, and a joke that died. Feeding Claude the whole screenshot stack is how you get a reply that comments on a message from Tuesday. The model is doing what long context does: over-attend. KOPY is biased the other way — this message, this mode, this tone. That bias is wrong for a board memo and right for “you free Thursday?”

I tried stuffing more thread history into the keyboard request. Latency went up. RAM got less funny. The replies started hedging like a staff meeting. I cut the window back. Claude should keep the long window. We should not impersonate it in an extension. Apple’s height and memory budget is a product manager whether we like it or not.

Careful refusal versus a flirty Continue tap

Claude will decline or hedge when you ask it to be someone you are not, or to push a line you should not push. Good. A dating keyboard that moralizes in the input view is unusable, and a dating keyboard with no brakes is gross. Our modes are not a jailbreak. They are genre. If you tap Dating + Funny, you asked for play, not a manifesto. If you tap Work + Professional, you asked for boring competence. Claude’s refusals belong in a chat UI where you can discuss them. They do not belong as a modal over iMessage.

I still do not auto-send. The 2-second draft is a suggestion with a human still on the hook. If you need Claude’s more conservative judgment, escalate the message there before you send. That escalation should be rare. If it is daily, your life is not a keyboard job. It is a writing job. Pay for Claude and use us less. That is a valid outcome of this page.

Projects, artifacts, and the sitting-down ritual

Claude’s better features assume you will remain. Projects, artifacts, iterative critique. KOPY assumes you will vanish into the host app. There is no history sidebar in a keyboard that I would trust on a stranger’s phone over your shoulder. Ephemeral is a feature. If you want a paper trail of how you talk to customers, that is a CRM or a Claude project, not an input accessory.

I built the extension after a month of using Claude for every Slack ping. The writing got more considered. The people on the other end got more ignored. Nuance that never sends is self-care, not communication. Use Claude where sitting down is allowed. Use the keyboard where standing up is the job.

Decision rule

Choose Claude when the cost of a wrong nuance is higher than the cost of waiting. Choose KOPY when the cost of waiting is higher than a slightly flatter sentence you can edit in place. Most adults have both costs in one day. Buy tools for both clocks. Do not make a long-context model commute into every text field through the pasteboard. I already did that commute. I built a keyboard so I could stop.

If you want the iPhone keyboard landscape rather than the assistant landscape, best AI keyboard apps for iPhone 2026 is the shopping list. Claude will not be on it, correctly. It is not a keyboard.