Rename codex-rs workspace and codex-acp package (#443)

## Summary
🤖 Generated with [Nori](https://www.npmjs.com/package/nori-ai)

- rename the Rust workspace directory from `codex-rs/` to `nori-rs/`
- rename the ACP crate/package from `codex-acp`/`codex_acp` to
`nori-acp`/`nori_acp`
- update repo docs, CI, release scripts, and package selectors to use
the new names

## Test Plan
- [x] `cargo test -p nori-acp`
- [x] `cargo test -p nori-tui`
- [x] `cargo test -p nori-cli`
- [x] `cargo test`
- [x] `cargo build --bin nori && cargo test -p tui-pty-e2e`
- [x] live tmux smoke test launching `./target/debug/nori --agent
elizacp --skip-trust-directory`
- [x] `just fmt`
- [x] `just fix`

Share Nori with your team: https://www.npmjs.com/package/nori-skillsets

---------

Co-authored-by: Nori <contact@tilework.tech>

Author: CSRessel

.github/codex/labels/codex-rust-review.md

@@ -15,8 +15,8 @@ Things to look out for when doing the review:
 
 ## Code Organization
 
-- Each create in the Cargo workspace in `codex-rs` has a specific purpose: make a note if you believe new code is not introduced in the correct crate.
-- When possible, try to keep the `core` crate as small as possible. Non-core but shared logic is often a good candidate for `codex-rs/common`.
+- Each create in the Cargo workspace in `nori-rs` has a specific purpose: make a note if you believe new code is not introduced in the correct crate.
+- When possible, try to keep the `core` crate as small as possible. Non-core but shared logic is often a good candidate for `nori-rs/common`.
 - Be wary of large files and offer suggestions for how to break things into more reasonably-sized files.
 - Rust files should generally be organized such that the public parts of the API appear near the top of the file and helper functions go below. This is analagous to the "inverted pyramid" structure that is favored in journalism.
 
@@ -131,7 +131,7 @@ fn test_get_latest_messages() {
 
 ## Pull Request Body
 
-- If the nature of the change seems to have a visual component (which is often the case for changes to `codex-rs/tui`), recommend including a screenshot or video to demonstrate the change, if appropriate.
+- If the nature of the change seems to have a visual component (which is often the case for changes to `nori-rs/tui`), recommend including a screenshot or video to demonstrate the change, if appropriate.
 - References to existing GitHub issues and PRs are encouraged, where appropriate, though you likely do not have network access, so may not be able to help here.
 
 # PR Information

.github/dependabot.yaml

@@ -8,8 +8,8 @@ updates:
       interval: weekly
   - package-ecosystem: cargo
     directories:
-      - codex-rs
-      - codex-rs/*
+      - nori-rs
+      - nori-rs/*
     schedule:
       interval: weekly
   - package-ecosystem: devcontainers
@@ -21,6 +21,6 @@ updates:
     schedule:
       interval: weekly
   - package-ecosystem: rust-toolchain
-    directory: codex-rs
+    directory: nori-rs
     schedule:
       interval: weekly

.github/workflows/cargo-deny.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: blacksmith-4vcpu-ubuntu-2404
     defaults:
       run:
-        working-directory: ./codex-rs
+        working-directory: ./nori-rs
     env:
       # Disable sccache wrapper from .cargo/config.toml since it's not available
       # in the cargo-deny Docker container.
@@ -26,7 +26,7 @@ jobs:
         uses: EmbarkStudios/cargo-deny-action@v2
         with:
           rust-version: nightly
-          manifest-path: ./codex-rs/Cargo.toml
+          manifest-path: ./nori-rs/Cargo.toml
           log-level: warn
           command: check
           arguments: --all-features

.github/workflows/docs.md

@@ -10,7 +10,7 @@ Path: @/.github/workflows
 
 ### How it fits into the larger codebase
 
-- The release workflow builds Rust binaries from `@/codex-rs/` and packages them via the Node.js launcher in `@/nori-cli/`
+- The release workflow builds Rust binaries from `@/nori-rs/` and packages them via the Node.js launcher in `@/nori-cli/`
 - Version detection delegates to `@/scripts/create_nori_release --get-next-version`, which queries git tags (via the GitHub API) as the single source of truth for version numbering
 - Stable releases use "synthetic commits" created by the `create_nori_release` script -- release tags point to commits that exist only for the release (not on any branch), with `Cargo.toml` updated to the release version, keeping the `main` branch's `Cargo.toml` at a placeholder `0.0.0`
 - The `nori-release.yml` workflow publishes to npm under the package name `nori-ai-cli`, with stable releases tagged `@latest` and snapshots tagged `@next`
@@ -25,7 +25,7 @@ Path: @/.github/workflows
 | Main branch push | Push to `main` (e.g., merged PR) with path filters | `publish_next=true` -- publishes a `@next` snapshot |
 | Manual dispatch | `workflow_dispatch` with inputs | Either `publish_next=true` or explicit version + optional `dry_run` |
 
-**Path filters for main branch pushes** restrict triggering to changes in `codex-rs/**`, `nori-cli/**`, `scripts/**`, and the workflow file itself, so docs-only changes do not trigger a release.
+**Path filters for main branch pushes** restrict triggering to changes in `nori-rs/**`, `nori-cli/**`, `scripts/**`, and the workflow file itself, so docs-only changes do not trigger a release.
 
 **Concurrency control** uses group `nori-release-${{ github.ref }}` with `cancel-in-progress` enabled only for main branch pushes. This means if two PRs merge in quick succession, the second run cancels the first since only the latest snapshot matters.
 

.github/workflows/nori-release.yml

@@ -38,7 +38,7 @@ on:
     branches:
       - main
     paths:
-      - "codex-rs/**"
+      - "nori-rs/**"
       - "nori-cli/**"
       - "scripts/**"
       - ".github/workflows/nori-release.yml"
@@ -225,24 +225,24 @@ jobs:
         uses: rui314/setup-mold@v1
 
       - name: cargo check
-        working-directory: codex-rs
+        working-directory: nori-rs
         run: cargo check --profile ci-test --target ${{ env.MUSL_TARGET }} --all-targets
 
       # - name: cargo clippy
-      #   working-directory: codex-rs
+      #   working-directory: nori-rs
       #   run: cargo clippy --target ${{ env.MUSL_TARGET }} --all-features -- -D warnings
 
       # - name: cargo build
-      #   working-directory: codex-rs
+      #   working-directory: nori-rs
       #   run: |
       #     cargo build --profile ci-test --target ${{ env.MUSL_TARGET }} -p nori-cli
       #     cargo build --profile ci-test --target ${{ env.MUSL_TARGET }} -p mock-acp-agent
 
       # - name: cargo test
-      #   working-directory: codex-rs
+      #   working-directory: nori-rs
       #   run: |
       #     cargo test --profile ci-test --target ${{ env.MUSL_TARGET }} --package tui-pty-e2e
-      #     cargo test --profile ci-test --target ${{ env.MUSL_TARGET }} --package codex-acp
+      #     cargo test --profile ci-test --target ${{ env.MUSL_TARGET }} --package nori-acp
       #     cargo test --profile ci-test --target ${{ env.MUSL_TARGET }} --package nori-tui
       #     cargo test --profile ci-test --target ${{ env.MUSL_TARGET }} --package nori-cli
       #     cargo test --profile ci-test --target ${{ env.MUSL_TARGET }} --package codex-protocol
@@ -352,15 +352,15 @@ jobs:
 
       - name: Set version in Cargo.toml
         if: ${{ needs.validate.outputs.publish_next == 'true' }}
-        working-directory: codex-rs
+        working-directory: nori-rs
         run: |
           VERSION="${{ needs.validate.outputs.version }}"
           echo "Injecting version $VERSION into Cargo.toml"
           perl -i -pe 's/^version = "[^"]*"/version = "'"$VERSION"'"/ && ($done=1) unless $done' Cargo.toml
           grep '^version' Cargo.toml | head -1
 
       - name: Build release binaries
-        working-directory: codex-rs
+        working-directory: nori-rs
         run: |
           cargo build --release --target ${{ matrix.target }} -p nori-cli
 
@@ -377,9 +377,9 @@ jobs:
 
           # Copy the main binary
           if [[ "$RUNNER_OS" == "Windows" ]]; then
-            cp codex-rs/target/$TARGET/release/nori.exe artifacts/vendor/$TARGET/nori/nori.exe
+            cp nori-rs/target/$TARGET/release/nori.exe artifacts/vendor/$TARGET/nori/nori.exe
           else
-            cp codex-rs/target/$TARGET/release/nori artifacts/vendor/$TARGET/nori/nori
+            cp nori-rs/target/$TARGET/release/nori artifacts/vendor/$TARGET/nori/nori
             chmod +x artifacts/vendor/$TARGET/nori/nori
           fi
 
@@ -527,7 +527,7 @@ jobs:
         run: |
           VERSION="${{ needs.validate.outputs.version }}"
           TAG_NAME="${{ needs.validate.outputs.tag_name }}"
-          CARGO_TOML_PATH="codex-rs/Cargo.toml"
+          CARGO_TOML_PATH="nori-rs/Cargo.toml"
 
           echo "Creating synthetic commit for version $VERSION"
 

.github/workflows/rust-ci.yml

@@ -11,7 +11,7 @@ jobs:
     timeout-minutes: 30
     defaults:
       run:
-        working-directory: codex-rs
+        working-directory: nori-rs
     env:
       CARGO_INCREMENTAL: "0"
       # Speed up repeated builds across CI runs by caching compiled objects.
@@ -60,8 +60,8 @@ jobs:
         shell: bash
         run: |
           set -euo pipefail
-          echo "hash=${{ hashFiles('codex-rs/Cargo.lock') }}" >> "$GITHUB_OUTPUT"
-          echo "toolchain_hash=${{ hashFiles('codex-rs/rust-toolchain.toml') }}" >> "$GITHUB_OUTPUT"
+          echo "hash=${{ hashFiles('nori-rs/Cargo.lock') }}" >> "$GITHUB_OUTPUT"
+          echo "toolchain_hash=${{ hashFiles('nori-rs/rust-toolchain.toml') }}" >> "$GITHUB_OUTPUT"
 
       # Cache cargo home directory (registry, git deps, etc.)
       - name: Restore cargo home cache
@@ -129,10 +129,10 @@ jobs:
           cargo build -p nori-cli --profile ci-test --target ${{ matrix.target }}
       - name: cargo test nori
         env:
-          MOCK_ACP_AGENT_BIN: ${{ github.workspace }}/codex-rs/target/mock-acp-out/mock_acp_agent
+          MOCK_ACP_AGENT_BIN: ${{ github.workspace }}/nori-rs/target/mock-acp-out/mock_acp_agent
         run: |
           cargo test --profile ci-test --target ${{ matrix.target }} --package tui-pty-e2e
-          cargo test --profile ci-test --target ${{ matrix.target }} --package codex-acp
+          cargo test --profile ci-test --target ${{ matrix.target }} --package nori-acp
           cargo test --profile ci-test --target ${{ matrix.target }} --package nori-tui
           cargo test --profile ci-test --target ${{ matrix.target }} --package nori-cli
           cargo test --profile ci-test --target ${{ matrix.target }} --package codex-protocol

.gitignore

@@ -97,7 +97,7 @@ CHANGELOG.ignore.md
 # git worktrees
 .worktree/
 .worktrees/
-/codex-rs/tui/target/
+/nori-rs/tui/target/
 /target
 
 # Local code/doc references for ACP work

AGENTS.md

@@ -2,9 +2,9 @@
 
 We only care about the ACP backend and the code that compiles into the nori bin. We do not care about the default codex backend or the code that compiles into the codex bin. Make sure all changes and responses are aligned to this critical fact. For example, if I ask 'add notifications to the cli', you should assume I mean 'add notification support to the ACP backend for the nori cli'.
 
-# Rust/codex-rs
+# Rust/nori-rs
 
-In the codex-rs folder where the rust code lives:
+In the nori-rs folder where the rust code lives:
 
 - Crate names are prefixed with `codex-`. For example, the `core` folder's crate is named `codex-core`
 - When using format! and you can inline variables into {}, always do that.
@@ -23,21 +23,21 @@ In the codex-rs folder where the rust code lives:
   - Prefer adding new modules instead of growing existing ones.
   - Target Rust modules under 500 LoC, excluding tests.
   - If a file exceeds roughly 800 LoC, add new functionality in a new module instead of extending the existing file unless there is a strong documented reason not to.
-  - This rule applies especially to high-touch files such as `codex-rs/tui/src/app.rs`, `codex-rs/tui/src/bottom_pane/chat_composer.rs`, `codex-rs/tui/src/bottom_pane/footer.rs`, `codex-rs/tui/src/chatwidget.rs`, `codex-rs/tui/src/bottom_pane/mod.rs`, and similarly central orchestration modules.
+  - This rule applies especially to high-touch files such as `nori-rs/tui/src/app.rs`, `nori-rs/tui/src/bottom_pane/chat_composer.rs`, `nori-rs/tui/src/bottom_pane/footer.rs`, `nori-rs/tui/src/chatwidget.rs`, `nori-rs/tui/src/bottom_pane/mod.rs`, and similarly central orchestration modules.
   - When extracting code from a large module, move the related tests and module/type docs toward the new implementation so the invariants stay close to the code that owns them.
 - When running Rust commands (e.g. `just fix` or `cargo test`) be patient and never try to kill them using the PID. Rust lock contention can make execution slow; this is expected.
 
-Run `just fmt` (in `codex-rs` directory) automatically after you have finished making Rust code changes; do not ask for approval to run it. Additionally, run the tests:
+Run `just fmt` (in `nori-rs` directory) automatically after you have finished making Rust code changes; do not ask for approval to run it. Additionally, run the tests:
 
-1. Run the test for the specific project that was changed. For example, if changes were made in `codex-rs/tui`, run `cargo test -p nori-tui`.
+1. Run the test for the specific project that was changed. For example, if changes were made in `nori-rs/tui`, run `cargo test -p nori-tui`.
 2. Once those pass, if any changes were made in common, core, or protocol, run the complete test suite with `cargo test`. Avoid `--all-features` for routine local runs because it expands the build matrix and can significantly increase `target/` disk usage; use it only when you specifically need full feature coverage.
 3. If any changes were made in tui, cli, or acp, run `cargo build --bin nori && cargo test -p tui-pty-e2e`. The E2E tests require the `nori` binary (from the `cli` crate), not `nori-tui`.
 
-Before finalizing a change to `codex-rs`, run `just fix -p <project>` (in `codex-rs` directory) to fix any linter issues in the code. Prefer scoping with `-p` to avoid slow workspace‑wide Clippy builds; only run `just fix` without `-p` if you changed shared crates. Do not re-run tests after running `fix` or `fmt`.
+Before finalizing a change to `nori-rs`, run `just fix -p <project>` (in `nori-rs` directory) to fix any linter issues in the code. Prefer scoping with `-p` to avoid slow workspace‑wide Clippy builds; only run `just fix` without `-p` if you changed shared crates. Do not re-run tests after running `fix` or `fmt`.
 
 ## TUI style conventions
 
-See `codex-rs/tui/styles.md`.
+See `nori-rs/tui/styles.md`.
 
 ## TUI code conventions
 
@@ -62,7 +62,7 @@ See `codex-rs/tui/styles.md`.
 
 ### Snapshot tests
 
-This repo uses snapshot tests (via `insta`), especially in `codex-rs/tui`, to validate rendered output.
+This repo uses snapshot tests (via `insta`), especially in `nori-rs/tui`, to validate rendered output.
 
 **Requirement:** Any change that affects user-visible UI (including adding new UI) must include corresponding `insta` snapshot coverage (add a new snapshot test if one doesn't exist yet, or update the existing snapshot). Review and accept snapshot updates as part of the PR so UI impact is easy to review and future diffs stay visual.
 
@@ -114,13 +114,13 @@ below. Choose the option that matches the area of the codebase you changed.
 
 ### Option 1: Build and Drive the TUI
 
-**When to use:** Any change to `codex-rs/tui/`, `codex-rs/cli/`, or `codex-rs/acp/` crates. Also consider running this for changes to shared crates (`core/`, `common/`, `protocol/`) that affect TUI behavior.
+**When to use:** Any change to `nori-rs/tui/`, `nori-rs/cli/`, or `nori-rs/acp/` crates. Also consider running this for changes to shared crates (`core/`, `common/`, `protocol/`) that affect TUI behavior.
 
 **Skill:** `tui-puppeteering-with-tmux`
 
 **Steps:**
 
-Run all steps from the `codex-rs/` directory.
+Run all steps from the `nori-rs/` directory.
 
 1. Build the `nori` binary: `cargo build --bin nori`
 2. Ensure `elizacp` is installed: `which elizacp || cargo install --locked elizacp`