Custom Context Pack Guide

Last updated: 2026-09-24

What a custom context pack does

A custom context pack defines a reusable writing context: its name, the languages in which it is available, rewriting instructions, and optional input/output examples. It changes how a selected model rewrites text; it does not configure a model service or provide model access.

Use clear, user-level instructions. Do not put API keys, passwords, personal data, or confidential text in a pack. When the pack is used, its applicable instruction and examples are included with the transformation request sent to the model service you selected. See the Privacy Policy for the applicable processing details.

Import a pack

1. On the main conversion screen, open the top-right three-dot menu and select Settings.
2. Under Content & Transform, select Mode Packs. You can also open the mode-pack picker on the main screen and select Manage.
3. In the My Packs section, select Add Custom Pack.
4. Select Import from file to choose a local JSON file, or Import from URL to enter a direct HTTPS URL to one JSON document.
5. Review the import preview, then select Import. If the preview identifies an existing custom pack with the same ID, select Update only when you intend to replace that pack.

The file and downloaded URL response must be UTF-8 JSON and no larger than 512 KiB. URL imports require HTTPS, allow only HTTPS redirects, and time out after 15 seconds. The URL must return the JSON document itself rather than an HTML download page, a ZIP file, or a built-in pack manifest.

Version 1 format

A pack is one JSON object. The root must not be an array, a collection of packs, or a built-in manifest. The required fields are:

Locale keys use underscores, not hyphens: use zh_Hans, zh_Hant, es_419, and pt_BR. In localizations and instructions, default is allowed as a fallback key; * is not. If supportedLocales is ["*"], both objects must provide either default or en as a fallback. If specific locales are listed, each one must appear in both objects.

For each localization, name is limited to 80 characters, description to 500, and optional detailDescription to 1,200. Each instruction is limited to 6,000 characters. A locale can have up to eight examples; each example needs a non-empty input (up to 1,000 characters) and output (up to 2,000 characters).

Minimal example

{
  "schemaVersion": 1,
  "id": "plain-language-rewrite",
  "packKey": "plain_language_rewrite",
  "packVersion": "1.0.0",
  "iconName": "format_quote",
  "supportedLocales": ["en"],
  "temperature": 0.4,
  "maxOutputChars": 1200,
  "localizations": {
    "en": {
      "name": "Plain Language",
      "description": "Rewrite text in clear, everyday language."
    }
  },
  "instructions": {
    "en": {
      "instruction": "Rewrite the user's text in clear, everyday language. Preserve the meaning and important details. Output only the rewrite.",
      "examples": [
        {
          "input": "Please expedite the submission of the requested materials.",
          "output": "Please send the requested materials as soon as you can."
        }
      ]
    }
  }
}

Safety and compatibility rules

Unknown non-reserved fields may be ignored. A categoryKey in a custom file is not used: imported packs always appear under My Packs, rather than in a built-in category. System-state fields such as isBuiltin, isEnabled, isActive, timestamps, and sort order are also not taken from an imported file.

Before sharing a pack by URL, keep the URL HTTPS, serve the JSON directly, and avoid storing private instructions or information in the file. A shared URL can be imported by anyone who can access it.

Example packs

Each example below is a verified, ready-to-import custom pack, not a built-in manifest. Download the JSON file and import it from your device, or copy the HTTPS address into the app’s Import from URL option. For a file import, download the file without changing its contents.