What This Looks Like
A task works in one environment but fails, changes, or behaves differently in another. The difference may appear across apps, accounts, workspaces, models, modes, browsers, runtimes, product surfaces, agent configurations, integrations, or deployment environments.
Why Users Blame AI
The user often sees the same prompt or task produce different behavior and assumes the AI is inconsistent or broken. The actual difference may come from environment state: model availability, permissions, connector setup, memory, workspace configuration, tool support, runtime version, or product-specific behavior.
What to Check First
- Whether the same model, mode, and product surface are being used
- Whether connectors, tools, or integrations differ between environments
- Whether account, workspace, or permission state differs
- Whether memory, files, prior context, or saved settings differ
- Whether one environment has a newer runtime, schema, or product behavior
- Whether the task depends on undocumented behavior from the working environment
When This Is AI-Adjacent
Use this AI-Adjacent Issue when environment differences may explain why the AI task works in one place but not another. If the same environment produces unstable results across repeated runs, use the related Workbench Issues for variance, prompt behavior drift, or output change.