See who is working where
View active coding agents beside the repository, branch state, local changes and work that needs attention.
See where Claude Code, Codex, opencode and supported agent sessions are working. Continue a conversation from your phone, open a remote terminal, compare parallel work and keep repository state visible.
FluxGit connects agent activity to the repositories and Git state those agents are changing, so the next action is easy to understand.
View active coding agents beside the repository, branch state, local changes and work that needs attention.
Talk to supported Claude Code, Codex and opencode sessions from FluxGit, including sessions started in compatible terminals.
Use desktop terminal sessions from your phone for agents and ordinary command-line work while the tools keep running on your computer.
Connect agent work to diffs, proposals, approvals, restore points and repository history instead of treating chat as the whole story.
Open Fleet Radar to find the active agents, repositories and waiting work.
Continue an agent conversation, enter its terminal or start a separate remote terminal.
Inspect what changed and use the right approval or recovery path before repository state moves.
FluxGit coordinates coding tools such as Claude Code, Codex and opencode. Models such as DeepSeek can participate through a compatible agent or local tool. Support is described per integration, so model choice does not blur the control boundary.
Claude Code and Codex are the verified lead integrations. opencode has live integration evidence. Gemini CLI and Qwen Code paths are implemented and still moving through release verification; additional tools are tracked explicitly.
FluxGit is building mobile alerts for finished work and decisions that need you. Push text stays generic; commands, prompts and repository content are not placed in the notification payload.
Remote records use authenticated Noise encryption with WebRTC DTLS as another layer. Repository, terminal, observation, prompt and decision access use separate scoped, revocable grants controlled by the desktop.
FluxGit Mobile is designed to show agent and repository state, continue supported conversations and access authorized desktop terminals while the agents keep running on the paired computer.
No. The coding agent and model run through the desktop environment or provider you choose. The phone is a control and visibility surface.
Yes when DeepSeek is used through a compatible coding agent, local model tool or terminal workflow. FluxGit documents support for the tool integration rather than claiming a direct DeepSeek harness.