Your first task

Before you start, install BIGGI, open a project folder, and connect a model provider.

1. Open BIGGI

Select the BIGGI icon in the VS Code Activity Bar. The sidebar opens with a new local session.

Use Open in Tab from the editor title or Command Palette when you want more room. The sidebar and editor tab use the same runtime, providers, and session data.

2. Choose an agent

Use the agent selector beside the prompt:

  • Choose Code for a normal implementation task.
  • Choose Ask for an explanation without edits.
  • Choose Plan when you want a plan before implementation.
  • Choose Debug for a reproducible defect.
  • Choose Gameplay, Game Architect, Tech Art, or Perf for game-specific work.

See Using Agents for the full set.

3. Describe a bounded task

Start with a request that has a visible result:

Add input validation to the player-name form. Run the relevant tests and show me the final diff.

For a game project:

Use the Gameplay agent to add a coyote-time window to the player jump. Inspect the existing controller first, make the smallest change, and verify it with the available game tools.

Mention constraints, acceptance criteria, and files when you know them. Type @ to attach a file or terminal as context.

4. Review permissions

BIGGI shows a permission request when an action is configured to Ask. Review the tool, command, or path before choosing:

  • Allow once for this action
  • Always allow for matching actions
  • Reject to keep the agent from running it

Rules can be changed under Settings → Auto-Approve. Keep commands, external directories, sensitive files, browser control, and game execution on Ask until you trust the workflow.

5. Review the result

Read the agent summary, inspect command and test output, and open the diff. Ask BIGGI to correct anything that does not meet the request.

Snapshots can restore files changed by the session, but they are not a replacement for Git. Commit work you want to keep.

Next workflows