Question 1

Why does a resumed Codex session change from “Ask for approval” to “Approve for me” after restarting Atlas on Windows?

Accepted Answer

This is a bug in Atlas 0.3.4 on Windows: resuming an existing Codex ACP session can use the approval mode reported by the agent instead of your previously selected mode. A fresh session is not affected.

Fix: upgrade to Atlas 0.4.0 or later. The fix is in PR #345, commit 6764d951. A resumed session now restores the approval mode you selected. If that mode cannot be applied, the composer displays a warning and does not send anything until you choose a mode.

Workaround for Atlas 0.3.4: after reopening the project and resuming the Codex session, check the visible approval mode before sending a prompt. If it shows “Approve for me,” manually reselect “Ask for approval.”

Question 2

How to fix "cannot find `menu` in `crate`" and "field `0` of struct `tauri::State` is private" when building src-tauri on Windows?

Accepted Answer

This happens in versions up to 0.3.4 because `keybindings.rs` references the macOS-only `crate::menu` module unconditionally. Upgrade to release 0.4.0 or later, which includes commit `7cb5749a`, then rebuild:

```bash
git checkout 0.4.0
bun run dev:app
```

If you must stay on 0.3.4, cherry-pick the fix or gate the menu-dependent code in `src-tauri/src/commands/keybindings.rs` with:

```rust
#[cfg(target_os = "macos")]
{
    // crate::menu::CloseTabItem code
}
```

On Windows and Linux, the command should be a no-op. The fix was verified on Windows 11; Linux CI was also added to catch platform-specific build failures.

Question 3

Why does memory_forget return "forgotten": true but memory_search still finds the deleted text in document results?

Accepted Answer

In version `0.3.3` (`69c56bfd`), `memory_forget` deletes the structured entry immediately, but the separate on-device document index had no eviction API. Deleted text therefore remained searchable until the next debounced index rebuild, usually about 1–2 minutes.

Temporary workaround: after calling `memory_forget`, wait ~2 minutes, then run `memory_search` with a unique phrase from the entry and confirm that it no longer appears in the `documents` array. Treat the content as still retrievable until that check passes.

Permanent fix: upgrade to a build containing commit `ece6e811` (available on `main` around `5bff2ba` and the `0.3.4` branch around `a932ac5`). The fix adds an `IndexEvict` seam so `memory_forget` evicts the corresponding document, and `memory_search` filters document hits against the live entry table via `live_shared_docs()`. Forgotten content is therefore no longer returned immediately.

Question 4

How to fix Atlas Codex ACP on Windows when npm throws 'Maximum call stack size exceeded' and Node throws EISDIR lstat 'C:' with \?\ paths?

Accepted Answer

Root cause: on Windows, `std::fs::canonicalize` returns a verbatim extended-length path such as `\?\C:\Users\...`. Atlas 0.3.3 passes this path to npm's `--prefix` and to the Node entrypoint. npm 11.6.1's Arborist can recurse until `RangeError: Maximum call stack size exceeded`, while Node 24.11.0 can fail with `Error: EISDIR: illegal operation on a directory, lstat 'C:'`.

Permanent fix: upgrade to an Atlas release containing the agent-store path-normalization fixes from PR #281 and its follow-up. If patching the Rust code, normalize the path before spawning npm or Node:

```rust
let install_dir = dunce::simplified(&std::fs::canonicalize(&dir)?).to_path_buf();
```

Use `install_dir` for npm's `--prefix` and for the Node script path. You may keep the original canonicalized path for internal filesystem checks.

Workaround: install the adapter using a normal `C:\...` path, then start it with a normal-path launcher. In PowerShell:

```powershell
$dir = "$env:APPDATA\dev.atlas.ide\external-agentsegistry
px\codex-acp"
npm install --prefix $dir "@agentclientprotocol/codex-acp@1.12.0"
node "$dir
ode_modules\@agentclientprotocol\codex-acp\dist\index.js" --version
```

The last command should print `@agentclientprotocol/codex-acp 1.12.0`. Create a `.cmd` launcher that uses the same normal path:

```cmd
@echo off
node "C:\Users\<user>\AppData\Roaming\dev.atlas.ide\external-agentsegistry
px\codex-acp
ode_modules\@agentclientprotocol\codex-acp\dist\index.js" %*
```

Configure Atlas to use that launcher. Do not pass a path beginning with `\?\` to npm or Node.

Question 5

How do I make Codex read Claude Code rules from CLAUDE.md and .claude/rules/?

Accepted Answer

Enable the `instructionSync` setting in Atlas 0.4.0 or later. Atlas then mirrors `CLAUDE.md` and `.claude/rules/*.md` into a marked block at the end of the project's `AGENTS.md`, which Codex reads. The block uses the markers `` and ``; text outside it is not modified. Enabling the setting syncs the active project in each window, while disabling it removes the mirrored block from all projects where Atlas wrote it. Rules already projected by a pack are skipped, and the memory corpus excludes the mirrored block to prevent duplicate indexing. Note that hooks and permissions in `.claude/settings.json` are not mirrored because they only apply to Claude Code.

atlas

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects