On your own computer
Run a Foxl Code task on your own machine, with your own CLI login and your own GitHub credential
On your own computer
By default a Foxl Code task runs in Foxl's cloud. It can also run on your machine: the clone, the coding CLI, the commit, the push and the pull request all happen there, using the CLI you are already signed into and your own GitHub credential. Nothing about the task reaches Foxl's cloud.
Off until you turn it on, and turning it on has to come from the machine itself - never from the web app or your phone - because it decides where your code runs.
Turning it on
Settings > Code > This computer, in the Foxl app on the machine you want the work to happen on. The answer is stored on that machine, so it survives a restart, an app update and a reboot.
If you run the desktop server yourself, FOXL_CODE_LOCAL_AGENT=1 in its environment turns it
on for that run and takes precedence over the stored answer.
The same pane is where the rest of it is configured:
- the clone folder - where repositories are checked out (see below);
- the folder a terminal starts in when no repository is selected;
- whether a coding agent asks first before it edits files and runs commands.
Which assistant runs it
Any of the six: Claude Code, Codex, Kiro, Cursor, Hermes, OpenCode. Each is launched the way that vendor's CLI actually wants, and a CLI you have not signed into says so in its own words rather than failing as "the task failed" - so a missing login reads as a missing login.
The choice comes from your account default, which you can change in the Tasks header or under Coding agents.
A pane on this computer starts the same program which claude names in your terminal, even
when a wrapper sits beside the original, and leaves your PATH untouched when the two already
agree.
Where your repositories go
A repo is cloned to ~/workspaces/<owner>/<name>, so two owners of the same repository name
never collide.
If that folder already exists it is used as it is. No fetch, no pull, no stash, no checkout - it may be your live working copy with uncommitted work in it, and Foxl will not raise a conflict in a tree you were in the middle of.
Seeing what happened
Tasks that ran on this machine appear in the Foxl Code Tasks list under On this computer, with the assistant that ran them, the goal, the repository and how long ago. Each row opens the task's own page - the live terminal you can type into, the status, the branch, a Stop button, and the pull request link in its header once there is one - and it opens while the task is still running, since that page is the only place the agent's output exists.
The group only appears where a Foxl desktop is actually reachable, so on the web with your machine asleep it simply is not there.
The assistant may open the pull request itself, and that is fine. Most of these CLIs do their own git even when asked not to: several commit, push, open a pull request and then put the branch back the way they found it. Foxl recognises its own work by commit, adopts the pull request that already exists rather than opening a second one beside it, and says which of the two of you opened it.
Remote, this computer, or a box of your own
The machine segment of the Tasks and Runtimes header (+ | Remote | Claude Code) is where a
task runs:
- Remote - the free machine Foxl runs your work on. Always there, the default, and not removable. It used to be called Foxl Cloud.
- This computer - your Foxl desktop, once you have turned it on above.
- A machine you add in Settings > Code > Machines: either Launch on AWS (pick a Light, Balanced or Power size and a region; Foxl shows an estimate with a link to AWS's own calculator and prints the commands to run where your AWS CLI is set up) or an SSH box you already have. It uses that box's CPU, disk and network - your bill, your account. Foxl holds no credential for your AWS account, so removing a machine from Foxl does not stop the instance.
Picking a machine sets your account default. A repository can also be pinned to a machine from the same menu, and the pin wins for that repository: Foxl resolves the machine as repo pin, then account default, then Remote. This computer cannot be pinned to a repository. A machine that has stopped checking in is reported as unreachable and skipped in that chain rather than dispatched to.
What still runs in the cloud
Turning this on does not move anything that was already running. Existing tasks keep running in Foxl's cloud exactly as before, and the autonomous loop and scheduled tasks are unaffected.
The orchestrator you talk to in Foxl Code is what starts a local task, and it tells you which
machine the work is on. On your computer it can also read the repository it is planning about -
CI status, a failing build, an issue - using the credential you already have: gh auth login,
your git credential helper, or FOXL_CODE_GITHUB_TOKEN. Reads stay confined to the repository
you have selected, and if no credential exists the refusal says so.