Before you start

LoneAct works inside a project folder: a directory you explicitly authorise. The Agent's file, terminal, and browser tools only work inside that folder.

A working LoneAct account and current plan whenever you need cloud, remote grants, or plan capabilities.
A project directory ready to hand to the Agent, or an authorized project you can reach remotely.
The LoneAct local service running if you plan to use file, terminal, or browser tools.

Start with Local Web on your first run

Local Web makes it easiest to confirm the project path, tool permissions, and execution results; move to the IDE or cloud entry point once you are comfortable.

Four steps to your first run

Choose an entry point and prepare a model

Open Local Web, or open the LoneAct plugin in VS Code / JetBrains; sign in only when you need Cloud or remote access. The cloud workbench needs an authorised device to be online.

Open a project folder

Select a project directory and confirm the LoneAct service can reach it. The project name, path, and execution scope are fixed to that folder.

Choose a model, write the goal

Use the workspace default model or switch from the Composer model selector. State results, constraints, and acceptance criteria rather than only steps.

Approve and verify

Approve prompts when the Agent needs to write files, run a terminal, or control the browser. When it finishes, review the diff, tests, and Reviewer conclusion.

Write a good first task

Fix a problem

"Fix the login endpoint returning 401 when a token expires, add a test for the failure branch, and run pnpm test auth."

Deliver a feature

"Add config export to the settings page; keep the existing API compatible, add tests, and list the changed files when you are done."

Understand a project

"Read the payment flow in this repository and list its entry points, data flow, external dependencies, and the three highest-risk change areas."

Hand it to the team

"Break this goal down for the project Agent Team; Planner gives the plan first, Executor implements, and Reviewer checks before delivery."

First-run checklist

Confirm these facts before you widen the scope

The project path is correct, and unrelated directories are not exposed.
The current model and plan are available, and the model name is the one you expect.
File and terminal operations run after approval, and the results are visible in the conversation.
Changes, tests, and open items are written back to the conversation or task record.

Next step

Read Core concepts to understand project folders and Agent teams, or go straight to Models and your own key.