HelloKeyboardAI 2.1.0-1: Documented AI Triggers, Dependencies, and Version Caveats

Key points

• The package stanza identifies HelloKeyboardAI as version 2.1.0-1, package identifier com.zqbb.hello.keyboard.ai, and architecture iphoneos-arm.
• The listed dependencies are mobilesubstrate version 0.9.5000 or newer and preferenceloader.
• The description documents keyboard, screenshot, and copy actions for AI-assisted text and image processing.
• Examples include translation, text polishing, and image understanding; Smart Response Mode offers AI persona presets.
• The package stanza and structured depiction identify different versions, so later depiction details should not automatically be attributed to 2.1.0-1.
• The depiction mentions Taurine, Dopamine, Bootstrap semi-jailbreak, and NathanLR in connection with specified iOS versions, while noting that unc0ver was not tested for iOS 14.

What the package record identifies

The official package stanza names the package HelloKeyboardAI and gives it the identifier com.zqbb.hello.keyboard.ai. The listed package version is 2.1.0-1, and its architecture is iphoneos-arm. The entry places it in the Tweaks section and marks it as commercial metadata. zqbb is listed as both maintainer and author.

The package record lists an installed size of 2,448 KB and a package size of 519,466 bytes. It also provides cryptographic checksums for the package, including an MD5 value and a SHA-256 value. These details identify the package record and can help users compare the build offered by a package manager with the record they are reviewing. They do not, by themselves, describe the feature set or establish compatibility with a particular jailbreak environment.

• Name: HelloKeyboardAI
• Identifier: com.zqbb.hello.keyboard.ai
• Version: 2.1.0-1
• Architecture: iphoneos-arm
• Section: Tweaks
• Maintainer and author: zqbb

Documented AI actions

The product description says users can quickly invoke presets through keyboard, screenshot, or copy actions to process text and images with AI assistance. The source gives translation, text polishing, and image understanding as examples of the kinds of tasks the assistant can handle.

The description also names Smart Response Mode. This mode is presented as providing flexible AI persona presets tailored to different needs. The supplied material establishes the existence of these presets and the mode, but it does not provide a complete list of personas, explain their individual behavior, or state which presets are included in the package identified as 2.1.0-1.

The source describes several ways to trigger the assistant, including gestures, the dictation key, and toggle keys. It does not give a complete list of default assignments or state that every trigger is available in every supported environment. Accordingly, users should treat the trigger categories as documented capabilities rather than assume a particular control layout.

• Keyboard actions can invoke AI presets.
• Screenshot actions can send screenshots for AI processing.
• Copy actions can process text after copying.
• Examples include translation, text polishing, and image understanding.
• Smart Response Mode provides flexible AI persona presets.

Copy and screenshot processing

The description specifically says that copy tokenization processes text at the SpringBoard layer after copying. This identifies the location and timing described by the author: the copy operation occurs first, followed by processing at the SpringBoard layer. The source does not explain every type of text that can be handled or provide performance limits for large selections.

Screenshot Action is described as sending screenshots directly to the AI for processing. The depiction also mentions an alternative “snapper3 solution.” Since the supplied material does not define the precise differences between the direct screenshot action and that alternative, it would be unsafe to assume that they use identical triggers, interfaces, or processing paths.

The description presents screenshot-based processing as a way to handle images or text without injecting into apps. This is a stated design advantage. It should not be expanded into a guarantee about every application, image format, screen state, or system configuration, because the supplied records do not provide those conditions.

• Copy tokenization is described as operating at the SpringBoard layer after copying.
• Screenshots may be sent directly to the AI for processing.
• The depiction references snapper3 as an alternative screenshot solution.
• The source does not specify retention, encryption, service endpoints, or response limits.
• The description does not provide a complete list of supported content types.

Dependencies and package requirements

The package stanza lists two dependencies: mobilesubstrate at version 0.9.5000 or newer and preferenceloader. These are the explicit package-level requirements supplied for version 2.1.0-1. The stanza does not list a minimum iOS version or identify a specific jailbreak as a package dependency.

The package manager should normally evaluate dependency resolution before installation, but the record alone does not show whether installing the package would require other upgrades or create a conflict with an existing setup. Users should review the proposed transaction and confirm that the exact package version being installed matches the version they intend to evaluate.

• mobilesubstrate (>= 0.9.5000)
• preferenceloader
• No minimum iOS version is stated in the package stanza.
• No specific jailbreak is listed as a package dependency.

Compatibility information and the version mismatch

The supplied records do not describe the same release. The package stanza identifies the package as 2.1.0-1. In contrast, the structured depiction identifies version 6.3.0-9, reports an information date of August 15, 2026, and lists iOS versions from 14.0 through 17.3.1. The depiction also contains changelog entries for 6.3.0-9 and numerous earlier releases. Those later entries should not be treated as evidence that every listed change exists in 2.1.0-1.

The depiction states that iOS 14 was tested on Taurine and was not tested on unc0ver. It lists Dopamine support for iOS 15.0–16.5 and support for Bootstrap semi-jailbreak and NathanLR on iOS 17.3.1. These statements are useful compatibility notes for the release represented by that depiction. They are not enough to establish that the separately identified 2.1.0-1 package has the same compatibility range.

The package stanza itself supplies no iOS range. Before installation, users should compare the version displayed by their package manager with the version associated with the applicable depiction. A later depiction, later changelog, or broad compatibility range should not be assigned to 2.1.0-1 without a matching package record.

• Package stanza: 2.1.0-1.
• Structured depiction: 6.3.0-9.
• Depiction range: iOS 14.0–17.3.1.
• iOS 14: tested on Taurine; unc0ver not tested.
• iOS 15.0–16.5: Dopamine is listed.
• iOS 17.3.1: Bootstrap semi-jailbreak and NathanLR are listed.

What users should verify before installation

The first check is release identity. Confirm the package name, identifier, and exact version shown in the package manager. If the offered build is 2.1.0-1, do not use the 6.3.0-9 changelog as a feature list for that build. If the offered build corresponds to the later depiction, evaluate the compatibility statements in that depiction against the device and environment being used.

The second check is dependency resolution. The supplied package requires mobilesubstrate 0.9.5000 or newer and preferenceloader. Review any proposed upgrades, removals, or conflicts before accepting installation.

The third check concerns AI processing. The description says copied text and screenshots can be processed by AI, but the supplied records do not state which service receives the material, how data is retained, whether processing is encrypted, or whether an account is required. Users should inspect the current settings and relevant provider information before sending passwords, private messages, personal documents, or confidential images.

• Match the offered version to the applicable depiction.
• Review dependency changes before installation.
• Confirm that the jailbreak and iOS notes apply to the same release.
• Check current AI-processing and privacy settings.
• Avoid sending sensitive material until handling details are clear.

Frequently asked questions

Original-source editorial · Published 2026-09-01 · Next Jailbreak