Your first task in Onevium

Start with a small task#

Onevium brings AI conversations, project files, and tools into one workspace. Describe what you want to do, and the assistant can read material, edit files, run commands, or inspect a web page. Follow its work and results in the conversation.

Start with three steps: connect a model → open a project → send a task. This guide first asks the assistant to understand a folder. You can learn other tools as you need them.

Connect a model and open a project#

1. Follow the installation guide to install and open Onevium.
2. Follow provider setup to connect a model. You can sign in to Claude Code or use a provider's API key or supported Coding Plan. Signing in to Onevium does not include model credits.
3. Click the folder-plus button (Add Project) beside Projects in the sidebar, then choose Open an existing folder. Use a code repository or a folder of documents. If you have no material yet, you can create an empty project.
4. Click the pencil button on the project row to create a conversation. Select your connected provider and model in the composer.

Think of a project as the folder where you work, and a conversation as one task in that folder. Keep follow-ups in the same conversation; start another conversation for a separate task.

Send your first task#

Copy and send this request. It only reads files, so it is a simple way to learn the workflow:

Help me understand the current project.
First confirm the working directory, then read the README or other existing documentation.
Describe the project in three sentences. List up to three files worth reading first and explain why.
If the folder is empty, suggest what material I could prepare first.
Only read for this task. Do not edit files or run the project.

Inspect the tool activity below the reply to see which files the assistant read. Add instructions in the conversation when useful, such as “Only look in the docs folder.” If an action needs permission, read it before deciding.

You can also click the composer microphone to dictate your request. Check the resulting text before sending. First-time use requires a speech model and microphone setup.

Find the result and check it#

Click the folder icon Browse all files in the conversation toolbar. Open one file cited in the answer and check that it supports the explanation. For an empty folder, the correct result is to report that no material is available.

Then try a small follow-up, such as “Turn this explanation into a to-do list.” After a task changes files, use the green +N and red -N toolbar entry to inspect changes in a Git project. See files, terminal, and Review for the steps.

Choose a tool for your task#

Learn what each tool is for, then open its guide when needed. The composer's @ menu helps you discover capabilities. Files, the terminal, and the browser also have workspace controls.

Install or create a Skill before using it. Team sessions, schedules, and channels also have setup steps in their guides. Selecting a tag still requires adding your request and sending it. Files and the browser are enough for many first tasks; add other capabilities when they help.

Troubleshoot your first task#

What to do next#

Finish provider setup, then organize real tasks with projects and conversations. Choose a guide from the table when its capability becomes useful; you do not need to configure every tool at once.