Code with AI
BIGGI turns a conversation into a reviewable engineering workflow. The agent can inspect the project, search code, edit files, run commands, use language servers, call connected tools, and explain what changed.
Choose the right interaction
| Need | Use |
|---|---|
| A multi-file change or investigated fix | Chat with Code or Debug |
| An explanation without edits | Ask |
| A design before implementation | Plan or Game Architect |
| A game mechanic or engine integration | Gameplay |
| Shader, material, VFX, or render-pipeline work | Tech Art |
| Frame-time, allocation, draw-call, or loading work | Perf |
| A short continuation while typing | Autocomplete |
| Several independent tasks | Agent Manager |
Give useful context
BIGGI starts from the open workspace and active editor state. Type @ in the prompt to attach a file or terminal, or describe the relevant path and behavior.
For strong results, include:
- The outcome you want
- How to reproduce the current behavior
- Acceptance criteria
- Constraints, such as engine version or files that must not change
- The verification command or visible behavior that proves the task is complete
Review the work
Tool calls appear in the conversation. Permission-controlled actions pause for approval. When the task changes files, inspect the diff and verification output before keeping it.
Use snapshots for quick session-level recovery and Git for durable history. In Agent Manager, each managed worktree also has a worktree diff and its own branch.
Keep sessions focused
Start a new session when the goal changes substantially. Use project instructions, memory, and indexing for durable context instead of carrying unrelated conversation history forever.
Continue with Your First Task or learn how agents differ.