> Source: Onevium official documentation
> Article: Organize projects and sessions
> Original URL: https://onevium.com/docs/projects-and-sessions
> Language: English
> Updated: 2026-09-09
> Applies to: 1.1.22
> Feature status: Released

---

# Organize projects and sessions

Choose the right working directory, keep related work in one conversation, and resume with a verifiable handoff.

## What projects and conversations contain

A **project** identifies a local working directory. A **conversation** stores a task's messages and tool activity. A project can contain several conversations, but creating one does not copy the directory, create a Git branch, or establish a worktree.

## Create a project or open an existing directory

Beside **Projects** in the sidebar, click the folder-plus button (**Add Project**) to open the New project dialog.

| What you need       | Action                                                                                                                     |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| An empty project    | Enter a name such as `onevium-tutorial` under Create a new project, check the full path below it, and click Create project |
| An existing project | Click Open an existing folder, select the project root in the folder picker, and confirm                                   |

New directories default to the `Onevium` folder in your user home directory. The dialog shows the actual path. Creating a folder does not download code, install dependencies, or initialize Git. For existing code, choose the root containing its README and package or build configuration, not its parent directory.

## Create a conversation in the right project

1. Click the project name to expand its conversations.
2. Hover over the project row and click its pencil button (**New Conversation**). You can also use New session at the top of the sidebar, but check the current directory first.
3. In the new conversation, confirm the project path, provider, model, and permissions before sending the task.

```text
Investigate how this project handles member invitations.
First report the working directory and Git branch, or say it is not a Git project.
Find the interface entry, server handling, and related tests. Cite file paths.
Do not edit files, install dependencies, or start services.
List anything you cannot find instead of guessing.
```

Clicking a project name mainly expands or collapses its list. Open one of its conversations or create a conversation from that project row to establish the working context. Keep follow-ups for the same goal together; create another conversation for an independent goal.

## View two conversations side by side

Drag another conversation from the sidebar into the chat area. Release it when the left or right split drop zone appears. In split view, click the column you intend to use before typing and check its title and project.

Drag the divider to resize columns. The close button in a column header closes that column only. Its `…` menu provides actions including rename, close, and close other columns. Conversations remain available from the sidebar.

Split view does not isolate files. Two columns using the same directory see the same files. Before parallel edits, use separate checkouts or assign non-overlapping files explicitly.

## Continue earlier work

Click a sidebar conversation to continue it. Use the search button beside Projects to find projects and conversations. The conversation's right-click menu includes **Copy Path** to verify its directory and **Open in Terminal**, which opens Onevium's built-in terminal.

Read the latest result before resuming, then recheck facts that may have changed:

```text
Continue this task. First list what is complete and what comes next.
Recheck the current branch, working-tree changes, and relevant services.
Do not treat the previous log as evidence that the same state still holds.
```

## Archive and restore conversations

Hover over an ordinary conversation row to reveal its trash button. Removed records can be found under **Settings → Archived sessions**, where **Restore** brings them back. For a pinned item, unpin it first to use the removal entry.

Restoring a conversation does not revert code or restart exited processes. Permanent deletion in the archive is a separate action. Use Restore for records you want to keep.

## Troubleshoot project context

| Symptom                                               | Check first                                                                                           |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| A new conversation reads another project              | Verify the project row and conversation path, not just its display name                               |
| A message goes to the wrong split column              | Click the target column and check its header and composer; each column has its own conversation state |
| Two tasks change the same file                        | Inspect the actual diff, preserve existing work, and revise task ownership                            |
| A conversation is missing from the sidebar            | Check search/filter settings, collapsed project groups, and Archived sessions                         |
| History says a service worked, but it no longer opens | Check the process and preview URL again. History is not a current health check                        |

## Next steps

Use [files, terminal, and Review](https://onevium.com/docs/files-terminal-review) to inspect work. See [memory and recap](https://onevium.com/docs/memory-and-recap) for handoffs and [Goal](https://onevium.com/docs/goal-mode) for continued work toward an outcome.