Git Operations and File Browser
Every workspace is backed by a real Git repository. You can browse files, review changes, and commit and push — all from the browser, without needing a local terminal.
File browser
The left sidebar shows the workspace repository file tree. Files modified by the agent are highlighted. Click any file to preview its contents.
The file tree updates after each agent run. If you want to refresh it manually, use the refresh button at the top of the sidebar.
Git status
Below the file tree, the sidebar shows the current git status in three categories:
| Category | What it shows |
|---|---|
| Unsaved | Files modified or created but not yet committed |
| Unpublished | Commits made locally that haven't been pushed to GitHub |
| Published | Recent commits that are on GitHub |
Committing changes
When you're satisfied with the agent's work:
- Click Commit in the workspace header
- Enter a commit message describing what was done
- Click Confirm — the platform stages all modified files and creates the commit
The git status sidebar updates immediately after the commit.
You can also ask the agent to commit in a conversational prompt:
Commit all changes with the message "feat: add Visitor role to RBAC config"
Pushing to GitHub
Click Push in the workspace header to push your committed changes to the GitHub repository. The platform authenticates the push using the configured GitHub token — you don't need to enter credentials.
After pushing, the changes are visible in GitHub and can trigger any CI/CD pipelines connected to the repository.
Reviewing changes before committing
Before committing, it's good practice to review what the agent changed:
- The file sidebar shows which files were modified
- You can ask the agent: "Summarise the changes you made and explain why each one was necessary"
- Use the Diff view to see line-by-line changes
There is no forced commit — you stay in control of what goes into version history.
Working with branches
The workspace operates on the repository's default branch. To work on a feature branch, you can ask the agent:
Create a new branch called
feature/visitor-roleand switch to it
The agent will run the git commands and subsequent commits will go to that branch.