Skip to content

feat: support the Daybreak slash command - #737

Open
daandemeyer wants to merge 1 commit into
agentclientprotocol:mainfrom
daandemeyer:daybreak-command
Open

daandemeyer wants to merge 1 commit into
agentclientprotocol:mainfrom
daandemeyer:daybreak-command

Conversation

@daandemeyer

Copy link
Copy Markdown

The adapter sends /daybreak as an ordinary prompt. Let's handle it locally,
retain the choice in native thread metadata and select an advertised cyber
access program for subsequent turns. The command refuses enabling Daybreak
when the provider or model doesn't support it.

The adapter sends /daybreak as an ordinary prompt. Let's handle it locally,
retain the choice in native thread metadata and select an advertised cyber
access program for subsequent turns. The command refuses enabling Daybreak
when the provider or model doesn't support it.

Signed-off-by: Daan De Meyer <daan@amutable.com>
@kylesnowschwartz

kylesnowschwartz commented Nov 13, 2026 •

Copy link
Copy Markdown

Thanks for this - it would unblock my setup. I run Codex as a subagent of another harness through codex-acp, and I'd like some of those agents to do defensive security work with Daybreak, which my account is approved for.

With codex-acp 2.6.0 I couldn't find a way to turn it on: passing daybreak=true through CODEX_CONFIG leaves the thread's daybreak_enabled unset, while codex exec -c daybreak=true sets it. So today those agents have to run through codex exec outside ACP.

A /daybreak command that the adapter handles and keeps on the thread would cover it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants