Coding Agent
Build, review, and test software projects with branches, isolated worktrees, terminal tools, and reversible change review
🟢 No funds move. Coding can modify files and run commands inside the selected project checkout. Use an isolated worktree for changes that should not touch your main working directory.
Coding gives Minara a project-aware engineering workspace. The agent inspects the repository before editing, follows its local instructions, changes the smallest relevant surface, and validates the result with the project's own tools.
Use it to understand an unfamiliar codebase, implement a feature, fix a failing test, review a change, improve an algorithm, or work through financial engineering code with explicit assumptions about data, precision, and risk.
Start a coding task
- Open Coding in the Web UI.
- Create a new project folder or add an existing folder. Selecting an arbitrary folder from the machine requires the Minara desktop app.
- For a fresh Git task, leave Worktree off to use the selected local checkout, or turn it on in the composer to isolate the task.
- Worktree mode prefers
mainwhen it is available, then falls back to a valid default or current local branch. Use the branch picker to choose another local base; this selection does not switch your local checkout. - Describe the outcome and send the first prompt. Minara creates a
minara/task-*branch and managed worktree from the selected base before the agent starts operating. The project, checkout, terminal, files, and workbench tools stay attached to that task.
Minara reads root AGENTS.md and CLAUDE.md files when the task starts. It
also discovers nested instruction files and repository structure so it can
load the rules that apply to each file before making changes.
Projects, checkouts, and worktrees
A project is the repository or folder registered with Coding. A checkout is the concrete directory used by one task.
| Checkout | Best for | Behavior |
|---|---|---|
| Local | Small changes in the current working directory | Uses the project folder directly and sees its existing uncommitted changes |
| Isolated worktree | Parallel features, fixes, and experiments | Creates a task branch and Minara-managed Git worktree under its data directory |
| Permanent worktree | A long-lived branch checkout you manage yourself | Creates a Git worktree at a folder and branch you choose outside Minara's managed directory |
Outside Worktree mode, the branch picker lists local branches, shows the current branch and dirty-file count, and can create or check out a branch. In Worktree mode, it selects the base for the new task branch without switching the local checkout. Git still rejects unsafe branch switches when local changes would be overwritten.
What the agent can do
- Explore files, architecture, types, configuration, and project history.
- Edit, add, rename, and remove files inside the bound checkout.
- Run terminal commands, tests, type checks, builds, and project-specific verification.
- Inspect application previews and runtime behavior when the project provides a development server or preview command.
- Explain algorithms, data flows, failures, and tradeoffs alongside the code.
- Review an existing diff without changing it when you ask for analysis only.
Browser & Computer Use
Browser and Computer Use form one interaction capability. Minara can inspect page structure, capture screenshots, click, type, scroll, drag, and send keys while you watch the same session.
- In cloud environments, it operates visible cloud browser or computer sessions.
- On desktop, it can operate local browser and computer surfaces.
- It uses page structure for ordinary websites and visual computer controls for canvases, desktop applications, or controls without reliable selectors.
This is useful for checking a local preview, reproducing a UI bug, validating a responsive layout, or completing a browser-based development workflow. Minara rechecks the screen after state-changing actions and asks before consequential external actions such as publishing, purchasing, sending, or deleting.
Review every turn
After a Coding turn changes files, the response includes a change-set card with the affected paths, additions, and deletions. Open Review to inspect the diff.
Choose Undo to restore that turn when the files have not changed since the turn completed. Minara compares the current file contents with the recorded post-change state first. If another edit would be overwritten, the undo stops with a conflict and restores nothing.
Large or binary files may be shown without a reversible text snapshot. Treat the Git diff as the source of truth before committing.
Safety and Git boundaries
- The task works inside its bound checkout unless you explicitly expand the scope and the configured folder permissions allow it.
- Minara checks that the project directory is readable and writable before binding it to a task.
- Existing user changes belong to the user. The agent preserves them and avoids unrelated cleanup.
- The agent does not commit, push, create or switch branches, create a pull request, rewrite history, or discard changes unless you explicitly request that action.
- Coding does not bypass Minara's confirmation rules for financial operations or consequential browser and computer actions.
Example prompts
Explore this repository and explain its architecture, run commands, and main risks.
Create an isolated worktree, implement CSV export for the report page, and run the focused tests.
Find the root cause of the failing authentication test. Explain the diagnosis before changing code.
Review the current diff for correctness, security, and missing tests. Do not edit anything.
Open the local preview, reproduce the mobile layout bug, fix it, and verify the result at desktop and mobile sizes.Where to go next
- Use Deep Research when a coding task needs cited external evidence.
- Use Data Studio for generated live-data dashboards with a managed component and publishing workflow.
- See Web Dashboard for the rest of the Web UI.