Learn as you go

Questions worth asking

• About your project. “Give me a plain-language overview of how this website works.” “Where does the contact form send messages?”
• About a change. “Explain what you changed and why, without code.” “What could break because of this?”
• About words. “What’s an API? Explain it with an example from our project.” Claude Code’s documentation also suggests asking for “a glossary of project-specific terms.”
• About options. “What are two other ways to do this, and what are the trade-offs?”

To ask without risking any changes, first switch the agent to a mode that doesn’t edit files. In the computer app, choose Plan for Claude Code, Grok Build, or OpenCode, or Read-only for Codex, in the agent settings’ Permissions column. See Plan before you build.

Ways to learn in Enjoy

• Ask about something you’re looking at. In Files, select text in a doc or code file and choose Start a conversation. Enjoy copies your selection into a new conversation’s message box without sending it. Add your question and say which file it’s from: “What does this part of the checkout file do?”
• Watch how the agent works. Select the status under the conversation’s title to open the agent activity panel. It shows each command, file, and result. Ask about any step you don’t understand.
• See what changed. When the agent commits its work, View changes under its reply shows each changed file, before and after.
• Ask for plain language every time. Add a line to your project’s Instructions: “Explain what you changed in plain language at the end of each task.” See Write instructions your agent will follow.
• Keep what you learn. “Save that explanation as a doc called ‘How the site works’.” If you switched to a mode that doesn’t edit files, switch back first, since that mode may keep the agent from saving docs. See Keep project knowledge in docs.
• Look up Enjoy’s own words in Words you’ll see in Enjoy.

An example

An agent’s reply mentions “adding an environment variable.” You ask:

“What’s an environment variable, and why did you need one here? Explain like I’m new to this, using our site as the example.”

Then: “Add that explanation to my ‘How the site works’ doc.”

Common pitfalls

• Nodding along. If a reply doesn’t make sense, say so. Asking costs a moment, and acting on a misunderstanding costs more.
• Learning in the middle of a task. Side questions fill the conversation with detail the task doesn’t need. Ask them in a separate conversation. See Use one conversation per task.
• Taking explanations as fact. Agents can be wrong. If something matters, ask how it knows, or ask it to show you.