---
title: "Guides · Running AI coding agents"
description: "Practical answers about running AI coding agents: working several at once, keeping them running unattended, giving them credentials safely, reviewing what they changed, and where your code goes."
url: "https://intentic.dev/guides/"
updated: "2026-08-13"
---

## [How do you run multiple AI coding agents in parallel?](https://intentic.dev/guides/run-multiple-coding-agents-in-parallel/)

Give each agent its own checkout so they cannot edit the same file, then pick how much isolation the work needs.

Give every agent its own checkout, so two can never edit the same file at once. Git worktrees do this on one machine for free. Containers go further, giving each agent its own processes, ports and installed tools. Then run each on its own branch and merge one at a time, reviewing each.[Read the whole answer →](https://intentic.dev/guides/run-multiple-coding-agents-in-parallel/)

## [How do you keep a coding agent running after you close your laptop?](https://intentic.dev/guides/keep-a-coding-agent-running-after-you-close-your-laptop/)

Move the agent off the thing that sleeps. A detached session survives a disconnect; only another machine survives a lid close.

Run the agent somewhere that does not sleep. A multiplexer such as tmux keeps it alive when your SSH connection drops, but not when the machine suspends. To survive a closed laptop the agent has to be on a machine that stays awake: a desktop, a home server, a VPS. Everything else is a workaround.[Read the whole answer →](https://intentic.dev/guides/keep-a-coding-agent-running-after-you-close-your-laptop/)

## [How do you give an AI agent database or API access without leaking credentials?](https://intentic.dev/guides/give-an-ai-agent-database-and-api-access-safely/)

Keep the secret out of the conversation. The agent should operate a tool that holds the credential, never read the credential itself.

Keep the credential out of the model's context. The agent should run a tool that already holds the secret, not be told the secret and asked to use it. That means a secret store the process reads, credentials scoped to the narrowest rights the job needs, and separate keys per task.[Read the whole answer →](https://intentic.dev/guides/give-an-ai-agent-database-and-api-access-safely/)

## [How do you review code an AI agent wrote before it lands?](https://intentic.dev/guides/review-ai-generated-code-changes/)

Read the diff, not the summary. Make the agent's work land somewhere that requires a decision to merge.

Make the agent's work land somewhere that cannot merge itself, then read the diff rather than the agent's description of it. That means a branch per agent, every hunk reviewed before merge, and tests on the branch. The summary is a claim about the change; the diff is the change.[Read the whole answer →](https://intentic.dev/guides/review-ai-generated-code-changes/)

## [Where does your code go when you use a cloud coding agent?](https://intentic.dev/guides/where-your-code-goes-with-cloud-coding-agents/)

Two questions decide it: whose machine holds the checkout, and whose account holds the keys.

It depends on where the agent runs, and there are two questions: whose machine holds the checkout, and whose account holds the credentials. A cloud service clones your repository onto its infrastructure and holds tokens for you. A local agent keeps both on your machine and sends only the conversation to the model provider.[Read the whole answer →](https://intentic.dev/guides/where-your-code-goes-with-cloud-coding-agents/)