# Coding agents

Nock's built-in engineering engine is V3Code Terminal. It can work in a project without installing another coding agent. You can also hand a task to an agent you already use, including Claude Code, Codex, or Grok Bot when connected. Selecting a coding agent is different from choosing the model for Nock's voice conversation.

## Start with the built-in engine

V3Code Terminal runs locally with Nock. It can index the project, search for relevant code, use language-server information where supported, edit files, and run commands and tests. For larger tasks it can coordinate workers; the Tasks board shows progress and questions while the notch remains available for another conversation. Give it a specific project and outcome, then inspect the files and test results it reports. [Background tasks](/nock/background-tasks) explains how to follow or stop work.

## Bring your own agent

Install and sign in to a supported external agent through its setup process. Confirm its account and billing mode there; an eligible subscription may cover work, but limits and any saved API billing configuration still belong to that provider. Availability and exact controls vary by integration and build.

Use a specific project folder. Save or commit work you need to preserve before requesting edits. Avoid two agents editing the same files at once.

## Give a bounded task

Try “Have Codex review the tests in my project without changing files.” If you want a particular external agent, name it; otherwise Nock can use its built-in engine. Identify the folder and say whether you want investigation or implementation. Read the selected project path on the task before proceeding if more than one folder has a similar name.

For an edit, define the outcome and verification: “Fix the failing parser test, run that test, and summarize the diff.” A request to explain a bug should not silently become a request to change the project.

## Follow the work

The task card reports progress, questions, and results. For a connected agent, choose model and effort using the coding card's available options; changes apply to a subsequent task or follow-up. Available options come from the integration and can change.

Use **Stop task** to stop coding work. Sending another voice message does not necessarily interrupt the running task. Follow-ups can queue behind it. If Nock quits, a task may be marked interrupted rather than resumed automatically.

## Review before keeping

Check the file diff, tests, and any remaining failures. A “complete” task status describes the run, not a guarantee of correct code. Built-in and connected coding agents can send relevant project content to their configured model providers; the exact destination depends on your settings.

## Let an external agent drive

If your build offers an external agent as the active conversation, choose it in the agent picker and check the name shown in the notch before speaking. That agent handles its own turns until you switch back. Do not assume that selecting an agent grants it new permissions or makes it the default for every future task. If your build only offers task handoff, use the bounded task flow above; voice control for that integration is not available there.

See [Coding permissions](/nock/coding-permissions) and [Background tasks](/nock/background-tasks).