> 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/using-mirrord/targetless.md). # Running Without a Target How to run mirrord without a remote target The common use case for mirrord is testing out modifications to an existing application. In this case, the stable version of the service is running in the cloud, and the new code runs locally, using the stable cloud version as its remote target. However, sometimes you want to test a brand new application that has never been deployed to the cloud. Or you might not want to run an application at all - maybe you just want to run a tool, like Postman or pgAdmin, in the context of your cluster. This is where targetless mode comes in. When running in targetless mode, mirrord doesn't impersonate a remote target. There's no incoming traffic functionality in this mode, since there's no remote target receiving traffic, but everything else works exactly the same. To run mirrord in targetless mode, just don't specify a target! For example: ```bash mirrord exec /bin/my-tool ``` ### IDE If you want to run in targetless mode using the JetBrains or VS Code plugin, you can select the `No Target ("targetless")` option from the target selection dialog, or you can add ```json { "target": "targetless" } ``` to your mirrord configuration file. ### What's next? 1. If you'd like to intercept traffic rather than mirror it so that your local process is the one answering the remote requests, check out [this guide](/mirrord/docs/using-mirrord/incoming-traffic/filter-incoming-traffic.md). Note that you can even filter which traffic you intercept! 2. Want to use Targetless mode to run a web browser in the context of your cluster? Check out this [guide](/mirrord/docs/using-mirrord/connecting-tools/web-browsing.md). 3. If you just want to learn more about mirrord, why not check out our [architecture](/mirrord/docs/reference/architecture.md) or [configuration](https://metalbear.com/mirrord/docs/config) sections? --- # 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/using-mirrord/targetless.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.