Manage prompts and defaults
Reuse task instructions and review the defaults applied to new work.
Saved prompts make a recurring request easier to reuse. Defaults supply starting choices for new sessions or integrations. Review their scope so a change affects the work you intend.
Save a useful prompt
Open Settings → Prompts and use the available create or edit action. Give the prompt a clear name and content that describes an outcome, constraints, and verification. Use repository-specific context where the editor offers that scope.
A prompt macro begins with !. The editor adds that prefix automatically; use lowercase letters, numbers, and underscores, for example !review_code. Review the inserted prompt before sending it in a session.
Avoid embedding credentials or environment-specific temporary links. Use secrets and stable source references instead.
Review root and system instructions
Where a root or system prompt is exposed, treat it as shared agent context. Check the selected prompt and revision before starting work. A saved edit should not be assumed to rewrite instructions already frozen into an existing session.
Use repository rules for persistent project conventions and skills for a specific repeatable procedure. Keep one source of truth for a rule rather than copying conflicting versions into several prompts.
Check defaults and identity
Review the model defaults for new sessions and supported integrations. A per-session model choice does not automatically replace those defaults. Availability still depends on provider connections and model access policy.
Check the workspace Git commit author settings and your account's linked GitHub identity when attribution matters. Author identity is separate from installation authorization and repository access.
For model selection use Choose a model; for GitHub identity use account security.