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
Add documentation for new features from reference implementation
- Document instructionDirectories in advanced.md
- Document continuePendingWork in advanced.md
- Document copilotHome and tcpConnectionToken in advanced.md
- Update Table of Contents
Co-authored-by: edburns <75821+edburns@users.noreply.github.com>
This sets the `COPILOT_HOME` environment variable on the spawned CLI process. When not set, the CLI defaults to `~/.copilot`. This option is only used when the SDK spawns the CLI process; it is ignored when connecting to an external server via `setCliUrl()`.
891
+
892
+
### TCP Connection Token
893
+
894
+
When using TCP transport, you can set a connection token for authentication:
895
+
896
+
```java
897
+
var client =newCopilotClient(
898
+
newCopilotClientOptions()
899
+
.setUseStdio(false)
900
+
.setTcpConnectionToken("my-secret-token")
901
+
);
902
+
```
903
+
904
+
When the SDK spawns its own CLI in TCP mode and no token is specified, a UUID is generated automatically so the loopback listener is safe by default. The token cannot be used with stdio transport.
0 commit comments