The chat works with your context
Chat history provides context for follow-up questions. Start a new chat for a different project to avoid mixing requirements. Upload the files that are needed; mentioning a filename does not grant access to your computer or game server.
Write a clear request
- State the goal: explain, review, repair or create.
- Add the framework and version, relevant resources and the affected workflow.
- For errors, include the exact message, reproduction steps and expected behaviour.
- Define the scope: which files may change, which interfaces must stay the same and which tests matter.
Files and follow-up questions
Use the attachment control for relevant files or resource packs. Remove passwords, private keys and unnecessary personal data before uploading. Answer follow-up questions in the same chat rather than starting a conflicting parallel task.
Use the result
Review the answer and any supplied files. Make follow-up changes specific, for example “Keep the permission check and only change the error message”. Use Agent Mode when you need a visible review of changes across connected files.
Example prompt
Explain this client.lua in plain language. List events and dependencies first. Do not change any files yet.