Text feeds are created under Form Settings -> AI Text and use Anthropic.
Model lifecycle #
Claude Sonnet 5.5 is the recommended default for new feeds. Existing selections are preserved. Older Claude models that Anthropic still lists as active may remain selectable with the plugin’s Superseded label and a recommendation to compare their newer replacement’s behavior, capabilities, and pricing. Legacy is reserved for an official provider status; the plugin does not currently apply it to any selectable Claude model.
Deprecated models are retained only for feeds that already use them. A retired model blocks every execution path until an administrator saves a supported replacement.
Effort and Thinking #
The controls and their choices update immediately when the model changes, including recognized Custom Model IDs. Unsupported explicit settings reset to supported defaults, with a visible explanation. Initial rendering preserves invalid saved values for correction. The server validates these combinations again before generation, including feeds imported or edited programmatically. Unknown custom IDs use provider defaults and have no reviewed advanced controls.
Provider default omits the corresponding request parameter. The page shows the reviewed model defaults. Opus 5.5 defaults to medium effort; Sonnet 5.5 defaults to high. Where supported, explicit effort levels are Low, Medium, High, Extra high (xhigh), and Maximum (max). Higher levels may increase latency and token usage. Haiku 4.5 has no effort control; Sonnet 4.6 does not accept Extra high.
Thinking choices depend on the model:
- Opus 5.5 and Fable models support adaptive thinking only, which is also their default. The Thinking control is hidden unless an incompatible saved value needs correction.
- Sonnet 5.5 supports adaptive or Between tools only, which produces no upfront thinking in these single-turn feeds without tools. Between tools only requires low, medium, or high effort.
- Opus 5 permits disabled thinking only with low, medium, or high effort.
- Sonnet 5, Opus 4.8/4.7, and Sonnet 4.6 support adaptive or disabled thinking. Older models may default to disabled. Deprecated manual thinking on adaptive-capable models is not offered.
- Haiku 4.5 supports a manual thinking budget. The budget must be at least 1,024 tokens and strictly less than Max Tokens. Recognized older custom IDs follow their reviewed control contract.
Thinking also hides when the selected effort leaves only adaptive thinking and it is the model’s default. Choosing a compatible effort makes the alternative modes available again.
Adaptive thinking may skip reasoning for simple requests. Thinking uses part of Max Tokens and is included in billed output tokens. The plugin does not display thinking summaries to visitors.
Speed #
Fast mode is an explicit opt-in research preview, off by default. It is available for Opus 5.5, Opus 5, and Opus 4.8, requires provider account access, and has premium pricing. Access errors are reported as failures. Requested speed and provider-reported actual speed are recorded separately; actual speed may differ or be unavailable. Historical ledger rows remain unknown.
See the official thinking, effort, and fast-mode documentation for provider behavior and pricing.
Max Tokens #
The maximum number of output tokens the provider may return. Tokens are pieces of text rather than words; one word can use one or several tokens. A larger value allows a longer answer and can cost more. It does not reserve or guarantee that much output.
Enter a positive whole number. A blank value uses 4,096. For listed models, the plugin rejects a value above the known model output limit. Recognized custom model IDs and pinned aliases use the same reviewed ceiling. For an unknown custom model, consult the provider because the plugin does not know its ceiling.
Some models always reason before they answer, and Claude Fable 5.1 cannot be asked not to. That reasoning is charged against this same limit, so a value sized only for the answer can be spent before the answer begins. Allow headroom on those models rather than trimming to the shortest value that once worked.
Choose a limit suited to the task. A category label may need tens of tokens, a short summary a few hundred, and a long draft considerably more. A JSON multi-field response needs room for the whole object, including every property name and value. If Anthropic reaches Max Tokens before finishing, the response is incomplete and cannot be applied safely. The plugin records a max_tokens diagnostic under GravityOps -> AI Feed -> Ledger; raise the limit and retry.
System Prompt #
Optional standing instructions describing how the AI should behave: role, tone, rules, boundaries, audience, and output style. Merge tags are supported, although stable instructions usually belong here and entry-specific content usually belongs in User Prompt.
Example: You are an internal support assistant. Be concise, do not invent facts, and do not include personal contact information in the summary.
User Prompt #
The required task and content for this request. Use the merge-tag button to insert form values.
Example: Summarize this request in three bullets for the support team: {Request details:5}
Anything inserted through a merge tag is sent to Anthropic. Do not insert {all_fields} without understanding how much and what kind of entry data it includes.
Output Mode #
- Single target field saves the complete response to one selected Gravity Forms field.
- JSON multi-field mapping asks the model for named, typed values and saves each through the selected destination field’s storage rules.
Target Field #
Shown for single-field output. Choose the field that receives the generated text. The selector lists only fields that can store generated output, so a field type that cannot receive it is not offered; the same check runs when the feed is saved and again before generation. Text, Paragraph, and Hidden destinations require Pro or higher. Other supported field types require Premium or higher and are shown with an upgrade explanation when the current plan cannot use them.
Regular Paragraph Text fields receive plain text. HTML output sent to one of them is flattened rather than dropped: paragraphs and line breaks become blank lines and newlines, entities are decoded, and the tags are removed. If Use the Rich Text Editor is enabled on a Paragraph Text field, the field receives sanitized HTML: output that already contains HTML tags is kept as written, and Markdown output is converted first. Either way the result passes through wp_kses_post(), so unsafe markup such as scripts is removed. Write the prompt for one format or the other; output that mixes HTML tags with Markdown syntax is treated as HTML, leaving the Markdown characters visible.
Output Map #
Shown for multi-field output. Add one row per generated value:
- Response name is the exact JSON property requested from the model.
- Destination field is the supported whole Gravity Forms field that receives the value.
- Output instructions describe the content required for this one destination.
Keep common context and behavior in the System and User Prompts. Put type-specific or destination-specific requirements in Output instructions so fill-empty execution can remove both an already-populated property and its instructions from the provider request. A destination can be used by only one row; after it is selected, the other rows disable that option.
Existing Values #
Shown for after-submission text feeds and used by synchronous, asynchronous, and Gravity Flow execution:
- Fill only empty targets asks the provider only for destinations that are logically empty. This is the default for a new feed and can avoid unnecessary provider usage.
- Overwrite configured targets requests and replaces every configured destination.
An administrator rerun always force-overwrites, regardless of this setting. Frontend generation has no saved entry yet, so Existing Values does not apply there.
Execution Mode #
Shown only for after-submission feeds.
- Synchronous waits for generation during submission processing. Use it when the generated value must be available to an immediate confirmation or another immediate operation.
- Async queues generation after submission. Use it for slower requests when the visitor does not need the result in the immediate confirmation.
Notification Options #
Premium/Agency settings can opt completion/failure events into administrator reruns and Gravity Flow runs. Normal post-submission feeds already emit their feed event. See the notifications and reruns reference.
