Code and Git
On a computer, each session’s Git lives in Editor alongside: the branch at the top of the files column (with the ⋯ menu), the Changes with checkboxes, commit and push right below, and Recent commits at the bottom. On the phone and on narrow screens, the same things are in the session’s Code tab. You can review and ship the agent’s work without opening the computer.
Review and commit
- The branch, commits to push and to pull, and the changed files.
- View diff for each file.
- Check the files (or All), write the commit message and confirm.
- Push sends the commits to the remote repository.
- Recent commits show up below, and Open in VS Code opens the project on the computer.
Commit and push require the operator or owner role and go into the audit log. They use the machine’s own Git and credentials: Fleetly never sees your keys.
Sessions in a worktree
A session created in a new worktree (see Tools) works in a copy of its own. In the Code tab, it gets three actions:
- Open PR: pushes the branch and opens a pull request on GitHub. It uses the machine’s
gh, which must be signed in. - Merge into the main branch, in the repository’s main folder.
- Discard worktree: deletes the copy and the branch. The session’s chat stays in the history. If there are changes or commits that weren’t merged, the dashboard asks you to confirm first.
Folder without Git
If the session’s folder isn’t a repository, the tab says so. To start one, use New folder with git init in New session, or ask the agent.
Files and editor
In the editor header, the wrap lines button and A− / A+ change how code is shown, in diffs too. They’re saved in this browser and apply to every open editor.
The Files tab shows the files of the session’s project. Changes since the last commit sit at the top, with who changed each file (you or the agent); tapping one opens its diff. Below is the project tree, with an icon for each file type and a button to collapse the folders. Tap a file to view or edit it.
- On a computer: tap Editor alongside, right after the session tabs. You get three columns: files, editor and chat. Drag the dividers by their dotted handle to change the widths (double-click resets them). To go back to just the chat, tap Close editor (the same button) or the × at the top of the files. For more room for the code, collapse the files (the « at their top) or the chat (the » on the divider): the column becomes a thin strip, and a tap opens it again. In Editor colors, on the editor bar, pick the theme: the dashboard’s, Noite, Drácula, Monokai, Solarizado or GitHub claro.
- On a phone: the Files tab shows the tree; a file opens full screen, with a row of keys the keyboard lacks (Tab, braces, parentheses).
- Edit and Diff (the diff against the last commit) are at the top of changed files. Save (⌘S) writes it on the machine.
- Save and ask to test saves and writes a request in the chat for the agent to check and run the tests. You review it before sending.
- The files you saved are listed in your next message, so the agent knows what you changed. The note above the message box shows which; the × removes it.
- If the agent changes the file before you save, nothing is written: Fleetly tells you and you choose between Use the current version and Overwrite with mine.
What’s left out: folders ignored by Git (like node_modules) don’t show. Secrets files (.env, keys) show, but their contents never leave the machine. Binary files or files over 1 MB don’t open. The editor changes existing files; to create, delete or rename, ask the agent.
Viewing files is for anyone who can see the session; saving requires the operator or owner role and goes into the audit log (the file path, never the contents). The building policy applies as it does to the agent: a forbidden folder doesn’t open, and what the policy won’t let the agent write is read-only.
Away from your computer: with the code in Git, open a session on a machine that stays on (a server, for example) and ask the agent to pull or clone the repository. From then on, chat with it and work on the files from your phone.
Didn’t find what you were looking for? Write to admin@fleetly.tools.