wdx message

See the messages still waiting to reach a terminal or agent.

wdx agent send and wdx terminal send keep a message until its holder says it typed it. When a holder dies, its messages go on if the agent resumes the same conversation. If it starts anew, or a shell does, they are held for you to send or discard, as what they were meant for is gone.

Command	What it does
`wdx message discard`	Discard a message still waiting
`wdx message list`	List a project’s messages still waiting, oldest first
`wdx message resend`	Send a message still waiting to its terminal or agent, as it is now

wdx message discard

Discard a message still waiting.

wdx message discard --id <id> [flags]

A review’s comments go back to being drafts, to send again.

Flags

Flag	Default	Description
`--id <id>`		id of the message
`--node <name>`		run the command on the node of this name, another of your account, through a session

--id is required

Examples

# Discard a held message
wdx message discard --id msg-1a2b3c4d

Output

That it went. With --json: {“result”: “removed”}

With --json, result is one of: removed.

Errors

Code	Exit	When
`daemon_unavailable`	3	the daemon is not running or not answering
`not_found`	1	nothing has this name or id
`usage`	2	the request, command line or a setting is invalid
`internal`	3	an unexpected failure: database, filesystem or git

With --node, also: code_not_set_up, code_wrong, connection_lost, daemon_unavailable, hub_unreachable, hub_version_unsupported, node_key_mismatch, node_not_found, node_offline, node_version_unsupported, not_logged_in, remote_access_off, remote_not_for_agents, route_not_allowed, session_closed, session_required, too_many_streams.

wdx message list

List a project’s messages still waiting, oldest first.

wdx message list [--project-id <id> | --project-name <name>] [flags]

Without a project flag, the project the working directory is in.

Flags

Flag	Default	Description
`--project-id <id>`		id of the project (default: the one the working directory is in)
`--project-name <name>`		name of the project (default: the one the working directory is in)
`--node <name>`		run the command on the node of this name, another of your account, through a session

at most one of --project-id or --project-name

Examples

# The messages of the project you are in
wdx message list

# Another project's, as JSON
wdx message list --project-name app --json

Output

The messages, oldest first. With --json: {“messages”: […]}

Errors

Code	Exit	When
`daemon_unavailable`	3	the daemon is not running or not answering
`invalid_path`	1	the path cannot be used
`not_found`	1	nothing has this name or id
`usage`	2	the request, command line or a setting is invalid
`internal`	3	an unexpected failure: database, filesystem or git

wdx message resend

Send a message still waiting to its terminal or agent, as it is now.

wdx message resend --id <id> [flags]

It goes in whatever conversation the agent is in now.

Flags

Flag	Default	Description
`--id <id>`		id of the message
`--node <name>`		run the command on the node of this name, another of your account, through a session

--id is required

Examples

# Send a held message
wdx message resend --id msg-1a2b3c4d

Output

The message. With --json: {“result”: “queued”, “message”: {…}}

With --json, result is one of: queued.

Errors

Code	Exit	When
`agent_not_running`	1	the agent’s AI coding agent is not running
`daemon_unavailable`	3	the daemon is not running or not answering
`not_found`	1	nothing has this name or id
`send_failed`	3	the message did not reach the terminal’s holder
`terminal_not_running`	1	the terminal’s shell is not running
`usage`	2	the request, command line or a setting is invalid
`internal`	3	an unexpected failure: database, filesystem or git