> For the complete documentation index, see [llms.txt](https://metalbear.com/mirrord/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metalbear.com/mirrord/docs/guides/readme.md). # Guides Step-by-step guides for debugging microservices, testing AI-generated code, and running AI agents in Kubernetes with mirrord These guides walk you through debugging real applications running in Kubernetes using [mirrord](https://metalbear.com/mirrord/). Each guide includes a sample application, step-by-step IDE and CLI setup, and a comparison with traditional debugging techniques. ## Language Guides Debug microservices written in your language of choice, with IDE integration and CLI workflows. | Language | IDE | Guide | | ----------- | ------------- | ---------------------------------------------------------------------------------------------------------------- | | **Java** | IntelliJ IDEA | [How to Debug Java Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-java-microservice.md) | | **Go** | GoLand | [How to Debug Go Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-go-microservice.md) | | **Node.js** | VS Code | [How to Debug Node.js Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-nodejs-microservice.md) | | **Kotlin** | IntelliJ IDEA | [How to Debug Kotlin Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-kotlin-microservice.md) | | **Ruby** | RubyMine | [How to Debug Ruby Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-ruby-microservice.md) | | **PHP** | CLI | [How to Debug PHP Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-php-microservice.md) | | **Python** | VS Code | [How to Debug Python Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-python-microservice.md) | | **.NET** | VS Code | [How to Debug .NET Microservices](/mirrord/docs/guides/language-guides/how-to-debug-a-dotnet-microservice.md) | ## Queue Guides Debug queue consumers with mirrord's copy target and queue splitting features. | Queue | Guide | | --------- | ------------------------------------------------------------------------------------------------- | | **Kafka** | [How to Debug Kafka Consumers](/mirrord/docs/guides/queue-guides/how-to-debug-kafka-consumers.md) | | **SQS** | [How to Debug SQS Consumers](/mirrord/docs/guides/queue-guides/how-to-debug-sqs-consumers.md) | ## AI Guides Use mirrord to test AI-generated code and run AI coding agents against your Kubernetes cluster. | Guide | Description | | ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | | [**How to Set Up AI Tools with mirrord**](/mirrord/docs/guides/ai-guides/setting-up-mirrord-for-ai-tools.md) | Configure Cursor, Claude Code, Copilot, Codex, and Windsurf | | [**How to Test AI-Generated Code with mirrord**](/mirrord/docs/guides/ai-guides/testing-ai-generated-code.md) | Validate AI-generated code against your Kubernetes cluster | | [**Autonomous AI Workflows with mirrord**](/mirrord/docs/guides/ai-guides/running-ai-agents-with-mirrord.md) | Set up E2E guardrails so agents validate their own changes | *** {% hint style="info" %} All guides use a sample Guestbook or message-processing application. You can find the source code linked in each guide. {% endhint %} --- # 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://metalbear.com/mirrord/docs/guides/readme.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.