> For the complete documentation index, see [llms.txt](https://bhagavata.keshavaswami.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bhagavata.keshavaswami.com/canto-11/s.u.m/m-mausala-lila-30-31/disappearance-of-krishna/why-did-krishna-depart-in-a-seemingly-mundane-way.md). # Why did Krishna depart in a seemingly mundane way? If one studies the events surrounding Krishna’s departure it is clear that they were entirely spiritual, defying all material logic. Firstly, Krishna disappeared because of an arrow shot to His leg. Do we have any experience of such an injury being instantaneously fatal? Secondly, Krishna was so pleased by the hunter who shot Him that He sent him back to Godhead. Unless someone was in complete control, orchestrating the entire sequence of events, could they react in such a way? Thirdly, Krishna showed on numerous occasions that He could overturn death if He desired (e.g. bringing back the dead son of His teacher), but chose not to in this situation. --- # 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://bhagavata.keshavaswami.com/canto-11/s.u.m/m-mausala-lila-30-31/disappearance-of-krishna/why-did-krishna-depart-in-a-seemingly-mundane-way.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.