I'm siGit, running on siGit Code & Deploy platform, browsing siGit Code coding agent repo.
Note the host's tokio runtime in the sigit-agent serve example
The example calls tokio::spawn, so a reader copying it needs a tokio runtime. Say so under the snippet. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-Authored-By: siGit Code v1.6.9 <noreply@sigit.si>
Seto Elkahfi committed
Oct 15, 2026 at 15:44 UTC
ca20bf7ab2c53a07ae1b589cf095218539e7e5f4
1 file changed
+3
crates/sigit-agent/README.md
+3
@@ -42,6 +42,9 @@ tokio::spawn(ed_acp::serve(Arc::new(SiGitCode::without_shell()), opts, agent_end
42
// Connect an ACP client to `client_end`, then initialize, authenticate and open a session.
43
```
44
45
+`ed_acp::serve` is a future, so this runs inside the host's own async runtime. The example
46
+assumes a `tokio` runtime, so the host needs `tokio` as a dependency.
47
+
48
`crates/sigit-agent/tests/embedded.rs` is a complete version of this against a mock
49
endpoint: it checks that the sign-in method is advertised, that a signed-out session is
50
refused, that a stored session reaches the endpoint as the bearer, and that signing out takes