Codex CLI’s Memory and Reach: #Mentions for Cross-Session Context and Waypoints for Multi-Host Execution

Two draft PRs opened on April 11, 2026 reveal where Codex CLI is heading: deeper memory and wider reach.

Prior-Conversation #Mentions (PR #17358)

Codex CLI is adding a # mention system that lets users reference prior conversations within the current session. Type # in the composer, autocomplete selects a previous thread, and the system injects that conversation’s context as a hidden remembered-context packet.

How it works

Trigger: Type # → autocomplete popup shows prior conversations
Selection: Enter/Tab accepts; multiple threads can be referenced
Injection: A hidden ResponseItem::Message is prepended: “The user explicitly selected the following previous Codex conversation(s)…to bring them into this conversation as remembered context.”
Extraction: Visible user/assistant messages are included; system prompts, tool calls, and reasoning items are excluded
Validation: Backend thread/remember RPC prevents self-referencing and fails atomically if any source is inaccessible

Why this matters for agentic workflows

Context fragmentation is the #1 productivity killer in long-running agentic sessions. Today, if you solved a tricky configuration issue three sessions ago, you either remember it yourself or re-discover it. #Mentions turn Codex’s conversation history into a queryable knowledge base — the agent can draw on prior solutions, decisions, and context without the user manually providing it.

For agentic pods, this enables a pattern where:

A planning session defines architecture decisions
Implementation sessions reference the planning session via #
Review sessions reference both planning and implementation for full context

This is conversation-level RAG without external infrastructure.

Waypoints: Multi-Host Remote Execution (PR #17362)

Waypoints adds a shared multi-host execution registry above individual sessions. Commands can target specific hosts via SSH-backed remote execution — no TCP port forwarding required; WebSocket traffic tunnels through the SSH stream.

CODEX_EXEC_SERVER_SSH_HOSTS="staging,production,gpu-box"
CODEX_EXEC_SERVER_DEFAULT_HOST="staging"

The exec_command tool gains an optional host_id parameter, so the model can route commands to the right host.

Enterprise implications

Multi-environment orchestration from a single session: develop locally, test on staging, deploy to production
Fleet management: run diagnostic commands across distributed infrastructure
Resource routing: GPU-intensive subagent tasks dispatched to appropriate hosts

Combined with the agent identity stack (PRs #17385-17388), waypoints could enable authenticated cross-host agent delegation — a subagent on your local machine delegates a build task to a remote CI server with cryptographic identity verification.

Also in the April 11 PR pipeline

PR	Feature	Significance
#17477	`request_permissions` hooks	Programmatic approval gates for model-level permission requests — foundation for CI/CD auto-approval
#17472	GitHub PR in TUI status	Current branch’s PR number displayed in status line with OSC 8 hyperlinks
#17486	Guardian timeout semantics	Changed decision handling after guardian review timeouts
#17245	Configurable keymaps + Vim mode	Custom TUI keybindings including Vim mode
#17151	Federated auth routing	Enterprise SSO through federated edge

The bigger picture

These features collectively paint a picture of Codex evolving from a single-machine coding agent into a distributed, memory-rich development platform:

#Mentions solve the “context amnesia” problem across sessions
Waypoints solve the “single-host constraint” problem
Permission hooks solve the “approval bottleneck” problem for automation
Federated auth solves the “enterprise identity” problem

For anyone building agentic pods or enterprise Codex deployments, April 11’s draft PRs are the most architecturally significant batch since the multi-agent v2 launch in v0.117.0.

*Published 2026-04-11

Sources: PRs #17358, #17362, #17477, #17472*