App parameters
Configure an app's topics, instructions, models, and template-defined behavior.
Parameters controls what a template-based app does: its topics, filters, instructions, cadence, and declared connector choices. Settings controls the app record itself, including name, description, and lifecycle. The available parameter fields belong to the template version used to create this app.
Change parameters
- Open the app workspace and choose Parameters.
- Review the current values. Field descriptions explain the template-specific behavior.
- Edit the supported fields. Text, multiline text, lists of chips, choices, switches, and numbers each preserve their corresponding value type.
- Check Default LLM model and connector selections if present.
- Choose Save changes and wait for the inline Saved confirmation.
Changes apply from the next run. They do not rewrite the output of work that has already finished. For an activated immutable release, publish and activate a new release to make the updated parameters part of subsequent release-backed runs.
Fields marked set at creation are read-only in this form. Use Settings to rename the app rather than trying to overwrite a creation-only title parameter. A populated numeric field cannot be cleared into an ambiguous value: enter a valid number that meets its constraints. In a chip list, Enter commits the typed chip instead of submitting the entire form.
Handle conflicts and validation
The form preserves edits while background data refreshes. If parameters changed elsewhere, Strive asks you to Reload. Reload replaces your unsaved draft with the current stored values; make a note of any values you want to reapply first. Review the fresh form and save your changes again.
A field validation failure keeps your draft for correction. A failed load offers Retry rather than presenting an empty form as valid configuration. If parameters are unavailable, this app may not have been provisioned with an editable parameter contract.
Parameter privacy
Parameters are restricted management information. Shared visitors do not receive the full parameter form or backend instructions. A template can explicitly expose selected values needed by the interface, such as a theme choice; those declared interface values are visible to app users. Keep credentials in connection setup, not in general text or prompt fields.
Template updates do not substitute a newer parameter schema for an existing app. This keeps defaults and validation tied to the app's provisioned version. Continue with Connector policy, Schedules, or Model selection.