Installation

This page gets you set up. The Quickstart then walks through doing real work.

What you need

• The Chronos client for your computer, provided by your organization. Chronos v1 runs on macOS (Apple Silicon and Intel).
• Access to a coding agent, signed in. Chronos works with leading AI coding agents; your organization will tell you which one to use and help you sign in.
• A repository you have permission to work on.

If anything here isn’t in place, contact your Chronos administrator — they manage access, the available agents, and your organization’s governance settings.

Install

1. Run the installer. Your administrator will give you the install command; it typically looks like:

   curl -fsSL https://raw.githubusercontent.com/renaiss-ai/aluxion-chronos/main/scripts/install.sh | sh

   The installer downloads the latest release, verifies its SHA-256 checksum, and installs the chronos and chronosd commands into ~/.local/bin. It also places the user guide where the dashboard serves it at /docs.

2. Check it worked:

   chronos --version

   If the installer notes that ~/.local/bin is not on your PATH, add it:

   echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc

3. Sign in. If your organization runs a Chronos enterprise panel, sign this machine in once:

   chronos login --panel https://panel.your-org.example

   The command shows a short code and a link. Open the link, enter the code and your work identity, and the terminal completes the sign-in by itself. Your credential is stored in the operating system’s keychain — never in a file — and Chronos remembers the panel, so future sign-ins are just chronos login. Check who is signed in with chronos login --status, and sign out with chronos logout.

   Signing in is what connects your sessions to the organization’s governance: approved connectors, shared context and your role all come from the panel.

4. Open Chronos. Start the daemon and open the dashboard:

   chronosd

   Then open http://127.0.0.1:4173 — a three-pane workspace where you’ll connect repositories, run sessions and review changes. Everything runs on your own machine; your code stays local unless you choose to open a pull request.

5. Connect a repository. In the dashboard header, enter the path to a repository (or . for the one you’re currently in) and click Open. The first time you connect a repository, Chronos sets up its workspace settings; you can adjust them later.

Tip

For your very first run, use a small or throwaway repository so you can explore freely before pointing Chronos at something important.

Installer options

The install script can also be run directly, optionally pinned to a specific release tag:

sh scripts/install.sh          # latest release
sh scripts/install.sh v0.1.0   # a specific tag

It reads a few environment variables:

Variable	Purpose	Default
CHRONOS_REPO	GitHub repo slug to download from	renaiss-ai/aluxion-chronos
CHRONOS_PREFIX	Install prefix (binaries go in <prefix>/bin)	~/.local
GITHUB_TOKEN	Used for API downloads when the gh CLI is not installed (required while the repo is private)	—

The script prefers an authenticated gh CLI, falls back to the GitHub API with GITHUB_TOKEN, then to anonymous download. It always verifies the SHA-256 checksum before installing.

If the release is not code-signed and Gatekeeper blocks the binaries, remove the quarantine attribute:

xattr -d com.apple.quarantine ~/.local/bin/chronos ~/.local/bin/chronosd

Desktop app (.dmg)

Each release also ships a desktop app image, Chronos-<version>-<target>.dmg, with chronosd bundled inside as a sidecar. Drag it to Applications; on unsigned builds, right-click → Open the first time.

You’re ready

That’s it — no lengthy setup. Continue to the Quickstart to put an agent to work.