Write your draft
Type the message in a supported editable field in chat, email, notes, a browser, or another Android app.
Write your message in a supported Android text field, type your chosen trigger at the end, and ControlG rewrites the text in place. Improve grammar, clarity, tone, or translation without opening another app.
The trigger is part of the action you configure. It activates only after you type it.
Type the message in a supported editable field in chat, email, notes, a browser, or another Android app.
Add the configured trigger, such as gg, at the end of the draft. ControlG detects the completed trigger once.
ControlG selects the original field content and replaces it with the result, without leaving the current app.
A typed trigger is faster than copying a draft into a separate chatbot. It also makes the action visible: you write the text first, then deliberately type the trigger that starts the rewrite.
Create different actions for different outcomes. You might use gg for grammar, pp for a polished professional tone, or a trigger of your choice for translation. Each trigger maps to an instruction you control.
ControlG works in many Android apps that expose a standard editable field through the Accessibility framework. It ignores password fields. Some custom editors and secure apps may not support reading or replacing text.
Turn an informal draft into clear English for Slack, Teams, or another supported chat field.
Fix grammar and tone directly in the mobile compose field before sending.
Make a response polite, concise, and easier to understand with a dedicated trigger.
Write in the language you know, then use a translation action for the language your reader needs.
Improve longer answers in supported web forms without moving the text into another app.
Choose action names, prompts, providers, models, and unique typed triggers.
Android may also require background access so the trigger can work reliably after the ControlG app leaves the foreground. The onboarding flow explains each setting before you enable it.
The Accessibility service is required because Android does not otherwise let ControlG detect a user-configured trigger and replace text inside another app.
Built-in AI text is processed through ControlG's Azure service for the request and is not stored as a rewrite history. Optional provider keys remain encrypted on the Android device.
It needs the permission to detect your configured trigger in the active editable field and place the rewrite back into that field. The disclosure appears before Android Settings opens.
The trigger is detected from changes to a supported editable field, so it is not tied to a special ControlG keyboard.
No. Password fields are ignored. Some secure or custom fields may also block the workflow.
Yes. Android triggers are configurable per action and sync with the action for signed-in accounts.
Start with 1,000 built-in AI rewrites, or connect your own supported provider.
Get ControlG for Android