Install and start AgReady
Install AgReady on the machine that will host your instance, start its server, and open that instance in your browser. The AgReady website is documentation—not a hosted account or your running instance.
On this page
This guide covers the v0.0.1 release and its associated installer defaults. The download entrypoint and platform modules can change independently. Review the installer you actually download. These instructions are based on release materials, not a claim that a clean installation was tested here.
Before installing
- Choose Linux or macOS, then the matching amd64 or arm64 package. Do not choose by operating system alone.
- Read the release notes, LICENSE and EULA. A public download does not grant an open-source license.
- Decide which machine will store the instance's configuration and data. On a remote server, arrange an administrator-approved access method before opening the UI.
- Keep the provider credentials you intend to use available privately. Do not put them in a support message or shell command copied into public logs.
The release includes Server archives with the Web UI. Runtime Assets and tool plugins are separate; installing the Server does not prove tools are ready.
Download and review the installer
Download without executing:
curl -fsSL https://download.agready.ai/agready/install.sh -o install-agready.sh
Inspect the saved script and the platform modules it retrieves. Confirm its destinations and requested privileges before running it:
bash install-agready.sh
For manually downloaded archives, use the release's SHA256SUMS for archive checksums. BINARY_SHA256SUMS describes binary checksums; do not compare an archive to a binary digest. A checksum establishes a match with the supplied digest, not permission to use the software.
Start on Linux
The default installation puts the executable at /usr/local/bin/agready and uses /opt/agready/server as the server working directory. The installer uses elevated privileges where needed, creates a systemd service named agready-server, enables and restarts it, and checks readiness.
Inspect the final installer output. To investigate without restarting:
systemctl status agready-server --no-pager journalctl -u agready-server -n 100 --no-pager
Access to service details and journals depends on your permissions. If the unit is missing or access is denied, ask the administrator to inspect the installation rather than changing permissions or rerunning setup blindly.
Start on macOS
The macOS installer does not automatically activate a managed service. For a fresh installation using the default paths, the printed start command is equivalent to:
cd "$HOME/.local/share/agready/server" && "$HOME/.local/bin/agready" start
Use the actual command printed by your installer if you selected different paths or it found an existing executable. Inspect the terminal output to determine whether startup succeeded.
Open your instance
The Linux installer defaults to checking http://127.0.0.1:18888/ for readiness. This is a local check, not a statement that the server listens only on loopback. In a browser on the same machine, that address refers to that machine. On your laptop, it does not refer to a remote server.
For a remote instance, use the address or secure connection method approved by its administrator. Do not disable certificate checks or authentication, or open a public port merely to make the page load. Do not infer a macOS address from a Linux readiness check; confirm your actual startup configuration.
Confirm the next step
A successful download is not a running service. A running service is not yet a configured model. Once the instance opens, follow Get started to initialize it, then test a real model connection and run the small text-only task.
If a login screen appears instead of first-time setup, do not initialize the instance again. Ask its administrator for access. For other failures, use the diagnostic checks.