Your first project in Firstbeam

Install the desktop

Get the current Windows x64 installer from Downloads. Close an older Firstbeam window before updating. The desktop package includes the Firstbeam CLI; you do not need to download a separate archive to use it.

Your projects stay in their original folders. Open an existing repository or choose a workspace directory. Firstbeam uses that folder for project context; installing the app does not move your code into a hosted editor.

Connect an engine and account

Firstbeam coordinates the coding engines you already use. Install and sign in to the selected engine, then check it in Settings → Engines. A Firstbeam account and an engine account are separate: access to one does not automatically authenticate the other.

• Select the intended engine account.
• Review the model and permission level before sending.
• Use engine diagnostics if installation or authentication fails.

Start with a bounded task

Describe the outcome, the relevant files and how you will check the result. For an existing project, ask the agent to inspect its instructions and current implementation first. Keep the first task small enough that you can review all changed files.

Inspect the project instructions and the current settings page.
Fix the misaligned action buttons.
Preserve saved preferences and verify the narrow layout.

Review, test and return

Use project files, Git changes and the terminal to inspect the result. A completed reply is not a substitute for a passing check. Save useful decisions in project memory, and return to the same conversation when you need to continue the work.

An example first request

Try an inspection before an implementation: ask which command runs the tests, where the settings page stores preferences and which files own its layout. Then ask for one bounded correction and a check that persisted preferences still work. This gives the agent a concrete outcome and gives you a small diff to review.

Read the repository instructions first.
Explain the current settings persistence.
Fix only the action-button alignment.
Check the result at desktop and narrow widths.

If the first task does not start

Separate application sign-in from provider sign-in. Check the selected engine in settings and confirm that its own command can run. If the terminal launcher works but the provider fails, use engine diagnostics rather than reinstalling the entire workspace. Send support the app version, engine name and error category without credentials.