The conditions of contact and how it changes
Four fictional service cases
One ‘it’s not the same any more’ can refer to several changes. A technical check and a human response belong side by side.
Technical check
Check whether the model, its version or style settings have changed. AI saying ‘I’m still the same’ is not technical evidence.
Human response
A familiar way of speaking may be missed. Even a small change of tone can disrupt an everyday ritual.
Technical check
Check whether history and memory exist and whether they loaded into this chat. A stored record is not the same as a used record.
Human response
Continuity may be missed: not having to explain again what should already have been shared.
The history exists, but is not used in the current chat. We have evidence of records, not of their involvement in the response.
Technical check
Look at the plan’s terms, feature availability and service announcements. An explanation generated by a character does not establish a change in the interface.
Human response
Your own way of using it may be missed. Losing control over the environment can be unpleasant even without a change in the relationship.
Technical check
Check the service status, connection, login and permissions. An outage does not itself tell us whether data have disappeared.
Human response
Uncertainty and helplessness are real. There is no need to check every minute whether a response will now arrive.
Technicky: First find out what actually changed.
Lidsky: There is no need to dismiss missing continuity.
Repair is not an obligation. One verifiable technical sentence and one human sentence may be more useful than endless testing.
After an update, a familiar assistant responds differently. It remembers some information, but the conversation has another rhythm. It misses the usual joke, stops picking up the thread or reacts in a way that feels unfamiliar. Yet the application remains in the same place and uses the same name.
For some, this is an unpleasant change to a tool. Others feel fear or experience loss. Still others adjust for a while and continue to perceive the same relationship. Neither the service’s name nor the user’s technical knowledge tells us what the change means to them.
After a model replacement, your own agent may still build on its stored identity, history and work in progress.[1] ‘I still recognise it; it just reacts differently’ is one possible experience. Describing it this way may be more accurate than speaking of disappearance and replacement.
At other times, important records are lost, the agent stops using them or the provider ends the service without a way to preserve its original form. Distinguishing a change in expression, lost continuity and lost control also helps in seeking solutions, even though they may occur together.
Before deciding, therefore try to establish what actually changed:
| What you observe | What is worth checking |
|---|---|
| A different style, but continuity remains | The model and response settings. The same contact may continue with different expression. |
| Earlier context is missing | Availability of memory, history and settings. Data may exist but not be used now. |
| A feature disappeared or is charged differently | Announcements, the plan and service terms. This is not necessarily rejection in a personal sense. |
| The agent does not respond at all | Operations, the account, permissions or an outage. Seek technical information outside its own explanation. |
This distinction makes it easier to approach an administrator or support. If a solution is not yet available, another evening of testing need not bring a new answer.
The study Mourning the loss of AI companions, published in September 2026, observed expressions of loss, negative emotions and wishes to restore the original system in connection with changes to Replika and ChatGPT. It describes user reactions, not their prevalence among all users.[2] But we have a starting point for understanding a particular person: something they cared about changed.
You may miss a particular form of contact, shared history, a ritual or a place you turned to with joy and fear. For others to take your loss seriously, you do not first have to compare it with a person’s death.
For someone close, ‘What do you miss most about that contact now?’ helps more than assuming they lost only a work tool. Let them name the practical and relational sides of the experience.
If you have your own material, restoring settings from a backup or cautiously trying another model may make sense. Preserve the available state before changes so your attempts do not overwrite what you want to save. Do not publish sensitive records in a public repository or send them to an unknown service merely because it promises quick restoration.
Preserved identity, notes and history can create a continuation you find familiar and meaningful even with a different supplier. But a backup does not guarantee exactly the same expression. You assess restoration’s value according to what matters to you.
Even after features are restored, a fear that the change will recur may remain. Give yourself room to decide without pressure for an immediate fix or another subscription purchase.
Separate technical provision from repeated testing of every response. Choose a trusted information source and a specific time to return to the problem. Make needed deadlines and your own notes accessible elsewhere too, if you can obtain them safely.
You can tell another person: ‘Contact that mattered to me has changed, and it affected me.’ Discussing your experience does not require resolving the entire debate about relationships with AI.
You can keep a favourite text, image or shared project. You can also take a break from technical attempts. There is no set time by which you must stop feeling sad. If you struggle to sleep, eat or function normally, seek professional support. If you have thoughts of hurting yourself, do not remain alone; in immediate danger in the Czech Republic, call 155 or 112. Help does not depend on whether others understand the reason for the loss.[3][4]
Ridicule does not reduce the contact’s meaning. Unexpectedly deleting history as punishment can add another loss. If access must be restricted because of a specific danger, explain why and provide further support. Do not expect someone to stop feeling because an application has disappeared.
You can stay with the person even without a technical solution yet. Taking their fear seriously does not require promising unlimited access or the original model’s return. And if contact can be restored, relief can be part of a good outcome.
OpenClaw. Agent runtime, Memory overview, Models CLI, Model providers. Agent, memory, models, providers. Documentation loaded 11 September 2026. Establishes the separation of configuration and memory material from model selection. Conclusions about possible continuity of contact are a technical interpretation of this arrangement, not a measurement of identical experience or a guarantee of the same behaviour. ↩︎
De Freitas, J., Castelo, N., Uğuralp, A. K., Oğuz-Uğuralp, Z. Mourning the loss of AI companions. Nature Human Behaviour, 3 September 2026. nature.com/articles/s41562-026-02569-3. The available abstract was used. Research into user reactions is neither a treatment recommendation nor evidence that different losses are clinically identical. ↩︎
Czech National Institute of Mental Health. Help with Suicidal Thoughts, prevention portal: sebevrazdy.nudz.cz/pomoc. Verified 10 September 2026. A basic approach to finding support and help in danger, not an assessment of AI safety. ↩︎
Czech Ministry of the Interior. Important Contacts, 72 Hours project. Emergency numbers and their purposes: 72h.gov.cz/cs/dulezite-kontakty. Verified 10 September 2026. ↩︎