Nori CLI ACP Roadmap

May 13, 2026 ยท View on GitHub

This roadmap is about Nori's ACP client work, not ACP in the abstract. The goal is to keep the client simple, fast, and predictable while we fill in the highest-value protocol features.

Note

Read this document in two passes: start with the product roadmap for what Nori users and maintainers should expect, then use the ACP feature appendix for protocol status and coverage detail.

Product Roadmap

Status key: โœ… done working well, ๐Ÿ”ต now current focus, ๐ŸŸก next near-term, โšช later planned but not near-term.

At a high level:

done                          now                          next                         later
 โ—โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ—โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ—โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ—โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ†’
core loop                     session forking              session config               agent auth
local agent registry          images/resources             official agent registry      multi-session
session lifecycle             message queue                                             unstable ACP
Product areaStatusUser valueNext workMaintainer note
File attachmentsโœ… doneusers can reference code and docskeep @ path reference behavior stableagents read referenced paths through ACP filesystem requests
Local agent registryโœ… donecustom agents can be registeredkeep local config registration simpleACP Registry should complement this, not replace it yet
Session lifecycleโœ… donenavigate previous sessionskeep behavior stable while forking work continuesload, list, resume, lazy indexing, and undo are already working
Session continuityโœ… doneusers can continue prior workkeep resume listing, speed, and metadata stablecontext/usage metadata and session_info_update are finished
Session forking๐Ÿ”ต nowsessions can branch and form treesfinish fork and tree-oriented flowskeep native ACP behavior ahead of local stand-ins
Image attachments๐Ÿ”ต nowusers can send visual contextcapability-aware image routing and transcript fidelityimages reach ACP, but the path needs polish
Queued messages๐Ÿ”ต nowusers can keep typing during workfinish backend handling for queued turnsTUI support exists, but ACP backend behavior needs tightening
Session configurationโœ… doneagents can expose useful controlscustom options like thinking/effort level and plan/build modeskeep this driven by agent-provided config, not hardcoding
Agent discovery๐ŸŸก nextcustom agents are easier to findsupport the official ACP Registrylocal config registration already works
Agent-driven authโšช lateragents can own login/logout flowsauth methods and logoutwait until lifecycle, config, and registry are settled
Multi-session UXโšช laterusers can move across active workmulti-session support and navigationkeep this separate from single-session lifecycle cleanup
Steering messagesโšช laterusers can redirect an active turnwait for ACP support, then design Nori behaviorunsupported by ACP today
Subagent UXโšช latergroup subagent updateswait for ACP support, then design Nori behaviorunsupported by ACP today
Experimental ACPโšช lateradopt new protocol ideas carefullyelicitation, NES, session/delete, provider endpoint workdo not let draft features complicate the core client

ACP Feature Appendix

This table keeps the roadmap grounded in the current ACP spec and draft surface. It is dependency-facing detail, not the main structure of the project roadmap.

Product areaACP featureACP statusNori status
Session lifecyclesession/loadstable baselinedone
Session lifecyclesession/liststabledone
Session lifecyclesession/resumeunstable landeddone
Session lifecyclesession/forkunstable landedtodo
Session lifecyclesession/closeunstable landedhandled
Session lifecyclesession/deletedraft onlynot planned near term
Session lifecycleundo, rewind, checkpointsnot first-class ACP todaylocal only
Session metadatasession_info_update, context/usage metadatastable + unstable landeddone
Session metadatamessageId and userMessageIdunstable landedpartial
Turn controlqueued messagesclient behaviorin progress
Turn controlsteering messagesACP draftlater
WorkspaceadditionalDirectoriesunstable landedpartial
File attachments@ path references + readTextFileACP filesystem capabilitydone
File attachmentsResourceLink / embedded Resource contextbaseline + embeddedContexttodo
Image attachmentsimage content blocksprompt capabilitypartial
Configurationsession config optionsstabledone
Configurationboolean config optionsunstable landednear term
DiscoveryACP Registrystablenear term
Authauth methodsunstable landedplanned
Authlogoutunstable landedplanned
Experimental protocolelicitationunstable landedlater
Experimental protocolNESunstable landedlater
Experimental protocolcustom provider endpointsdraft onlynot planned near term
Experimental protocoldiff-delete metadatadraft onlynot planned near term
Experimental protocolproxy-chainsdraft onlynot planned near term
Experimental protocolsubagentsnot first-class ACP todaynot planned near term

Notes

  • This reflects our current understanding as of April 2026.
  • "Done" means done enough for initial usage within Nori, not necessarily that every implementation detail is perfect.
  • We will keep preferring fewer special cases and more native ACP behavior as we iterate.