Browse generated code

The Code tab connects something visible in Build to its generated source. It is also a precise starting point for a developer.

Open a file

Choose Code in the editor navigation. The left side shows a file tree; the right shows the selected file with line numbers. Available roots can include Web App, Mobile App, Admin App, Backend, or Shared. Choose the root and file that match the surface you are investigating.

Jump from a selected element

In Build, choose Select element and click a heading, button, form field, or card. In the element controls, choose <> to jump to its source. Ahamo opens Code, selects the connected file, and highlights the related line.

Confirm that the file and highlighted line match what you selected. Repeated elements may share one source location, so note every screen where a later change could appear.

Know the read-only boundary

Code displays text files with syntax highlighting and previews supported image files. It does not provide a manual edit or save action. Request changes through a Build prompt or the supported visual controls, then return to Code only if you need to inspect the result.

Manual code editing remains unavailable; see capability status for how unavailable work is labeled.

Prepare a developer handoff

Give the developer only the context needed to reproduce and locate the issue:

• the screen and action that reveal it;
• the expected and visible result;
• the selected element, file path, and highlighted line;
• the behavior or other screens that must remain unchanged.

For example: “On the mobile confirmation screen, the service name wraps over the time. The selected summary card opens in this file and line. Keep the desktop layout and confirmation behavior unchanged.”

After any change, return to Build and repeat the original journey. Reading the expected file does not by itself prove that the app works.

Next: Preview and visually edit your app and review history and undo a build.