AI agents
Threads
A thread is one agent conversation tied to one project folder: you give a coding task to Claude Code, Codex, OpenCode, an ACP agent or OmniGet’s own agent, and follow the work, the file changes and the approvals in one place. Keep one thread per task, so each change has its own history and can be reviewed or undone on its own.
Where it is
LLM › Threads. The first time, the page asks What should we build? and offers Add project.
Before you start
- A project: any folder. Worktrees and diffs need a git repository.
- A driver: OmniGet’s own agent is always listed. Claude Code, Codex, OpenCode and the ACP agents appear once the tool is installed and signed in (Coding tools). Claude Code and Codex get one entry per account you added in Connections.
Each tool runs with your own account and under its provider’s terms and limits.
How to use it
- Click Add project and pick the folder.
- Click New thread.
- Choose the Project and the Driver. Drivers that cannot run right now are marked unavailable.
- Optionally set the Model (empty means Default of the driver) and a Title (empty means From the first message).
- Choose the Access mode (see the table below).
- Turn on Work in a separate worktree if you want the agent on its own branch.
- Type the First message (optional) and click Create thread (⌘↩Ctrl+Enter).
OmniGet remembers the last project, driver, model, access mode and worktree choice for the next thread.
Plan first
Click Plan in the composer to make the agent propose a plan before it touches files. When the plan is done, the thread shows Plan ready with Implement and Implement in a new thread.
Access modes
| Option | What it does |
|---|---|
| Ask first | Every edit and command waits for your approval. This is the default. |
| Accept edits | File edits run; commands still ask. |
| Auto | The agent decides what is safe; risky actions ask. |
| Full access | Nothing asks. Use it in a worktree. |
⇧⌘XCtrl+Shift+X cycles through the access modes from the composer.
Worktrees
Work in a separate worktree creates a new branch in its own folder, so your checkout stays untouched. It is off by default and only offered for git repositories.
- The worktree lives in OmniGet’s data folder, in
worktrees/, on a branch namedomniget/…. - Setup runs in stages: Fetch, Checkout, Submodules and Setup script. A setup script can be defined in the project’s
.omniget/project.json. - Cancel setup stops it before the thread starts.
The thread header shows the branch, and the thread list shows a Worktree pill with its path.
The side panel
The panel on the right has these tabs (⌘JCtrl+J shows or hides it):
| Tab | Keys | What it shows |
|---|---|---|
| Diff | ⌥DAlt+D or ⌘DCtrl+D | The changes of a turn or of the whole thread. |
| Terminal | ⌥TAlt+T | A terminal in the thread’s folder. |
| Files | ⌥FAlt+F | The project files. |
| Plan | ⌥PAlt+P | The current plan. |
| Tasks | ⌥AAlt+A | The agent’s task list. |
| PR | ⌥RAlt+R | The pull request for the branch. |
| Browser | A browser preview. |
Diff, Terminal and PR need a folder; otherwise they say This thread has no folder.
Diffs and going back
- Switch between Turn and Whole thread, and use Pick a turn to see an earlier one. Ignore whitespace hides space-only changes.
- The diff opens by itself after a turn that changed many files or lines.
- Revert to here asks Edit from here? and offers Revert chat only or Revert files and chat. OmniGet keeps a checkpoint of each turn in the repository, under
refs/omniget/checkpoints.
Approvals
When the agent needs permission, the Approval needed drawer opens. It says what kind of request it is (a command, a file read, a file change, app access, a permission or a tool) and offers:
| Button | Key |
|---|---|
| Approve | Y |
| Approve for this session | S |
| Always | A |
| Decline | N |
| Cancel turn |
With several requests waiting, [ and ] move between them. Some drivers send their own choices (for example Allow once or Deny); the same keys still work.
When the agent asks you something instead, the drawer shows Question from the agent.
Shortcuts
| Action | Keys |
|---|---|
| New thread | ⌘NCtrl+N |
| Add project | ⌥⌘NCtrl+Alt+N |
| Rename thread | F2 |
| Fork thread | ⇧⌘KCtrl+Shift+K |
| Archive thread | ⌘⌫Ctrl+Backspace |
| Toggle right panel | ⌘JCtrl+J |
| Toggle plan/default mode | ⇧⌘ACtrl+Shift+A |
| Cycle access mode | ⇧⌘XCtrl+Shift+X |
| Send | ↩Enter |
| New line | ⇧↩Shift+Enter |
| Send now (interrupt) | ⌘↩Ctrl+Enter |
| Interrupt the running turn | escEsc |
| Keyboard shortcuts | ? |
Common problems
“No drivers available. Install or log in to a CLI in Tools.”
No coding tool is installed and signed in. Open Coding tools, install one and click Sign in.
Work in a separate worktree is greyed out
The project is not a git repository (Only for git repositories.). Run git init in the folder, or work without a worktree.
Plan does nothing useful with some drivers
Plan mode depends on the driver. Claude Code supports it; OmniGet’s own agent and Codex do not, and the button is shown anyway.
Fork or Compact is missing
They only appear for drivers that support them.