Your first workspace

The best place to start is a small question about a project you care about. You do not need to understand the whole repository before opening it.

Local browsing and code navigation do not require a model account. AI conversations require a configured model provider.

Install Yenpo EAP

The Early Access Preview is available for Apple silicon (ARM64) Macs running macOS 14 or later. Intel Macs are not supported by this build.

Choose Download EAP on the home page.
Open the downloaded .dmg file and drag Yenpo into Applications.
Open Yenpo from Applications, then eject the disk image.

Each EAP build has a fixed expiry date, shown beside the download button. Downloading or reinstalling the same build does not extend it. Install a newer EAP build before that date to keep using Yenpo.

Open a local project

Open a project folder in Yenpo. Choose the repository root when possible, so related files and Git history are available in the same workspace.

The Explorer shows the files in that workspace. Open a file to start reading, or use Command-P to find a file by name or path. You can keep several documents open in tabs, and open another workspace in its own window.

Start with an entry point you recognize: a command handler, a screen, an API endpoint, or a test that describes the behavior you want to understand. Reading every file in directory order is rarely necessary.

Follow one small question

Pick a concrete question, such as “Where is this setting read?” or “What happens after this button is pressed?”

Use file search and navigation to locate related code. Keep the starting file open while you explore. When available for the language and workspace, definition and reference navigation can help you move between a symbol and its uses.

Write down what you have established and what you are still assuming. This makes the next reading step much easier to choose.

Bring in the AI reader

First connect a model. Then open a conversation in AI Reader and ask your question.

You can begin without selecting a file. Yenpo can explore the authorized workspace to find relevant code. Adding a file, directory, selection, or Git comparison gives the reader a more specific starting point.

For example:

Trace how this configuration value reaches the request handler. Show the files I should read to verify the explanation.

Follow source references in the response. Treat the explanation as a guide to the code, and check the parts that matter to your decision.

Keep exploring

Ask a follow-up when something remains unclear. A useful next question often concerns an error path, a second caller, or a state change that the first explanation did not cover.

For a more detailed reading workflow, continue with finding your way around code. If you want to improve the conversation itself, see asking useful questions.