# Should saying thanks change project files?

Canonical: https://uvilno.com/answers/can-a-chat-message-change-files-accidentally
Updated: 2026-10-27

A conversational acknowledgment should not initiate generation, modify files or consume model allowance. Uvilno routes replies separately from build and edit requests. Ambiguous instructions still need clear intent, so describe the change explicitly and inspect the run state rather than assuming every message requests code.

A chat composer serves both conversation and work. Acknowledgments such as thank you or got it are different from remove a button or fix a failing form. The ingestion guard can return a local professional reply without reserving a build or invoking the provider.

Do not combine an important edit with vague praise and expect targeting to be obvious. State the exact element, route and desired behavior, optionally using a context mention. If a message unexpectedly starts work, keep the previous version and inspect the captured request before retrying.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Social reply | Recognized pure acknowledgments bypass generation. | Send a simple thanks message and check for no build run. |
| Edit intent | An explicit action enters the normal edit flow. | Use a clear route and expected behavior. |
| Safety | Saved versions remain the comparison point. | Review the change summary for actual file modifications. |

## Steps

1. Keep acknowledgments separate from requested changes.
2. State actionable behavior precisely.
3. Check that no generation run starts for a social reply.

## Editable starting brief

Refine only the duplicate sign-in action in the selected navigation. Remove the redundant control while preserving the actual account flow, dashboard destination, accessibility and unrelated routes. Locate the relevant source before changing it, verify the requested result and keep ordinary acknowledgments separate from code-modification requests.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)