Chat
Use conversations to work with an enabled agent in the web app. Each conversation keeps its own messages and resumable runtime session while sharing the agent's durable memory.
Start a conversation
Open an agent, select Conversations, and create a conversation. Send a clear outcome and attach files when they are relevant.
Aleph streams the response and shows transient phases while the sandbox is prepared, the agent works, the response is finalized, and the sandbox shuts down. “Finalizing response…” means generation has ended and Aleph is recording the completed turn. If the connection drops, the UI resumes active work when possible and otherwise reloads the latest stored history.
Reasoning and tool activity appear as compact expandable steps. Active work opens automatically; completed work collapses so the answer remains easy to scan. Expand any step to inspect its details. Markdown answers support lists, tables, links, and code blocks, and code blocks include a copy action.
Visible progress is part of conversation history while the turn is still running. Navigating away and returning keeps partial text, reasoning, tool calls, command output, and visible sandbox hooks even if the live stream cannot reconnect. Hook rows update from running to completed or failed without creating duplicates.
The message box grows with longer prompts. Press Enter to send or Shift+Enter for a new line. You can attach files with the attachment button, drag and drop, or paste.
Stop records the latest partial response before cancelling the matching turn. It does not cancel a newer turn that may have started elsewhere.
Continue with context
Messages and the Pi runtime journal are conversation-local. Starting a new conversation gives you a clean chat history, but relevant agent memory may still be retrieved.
The first web turn may generate a short conversation title. Channel conversations keep their transport title instead.
If chat is unavailable
Confirm the agent is enabled and has a pinned version. Then check that required secrets and variables exist in the agent's exact scope. A disabled agent cannot start a turn.
Turns have a four-minute application deadline. If work times out, Aleph persists an explicit timeout message rather than presenting partial narration as a completed result.