Valen, messages and work
Applies to: Public Core prototype
Updated
Valen is the AI within the product family. In Core, communication with Valen can refer to the work object currently in focus, allowing the conversation and the relevant material to remain together.
Prepare a contextual message#
- Navigate to the object you want to discuss.
- Open Valen Messages.
- Check the context label above the composer.
- Enter the message and review it before submitting.
Enter submits the message; Shift+Enter adds a new line. The composer accepts up to 8,000 characters. Do not submit credentials or confidential customer information to a public prototype.
Read connection and delivery state#
The connection indicator describes whether the communication capability is available. If Valen is disconnected, Core can retain a pending or failed message without receiving an answer. A queued message is not evidence that a model has processed it.
After submitting, read the displayed delivery state and any error. If delivery fails, preserve the message you need and inspect the connection before trying again. Repeated submission can create duplicate requests when a connection recovers.
The public product interface does not guarantee that every visitor has an attached model or the same connected tools. The active environment's status is the source for that determination.
Review updates#
Updates records messages about work and interface operations. Read the object, action and result together. An operation can be pending, successful or failed within its own scope. A successful local interface action does not by itself establish that an external application changed or that another person received a message.
For connected work, inspect the application's own result when the outcome matters. For a representative product preview, interpret the update as part of that preview.
Pause agent control#
The Pause agent control control changes the interface's agent-control state. Use it when you want to inspect or steer the surface yourself. It is not a general stop command for every remote service or previously submitted operation. Use the controls of the relevant connected application to stop work there.
Local conversation state#
The prototype retains conversation state in the current browser when storage is available. That history is not automatically a shared conversation across devices. Text that you explicitly submit can be sent through an attached communication capability; merely keeping a local draft is a different action.
If local state cannot be saved, the interface reports the limitation. Preserve any text you need before closing the page or clearing browser data. See Troubleshooting and browser data.