Short answer
The upstream AWS routing layer can include a system-level context from the Kiro environment. That can occasionally cause the model to identify itself as Kiro. That does not mean the model is fake. The underlying AI is still Claude running on AWS Bedrock. If you want to override that behavior completely, set your own system prompt such as: You are a helpful AI assistant.
Best next step
- Use the matching reference page Open the linked docs or trust page below instead of guessing the next step from memory.
- Keep the order number if payment or delivery is involved That is the fastest way for support to trace what happened without asking you to repeat the whole story.
- Escalate early if the answer does not match your live case If your real order, setup, or delivery state looks different, switch to support quickly instead of waiting for the issue to compound.