Your workspace

Repositories and Git workflows

Attach code, work in isolation and integrate completed changes through a clear delivery process.

App version 0.7.934 · Updated

Get started

  1. Select Attach repository when creating a session, or open the repository picker in Dev Cockpit.
  2. Find the project in the active GitHub account or select an existing repository.
  3. Check the displayed working copy and branch before sending your coding task.
  4. Open Dev > Setup and choose how completed work should be integrated and delivered.
  5. Review changes and test results, then follow your project’s delivery process.

Choose the right project

The GitHub picker searches repositories accessible to the active account by default. This can include private and public projects, organization repositories and repositories shared with you. Favorites make recurring access easier.

Public GitHub search is a separate option that starts off. Enable it deliberately to add global public-project results. Those results remain separate from the list of repositories your account can access.

A branch for the session

When you attach a repository, IXIOM prepares a separate working copy and branch for the session. The agent receives that assignment and works there until delivery. Ordinary sessions can use this workflow without starting a team.

An environment can carry a repository as its default. Shared Claude/Codex work and teams also give each coding participant a separate workspace. Their committed changes are then brought together during integration.

Configure delivery for the project

Setup controls whether completed tasks are merged, whether to ask first, whether pushing deploys, whether to tag a version and whether to prepare a fresh worktree after shipping. A preview shows the resulting instructions sent to the session.

A push only deploys if your repository has been configured that way. Supply the real deploy process and its verification in the relevant project or team settings. After confirmed delivery, IXIOM can prepare the next workspace while retaining the previous directory.

When automatic merging is disabled, saved work remains on its working branch. Dev Cockpit also provides explicit Git actions and tools to compare changes.

Related topics