> For the complete documentation index, see [llms.txt](https://docs.urbit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbit.org/urbit-os/kernel.md). # Kernel API documentation and guides for the Urbit OS kernel and its modules Ames, Behn, Clay, Dill, Eyre, Gall, Iris, Jael, Khan, and Lick. Guides and API documentation for the Urbit OS kernel, including Arvo and the various modules. * [Arvo](/urbit-os/kernel/arvo.md) - The kernel itself. Implements the event loop and otherwise acts as air-traffic-control between the modules. * [Ames](/urbit-os/kernel/ames.md) - Ames is the name of our encrypted peer-to-peer networking protocol and the module that communicates over it. * [Behn](/urbit-os/kernel/behn.md) - Timer module. Allows Urbit OS and third-party applications to set and respond to timer events. * [Clay](/urbit-os/kernel/clay.md) - Revision-controlled filesystem. * [Dill](/urbit-os/kernel/dill.md) - Terminal driver. The Urbit runtime sends keyboard events to Dill from the terminal, and Dill produces terminal output. * [Eyre](/urbit-os/kernel/eyre.md) - HTTP server. The runtime sends HTTP requests to Eyre, and Eyre forms HTTP responses. * [Gall](/urbit-os/kernel/gall.md) - A framework for running state machines and third-party applications. * [Iris](/urbit-os/kernel/iris.md) - HTTP client. * [Jael](/urbit-os/kernel/jael.md) - Manages networking keys and Azimuth state. * [Khan](/urbit-os/kernel/khan.md) - Thread dispatcher, the kernel's alternative to spider. * [Lick](/urbit-os/kernel/lick.md) - IPC module for communicating with processes on the host machine. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.urbit.org/urbit-os/kernel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.