> For the complete documentation index, see [llms.txt](https://docs.githud.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.githud.net/command-interface/concepts-and-architecture/overview.md). # Overview ## Overview: The Execution Engine Githud's Command Interface is much more than a standard developer tool—it is the primary execution engine that bridges your local environment with our decentralized Core Protocol. Designed as a lightweight, high-performance gateway, the interface is responsible for orchestrating all cryptographic operations locally, ensuring that zero-trust security is strictly maintained at every touchpoint. ### The Local Security Boundary Rather than relying on cloud-based authentication or transmitting vulnerable tokens over the network, the Command Interface handles all identity verification directly on the host machine. It seamlessly manages your local private keys and automatically signs every repository action before any data ever leaves your device. This architecture guarantees that your local environment remains the absolute source of truth, completely isolated from external interception. ### Strategic Advantages * **Security at the Edge:** By processing all cryptographic signatures locally, the interface ensures that your private keys never traverse the internet. This effectively neutralizes network-based credential theft and server-side breaches. * **Invisible Complexity:** While the underlying Ed25519 cryptography is military-grade, the user experience remains incredibly simple. The interface abstracts away the heavy lifting, allowing engineering teams to focus strictly on software development rather than managing complex security configurations. * **Universal Deployment:** Whether installed on a human engineer's laptop or embedded deep within a headless AI container, the Command Interface provides a unified, frictionless bridge to the Githud ecosystem. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.githud.net/command-interface/concepts-and-architecture/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.