Ask in plain English.
Keep the project in view.

A question and an instruction are different.

Ask a thread about its work when you want a conversation with that agent. Order work when you want a project change routed through the responsible leader. Use the Vraido assistant when you want help with the workspace itself.

This distinction is especially valuable when you are looking at a coder or a specialist. A casual question should not unexpectedly start a new delivery or change a requirement that the leader still believes is settled.

Useful things to ask.

• “Help me set up a project for a customer booking website.”
• “Explain why this task is waiting.”
• “Where do I change the model for a reviewer?”
• “Show me the project settings and the AI connections I can use.”

The assistant uses a defined tool catalog for navigation, project setup and supported settings. Project work goes through the normal work-request path. A chat instruction is not unrestricted permission to run arbitrary commands or alter a database.

Choose the AI that answers.

The assistant has its own AI, model and reasoning-effort selection. A conversation-specific choice takes priority; otherwise it can use your configured assistant profile or follow the relevant leader’s profile.

Only capabilities supported by the selected model are valid. An unavailable explicit choice should be visible rather than silently replaced with a potentially different billing route.

Relevant knowledge, not the whole manual.

The workspace prepares a compact base instruction, searches its help locally and includes relevant project context. Selected chapters and approved skills provide more focused support than copying every document into every turn.

Conversation history and versioned knowledge can be reused when appropriate. The assistant is still an AI: its requests consume the chosen provider’s usage, and its explanations should be grounded in the current workspace.

Start with one clear outcome.

The value of the assistant is making that first decision easier while keeping responsibility in the project. It does not replace the leader, coder and reviewer roles with a second hidden project.