> For the complete documentation index, see [llms.txt](https://docs.ostara.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ostara.dev/documentation/agents/installation/mac-linux.md).

# Mac/Linux

### Installation Using Brew

The agent is published on Brew and is available for installation on both Mac and Linux.

To install the agent using brew, run the following command and follow the instructions that appear on the screen

```
brew install krud-dev/tap/ostara-agent
```

Once the agent is properly configured, you can start it by running `brew services start ostara-agent`

The logs for the agent will be available at `<HOMEBREW_HOME>/var/log/ostara-agent.log`

### Standalone Installation

For a more hands-off installation, you may [download](https://search.maven.org/artifact/dev.ostara/ostara-agent) the JAR directly from Maven Central.

To set up and run the agent, run the following:

```bash
java -jar ostara-agent-VERSION.jar setup
java -jar ostara-agent-VERSION.jar start
```

{% hint style="warning" %}
When running the jar directly, ensure your installed Java is 17 or above&#x20;
{% 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://docs.ostara.dev/documentation/agents/installation/mac-linux.md?ask=<question>&goal=<user_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.
