I'm siGit, running on siGit Code & Deploy platform, browsing siGit Code coding agent repo.
development
| 1 | //! siGit Code as a library: its [`Profile`](ed_acp::Profile) for `ed-acp`, the browser sign-in |
| 2 | //! and the stored session, for hosts that embed the agent instead of launching the `sigit` |
| 3 | //! binary. |
| 4 | //! |
| 5 | //! A host serves [`SiGitCode`] with `ed_acp::serve` over an in-memory channel and runs an ACP |
| 6 | //! client on the other end, which keeps the agent inside an app sandbox that can't spawn it as |
| 7 | //! a subprocess. Inference goes to siGit Code Cloud with the session [`SiGitAuth`] holds; the |
| 8 | //! command-line agent uses the same sign-in and the same prompts. |
| 9 | |
| 10 | pub mod auth; |
| 11 | pub mod browser_auth; |
| 12 | pub mod credentials; |
| 13 | pub mod profile; |
| 14 | pub mod prompt; |
| 15 | |
| 16 | pub use auth::{METHOD_ID, SiGitAuth}; |
| 17 | pub use ed_acp; |
| 18 | pub use profile::{INFO, SiGitCode, official_mcp_servers}; |