Bring your running agent
- The daemon is healthy and detached.
- Your agent has already replied in a conversation.
Read the agent roster
The roster joins the human name to the machine identifier and current model.
armaraos agent list
Choose one row. Confirm its state is Running and its model is the model you expect. Copy the long UUID from the first column.
Send one message and exit
message sends one prompt, prints one reply, and returns control to the shell.
armaraos message <UUID> "Reply with the single word: working"
Although help says name or ID, a friendly name fails on this 0.8.3 instance because the API path requires a UUID. Use the ID from the roster.
chat is a conversation you sit in. message is a request you fire and finish. That second shape is what unattended work will use.
Find the recorded session
Sessions gives you the record inventory, not the transcript text.
armaraos sessions
Match agent_id to the UUID from the roster. The message_count reflects activity in that session, while session_id identifies the conversation record.
This CLI command does not print the conversation itself. It confirms that a session record exists and shows its count.
Work around the ignored filter
The optional agent argument is documented, but it does not narrow the result in version 0.8.3.
armaraos sessions <AGENT>Both a friendly name and a UUID were accepted and then ignored on the live instance. Each returned all three sessions. Use the full list and match agent_id yourself.
Prove a prompt before scheduling it
Never schedule a prompt you have not first proven with armaraos message.
A one-shot run proves that the UUID, selected model, prompt, and reply work together while you are present. Course 3 will use that exact habit before any timer or external channel repeats work.
Check it / run this yourself
Make one recorded reply.
armaraos message <UUID> "Reply with the single word: working"Read working, then run armaraos sessions and find the same agent ID. Its session count should reflect the new exchange.
A one-shot message is still real agent work. Test a prompt while you are present before putting it into any schedule, trigger, webhook, or channel.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| The message says the agent ID is invalid | A friendly name was used. | Copy the UUID from armaraos agent list. |
| The reply is slow | The free provider is queued or throttled. | Wait once, then retry only if the command exits with an error. |
| The filter still shows every agent | The 0.8.3 filter is ignored. | Match the agent_id field manually. |
| No message text appears in sessions | The command exposes metadata only. | Use the session ID and message count as the available record. |