Console commands 

ai-chat:process 

Process a single chat conversation. Used by the exec processing strategy -- the ChatApiController forks this command for each incoming message.

vendor/bin/typo3 ai-chat:process <conversationUid>

Arguments:

conversationUid (required)

UID of the conversation to process. The conversation must be in processing status.

Exit codes:

0

Success -- conversation processed and set to idle.

1

Failure -- conversation not found, wrong status, or processing error. The conversation is set to failed with an error message.

Behavior:

• Initializes the backend user context for the conversation owner.
• If the conversation has pending tool calls (crash recovery), executes them first via resumeConversation().
• Otherwise, runs the full agent loop via processConversation().

ai-chat:worker 

Long-running worker process that polls for conversations in processing status and processes them sequentially. Used by the worker processing strategy.

vendor/bin/typo3 ai-chat:worker [--poll-interval=200]

Options:

--poll-interval (optional, default: 200)

Poll interval in milliseconds. How often the worker checks for new conversations to process.

Behavior:

• Runs indefinitely (designed for systemd or supervisord).
• Uses dequeueForWorker() with atomic locking to prevent multiple workers from processing the same conversation.
• Each worker identifies itself with a unique ID (PID + random bytes).
• After processing, the backend user context is cleared to prevent leaking between conversations.

Production deployment:

See Worker mode production setup in the Configuration section for a systemd service example.

ai-chat:cleanup 

Maintenance command that handles stuck conversations, auto-archiving, and deletion of old data. Should be run periodically (e.g. daily via cron).

vendor/bin/typo3 ai-chat:cleanup \
    [--delete-after-days=90]

Options:

--delete-after-days (optional, default: 90)

Hard-delete archived conversations older than this many days.

Actions performed:

1. Timeout stuck conversations -- Conversations in processing, locked, or tool_loop status for more than 5 minutes are set to failed with a timeout error message.
2. Auto-archive inactive conversations -- Conversations in idle status that have been inactive longer than the configured autoArchiveDays are archived.
3. Delete old archived conversations -- Archived conversations older than --delete-after-days are hard-deleted from the database.

Output example:

Timed out 2 stuck conversation(s)
Auto-archived 5 inactive conversation(s)
Deleted 12 old archived conversation(s)

Cleanup summary:
  Timed out stuck conversations: 2
  Auto-archived inactive conversations: 5
  Deleted old archived conversations: 12