Skip to content
Back to search

nac

Give AI agents ambitious work without losing the plot. nac is an open-source harness for long-running tasks, using a central orchestrator, threads, and structured episodes to stay aligned with your intent.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/arcee-ai/nac with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/arcee-ai/nac'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/arcee-ai--nac/badge.svg)](/listings/arcee-ai--nac)

HTML

<a href="/listings/arcee-ai--nac"><img src="/api/listings/arcee-ai--nac/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

**By Hand.** Install the latest stable release:

curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/install.sh | sh

The installer puts `nac-web` in `$HOME/.local/bin`. Add that directory to your `PATH` if needed, then start the dashboard from your project,

nac-web

and navigate to the interface in your browser (default: [http://127.0.0.1:3210](http://127.0.0.1:3210/)).

**By Agent.** Nac provides a portable onboarding skill and MCP integration; paste this into your chosen agent harness to install nac, configure it, and connect the MCP:

> Install the nac onboarding skill with `curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/install-skill.sh | sh -s -- --target agents`, load `nac-onboarding`, and walk me through installing nac, selecting Arcee login, ChatGPT Codex login, or an OpenAI-compatible API key, adding MCP servers, and connecting your MCP client to nac.

**Upgrade.** Nac ships with a native upgrade function which can be used to install the latest stable release of nac.

nac-web upgrade

Model Provider Authentication

Pick one before you start a session, or configure it later from the dashboard.

# Recommended: Arcee device-code login → Latest Open & Arcee Trinity models
nac-web arcee-auth login

# ChatGPT account via OAuth → OpenAI models
nac-web codex-auth login

# Any catalog provider (DeepSeek, Fireworks, Together, OpenAI, Anthropic, arcee-api, …)
export OPENAI_API_KEY=...   # or ANTHROPIC_API_KEY, TOGETHER_API_KEY, ARCEE_API_KEY, …

More details can be found in [Providers and logins](docs/configuration/credentials.md) and [Model configuration](docs/configuration/model.md).

Uninstall

curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/uninstall.sh | sh

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 199 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="docs/images/header.jpg" alt="nac from Arcee" />
  3. </p>
  4. <p align="center">
  5. <a href="https://arcee.ai">Arcee</a> &bull;
  6. <a href="#documentation">Documentation</a> &bull;
  7. <a href="https://github.com/arcee-ai/nac/releases">Releases</a> &bull;
  8. <a href="https://platform.arcee.ai">Arcee Open Model API</a>
  9. </p>
  10. <p align="center">
  11. <a href="https://github.com/arcee-ai/nac/actions/workflows/stable-release.yml">
  12. <img src="https://img.shields.io/badge/CI-GitHub_Actions-2088FF?logo=githubactions&logoColor=white" alt="CI" />
  13. </a>
  14. <a href="LICENSE">
  15. <img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="License" />
  16. </a>
  17. </p>
  18. nac is an open-source coding-agent harness for longer tasks. A persistent direct
  19. agent works in your project, can use tools and delegate bounded work to child
  20. agents, and retains session history and goals. It takes inspiration from
  21. [nanocode](https://github.com/1rgs/nanocode) and [pi](https://github.com/badlogic/pi-mono).
  22. ## Quickstart
  23. **By Hand.** Install the latest stable release:
  24. ```sh
  25. curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/install.sh | sh
  26. ```
  27. The installer puts `nac-web` in `$HOME/.local/bin`. Add that directory to your `PATH` if needed, then start the dashboard from your project,
  28. ```sh
  29. nac-web
  30. ```
  31. and navigate to the interface in your browser (default: [http://127.0.0.1:3210](http://127.0.0.1:3210/)).
  32. **By Agent.** Nac provides a portable onboarding skill and MCP integration; paste this into your chosen agent harness to install nac, configure it, and connect the MCP:
  33. > Install the nac onboarding skill with `curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/install-skill.sh | sh -s -- --target agents`, load `nac-onboarding`, and walk me through installing nac, selecting Arcee login, ChatGPT Codex login, or an OpenAI-compatible API key, adding MCP servers, and connecting your MCP client to nac.
  34. **Upgrade.** Nac ships with a native upgrade function which can be used to install the latest stable release of nac.
  35. ```sh
  36. nac-web upgrade
  37. ```
  38. ### Model Provider Authentication
  39. Pick one before you start a session, or configure it later from the dashboard.
  40. ```sh
  41. # Recommended: Arcee device-code login → Latest Open & Arcee Trinity models
  42. nac-web arcee-auth login
  43. # ChatGPT account via OAuth → OpenAI models
  44. nac-web codex-auth login
  45. # Any catalog provider (DeepSeek, Fireworks, Together, OpenAI, Anthropic, arcee-api, …)
  46. export OPENAI_API_KEY=... # or ANTHROPIC_API_KEY, TOGETHER_API_KEY, ARCEE_API_KEY, …
  47. ```
  48. More details can be found in [Providers and logins](docs/configuration/credentials.md) and [Model configuration](docs/configuration/model.md).
  49. ### Uninstall
  50. ```sh
  51. curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/uninstall.sh | sh
  52. ```
  53. ## Documentation
  54. - [Usage](docs/usage/README.md)
  55. - [Release lifecycle](docs/usage/releases.md)
  56. - [AGENTS.md Files](docs/usage/agents-md.md)
  57. - [Skills](docs/usage/skills.md)
  58. - [Sandbox](docs/usage/sandbox.md)
  59. - [Configuration](docs/configuration/README.md)
  60. - [Data stores](docs/configuration/data-stores.md)
  61. - [Example config](docs/configuration/example.md)
  62. - [Model configuration](docs/configuration/model.md)
  63. - [Catalog and cost](docs/configuration/catalog.md)
  64. - [Providers and logins](docs/configuration/credentials.md)
  65. - [HTTP API](docs/api/http.md)
  66. - [Model request security](docs/security/model-requests.md)
  67. ## Contributing
  68. Pull requests are welcome; see [pull request guidance](docs/contributing/pull-requests.md) for scope and before/after evidence. A CLA-signing bot checks every PR against arcee-ai's [CLA](https://github.com/arcee-ai/mergekit/blob/main/CLA.md); comment `I have read the CLA Document and I hereby sign the CLA` on your PR to sign it (or `recheck` to re-run the check).
  69. Development happens on the remote's default branch, currently `dev`; `main`
  70. is not the integration branch. Ask the remote rather than trusting a local
  71. cache, because an older clone's `origin/HEAD` can still point at `main`:
  72. ```sh
  73. git fetch origin
  74. git remote show origin | sed -n 's/.*HEAD branch: //p' # prints: dev
  75. git switch dev # or: git switch -c dev --track origin/dev
  76. ```
  77. `git remote set-head origin --auto` refreshes the cached `origin/HEAD` if you
  78. want it to agree; it does not change any branch.
  79. The supported source workflow starts with one dependency setup per fresh
  80. worktree:
  81. ```sh
  82. make setup
  83. make dev
  84. ```
  85. `make dev` runs the Rust API at `http://127.0.0.1:3210` and the React app at
  86. `http://127.0.0.1:5173`, with Vite HMR and API proxying. Both process trees are
  87. supervised together; Ctrl-C or either process failing stops the other.
  88. If either port is taken, `make dev` stops before starting anything and names
  89. the address and the variable to change. It never stops or reuses the other
  90. process. Pick free ports instead; the Vite proxy follows `DEV_BIND`
  91. automatically, so open the app port:
  92. ```sh
  93. DEV_BIND=127.0.0.1:4321 make dev # API moves; app stays on 5173
  94. DEV_BIND=127.0.0.1:4321 VITE_PORT=5174 make dev # both move; open http://127.0.0.1:5174
  95. ```
  96. Use `make build` to rebuild the committed frontend bundle and compile the
  97. complete production-embedded debug application, then `make run` to build and
  98. run that production-equivalent application from the current checkout. `make
  99. run` serves one port and uses `RUN_BIND`, not `DEV_BIND`: set
  100. `RUN_BIND=127.0.0.1:4321 make run` when the default port is already in use.
  101. For day-to-day use without replacing a stable installation, install the source
  102. build under its development name:
  103. ```sh
  104. make install-dev
  105. # defaults to $HOME/.local/bin/nac-web-dev
  106. make install-dev DEV_INSTALL_DIR="$HOME/bin" DEV_BIN_NAME="nac-my-branch"
  107. ```
  108. Source builds have the `dev` build track and report the exact source revision.
  109. Without an override they use `dev.db` under `NAC_HOME` (or the normal NAC
  110. configuration directory), isolated from `beta.db` and `stable.db`. Set
  111. `NAC_HOME=/path/to/branch-state` for a fully separate development home, or pass
  112. `DEV_STORE_PATH=/path/to/branch.db` to `make dev` and `--store-path` to the
  113. installed executable. Configuration-level storage overrides remain
  114. authoritative too. Database migrations are forward-only: when testing revisions
  115. that may move backward across an incompatible schema, use a disposable
  116. per-worktree or per-branch store rather than a shared development database.
  117. The local verification lanes are `make test-web` for frontend unit/component
  118. tests, `make test-e2e` for isolated real-browser tests against the embedded
  119. server and a credential-free scripted model, and `make test-durability` for the
  120. focused lifecycle/crash-window regressions. `make test-managed-load` runs the
  121. bounded deterministic legacy managed and 1/2/4 direct-session load and fault
  122. scenarios described in
  123. [the managed-load guide](docs/managed/deterministic-load.md). Install the E2E
  124. browser once with `npm --prefix crates/nac-server/web exec -- playwright install chromium`.
  125. `make ci` is the portable unit, lint, formatting, and committed-asset lane.
  126. Run `make test-e2e` as the matching production-browser release gate and
  127. `make test-durability` as a faster focused rerun of crash-window contracts that
  128. are also covered by the broader Rust suites. Release packaging and installer
  129. checks remain workflow-only.
  130. For an explicitly provisioned remote Managed NAC using the legacy BasicAuth
  131. gateway, set
  132. ```text
  133. NAC_E2E_REMOTE_URL
  134. NAC_E2E_REMOTE_USERNAME
  135. NAC_E2E_REMOTE_PASSWORD
  136. ```
  137. through a private runtime secret source and run `make test-e2e-remote`. This
  138. lane verifies gateway denial, authenticated health/readiness, release identity,
  139. and production-client loading without modifying remote state. Optionally set
  140. `NAC_E2E_REMOTE_EXPECTED_VERSION` to pin the expected release.
  141. For a portal-owned host, set `NAC_E2E_REMOTE_AUTH_MODE=portal-launch`, keep
  142. `NAC_E2E_REMOTE_URL` at the HTTPS host root, and inject the single-use URL as
  143. `NAC_E2E_REMOTE_LAUNCH_URL`; do not set the BasicAuth variables. The launch URL
  144. must use the exact target origin and managed launch route. Portal mode redeems
  145. it once into an isolated browser context, disables trace, screenshot, and video
  146. artifacts before redemption, and refuses `DEBUG` or `PWDEBUG`. An optional
  147. `NAC_E2E_REMOTE_ENVIRONMENT` non-secret label is included with the recorded
  148. build and schema identity.
  149. Never put remote credentials, launch URLs, or cookie values in Git, command
  150. arguments, shell history, test artifacts, or CI logs. The remote smoke lane
  151. complements rather than replaces the isolated local `make test-e2e` suite, and
  152. it remains non-mutating in both authentication modes.
  153. nac is licensed under [Apache 2.0](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.