Your first session
Connect a repository, send a bounded task, and review the change.
Start with one small change whose result you can verify. You need a Uno account, a workspace you can run work in, repository access, and an available model.
1. Select the workspace
Sign in at app.uno.engineering. Choose the workspace that owns the code. If you are joining a team, ask an admin to add your existing account as described in Create an account.
2. Connect and attach your repository
Open Settings → Integrations → GitHub and complete the connection. Select the repositories in the GitHub installation, then attach the ones this workspace should use. Check the workspace repository list before continuing.
If the repository is missing, confirm the installation owner and selected repositories. See GitHub and source access.
3. Choose Engineering and start a session
Open a new Engineering session. Select the repository and the branch or commit you want to work from. Choose an available model in the composer. Connection or model access errors must be resolved before the turn can run.
Use an objective like this:
Fix the search box so clearing the query shows all results again.
Keep the current layout and keyboard behavior.
Add a regression test and run the relevant checks.
Create a pull request with the change and test results.Send the message once. Keep the session open while Uno prepares the environment and starts the turn. A slow startup is not a reason to submit the same task again.
4. Follow and steer
Read the messages and open Progress to inspect steps and the turn summary. If Uno asks a question, answer it in the session. You can add a constraint during work, for example, “Preserve the existing public API.”
An accepted follow-up still needs to be applied by the agent. Check the subsequent response and diff. See steering and questions.
5. Review the result
Open the changes panel and inspect the relevant files. Compare the result to your request and read the reported checks, including failures and checks that could not run. Open the pull request if one was created. Merge through your team's normal process.
For a UI change, ask the agent to run the app and register a preview. For a document or image, look in outputs.
Next time
Add repository rules and skills to preserve team context. Use a task for work that needs tracking or a specification when the outcome needs agreement first.