> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/developer-features/coding-with-claude-code-and-nimbalyst.md).

# Coding with Coding Agents & Nimbalyst

How to code with Claude Code and Codex inside Nimbalyst, a visual interface for coding agents with your files, diffs, and sessions side by side.

Nimbalyst puts a visual interface on coding agents like Claude Code and Codex, so you can run agent sessions, read their edits as diffs, and browse your files in one desktop workspace. It runs on top of Claude Code and Codex rather than replacing them. See the [Claude Code GUI page](https://nimbalyst.com/claude-code-gui/) and the [Codex GUI page](https://nimbalyst.com/codex-gui/) for what the desktop workspace adds on top.

<figure><img src="https://562749618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVUeHZHlFlZrZt02syRC%2Fuploads%2Fgit-blob-92abccde7e0857a13018dfea6ec9c7a6562aa96a%2FCoding%20with%20Nimbalyst%20(1).gif?alt=media" alt="A coding agent session in Nimbalyst, with the session list on the left, red/green edit cards in the transcript, and the Files panel on the right"><figcaption><p>An agent session in Nimbalyst: your prompt, the agent's edits as red/green cards, and the files it touched, all in one view.</p></figcaption></figure>

### Nimbalyst's Two Modes

**Chat Mode** is an AI sidebar for quick questions and targeted edits. Good for:

* Explaining code
* Small edits to the current document
* Quick lookups

**Agent Mode** is full-screen autonomous coding. Good for:

* Multi-file refactors
* Implementing features from a plan
* Running tests and fixing failures iteratively
* Running multiple sessions in parallel

### Code Editor with Diff Visualization

<figure><img src="https://562749618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVUeHZHlFlZrZt02syRC%2Fuploads%2FTvuT4y8nCeeYNe4wikgB%2Fimage.png?alt=media&amp;token=61c3eaa7-2c26-47c3-bafa-3d66bef8bdd0" alt="A Python file open in the Nimbalyst code editor with syntax highlighting, file tabs, and a minimap"><figcaption><p>The code editor with syntax highlighting, file tabs, and a minimap for navigating longer files.</p></figcaption></figure>

When the AI edits code or a document, changes appear inline:

* **Green background**: added content
* **Red background**: removed content, shown with strikethrough

Changes remain visible until you accept or reject them:

* **Accept All** keeps all changes
* **Reject All** reverts to the original content

### Inline Edit Cards in the Transcript

Both Claude Code's `Edit` tool and Codex's `file_change` tool render as red/green edit cards directly in the session transcript, so you can see exactly what the agent did to each file as the turn unfolds.

Edit cards work for:

* New files, rendered as a single-color "added" card
* Existing files, with red lines for removals and green for additions
* Gitignored or never-snapshotted files
* Renamed and deleted files


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbalyst.com/developer-features/coding-with-claude-code-and-nimbalyst.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.