You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remote Tool Host executes an Agent's file, Shell, and LSP tools on another machine on the same network. This page targets integrators and operators who set a pairing up outside DotCraft Desktop.
4
+
5
+
6
+
7
+
8
+
## Responsibility split
9
+
10
+
The Agent machine owns the model loop, approvals, hooks, and the Session history. The workspace machine owns the real workspace, the local tool policy, and the execution audit. A remotely executed tool keeps its existing tool identity, schema, and Session projection — remote execution replaces only the runtime route behind a stable registration, so the model never sees a second, remote copy of a tool.
11
+
12
+
The Hub on the Agent machine is the rendezvous point. The Remote Tool Host dials out to it and never listens for inbound connections, so the workspace machine needs no inbound firewall rule, port forward, or TLS identity. The Hub relays the bytes between the two sides without interpreting them.
13
+
14
+
Both machines run as the signed-in user, not as a service, so both must stay signed in.
15
+
16
+
## Pair from the command line
17
+
18
+
The Agent machine runs DotCraft Hub (`dotcraft hub`), and the workspace machine must be able to reach it on port 47600. Run this on the Agent machine to mint an invitation:
The command prints the invitation link plus the exact command to run on the other machine. An invitation names this device by its host name; if the other machine cannot resolve it, mint the invitation with the address to dial instead:
`join` stores a long-lived credential in the operating-system credential store and prints the workspace id that Agents will use. `serve` keeps the control connection open and reconnects on its own after a Hub restart. To start it at sign-in:
41
+
42
+
```powershell
43
+
dotcraft tool-host autostart install
44
+
```
45
+
46
+
[DotCraft Satellite](../../features/agent-system/satellite) is the tray client that replaces `setup`, `join`, `serve`, and `autostart install` with an installer and an approval window, for a machine owner who does not want a terminal.
47
+
48
+
## Inspect and route
49
+
50
+
On the Agent machine, `dotcraft tool-host list` prints the machines paired with this Hub and their ids, and `dotcraft tool-host test <machine-id>` checks whether one of them is online. On the workspace machine, `dotcraft tool-host workspace list` prints the folders it exports, and the policy commands show and change what it will run:
51
+
52
+
```powershell
53
+
dotcraft tool-host policy list
54
+
dotcraft tool-host policy set Exec needs-approval
55
+
```
56
+
57
+
A policy is `allow`, `deny`, or `needs-approval`, set per canonical tool name.
58
+
59
+
Policies are enforced on the Tool Host. An Agent cannot weaken a `deny` rule or create a permanent approval on the remote machine.
60
+
61
+
Outside Desktop, an Agent routes a conversation with the `RemoteToolHost.List`, `RemoteToolHost.Connect`, and `RemoteToolHost.Disconnect` model tools:
62
+
63
+
```text
64
+
Call RemoteToolHost.List, then connect this conversation to workspace
65
+
sample-project on <machine-id> with RemoteToolHost.Connect.
66
+
```
67
+
68
+
A workspace serves one Agent Host at a time. If it is already held, disconnect it there or wait for it to be released — there is no queue and no takeover. A remote failure is reported as a remote failure; DotCraft never silently retries the call against the local binding.
69
+
70
+
## End a pairing
71
+
72
+
```powershell
73
+
dotcraft tool-host revoke <machine-id>
74
+
```
75
+
76
+
On the Agent machine this removes the peer from the Hub and closes its connections. On the workspace machine it deletes the local pairing and stops `serve`. Either side is enough — the stored credential goes with it.
77
+
78
+
## Related docs
79
+
80
+
-[DotCraft Satellite](../../features/agent-system/satellite) — the same pairing driven from Desktop
81
+
-[Architecture overview](./overview) — where the Hub and the Agent Host sit in the wider runtime
Copy file name to clipboardExpand all lines: docs/features/agent-system/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ At the center of DotCraft is one agent that keeps growing with your project. The
6
6
7
7
## Extend what it can do
8
8
9
-
[Skills & Self-Learning](./skills) turns a workflow that already worked into a reusable skill, ready for the next task of the same kind. [Plugins & Tools](./plugins-tools) covers the built-in tools, plugins, and MCP servers that give the agent its capabilities, and the trust boundary around each. [Remote Tool Host](./remote-tool-host) runs eligible built-in tools in a workspace on another device without moving the Agent session, and [DotCraft Satellite](./satellite) is what the owner of that device installs to approve and watch it. When you need more, [Plugin Marketplaces](./plugin-marketplaces) adds plugin catalogs you trust, and [Connected Apps](./connected-apps) lets a conversation work directly with the products and services you already use.
9
+
[Skills & Self-Learning](./skills) turns a workflow that already worked into a reusable skill, ready for the next task of the same kind. [Plugins & Tools](./plugins-tools) covers the built-in tools, plugins, and MCP servers that give the agent its capabilities, and the trust boundary around each. [DotCraft Satellite](./satellite) lets the agent work in a shared folder on a colleague's PC — you invite the PC from Desktop, and its owner approves the one folder and can stop it at any time. When you need more, [Plugin Marketplaces](./plugin-marketplaces) adds plugin catalogs you trust, and [Connected Apps](./connected-apps) lets a conversation work directly with the products and services you already use.
0 commit comments