Connect and open a project
- Select SSH in the sidebar to open Remote Explorer, then choose Add SSH host.
- Enter the host details, or pick a host under Import from ~/.ssh/config when your SSH config lists one. For Authentication, choose Auto (ssh-agent / default key), Key file or Password.
- Connect, browse the remote folders and add the project.
- Start a shell or agent there. The provider CLI and its login must be available on that machine.
A remote Kimi Code pane showing its SSH connection and working folder.
Send files to the remote agent
Paste an image or drop files onto its terminal. Dure uploads them and inserts remote paths after preparation succeeds. Wait before submitting the request; see terminal attachments.Reconnect and review
Reconnect to an existing managed remote session when its host is still running. A remote reboot or ended process requires recovery, not a claim of uninterrupted execution. Check state before starting duplicate work. Use Git on the remote host to inspect and combine changes. The built-in Diff review currently targets local worktrees.Read GitHub issues with your desktop login
Agents started in a GitHub SSH project by Dure can usegh issue list and gh issue view NUMBER --comments. Dure runs those reads with the desktop’s gh login and returns the result over SSH. The remote machine needs Python 3; it does not need a GitHub login or a local copy of the repository on your desktop.
origin on github.com. --repo may name that same repository. Use --state, --label, --assignee and --author for filters. --search accepts plain text without advanced qualifiers or boolean operators. Lists are limited to 100 results, and large responses must be narrowed with --json. Authentication commands, writes, other repositories, --web, templates and --jq are unavailable through this connection. Sign in with gh auth login on your desktop if a query reports an authentication error.
Keep the desktop app connected. After a disconnect or desktop restart, refresh the agent in Dure to restore the connection. Existing agents need a refresh to receive the new command environment. GitHub Enterprise and agents started directly outside Dure are not covered by this integration.
For local issue and pull-request workflows, use the GitHub sidebar guide.