Usage¶

One-liner (session install)¶

Install tools into your current shell session:

Bash / ZshFish

source <(curl -sL in-1.cc) rust node

curl -sL in-1.cc | source - rust node

For silent use in a script, pass -q or --quiet:

source <(curl -sL in-1.cc) -q rust node

Successful notes, progress and status output are suppressed. Failure diagnostics remain visible.

Each bare argument is a tool name (or an alias). A NAME=VALUE argument is passed through to makes as a variable, so you pin a version with the tool's makes variable:

source <(curl -sL in-1.cc) go GO-VERSION=1.23.4 jq

An alias can abbreviate its tool's version variable, so bb BB-VERSION=1.13.220 is equivalent to using BABASHKA-VERSION=1.13.220.

PREFIX=DIR is the exception: it sets the install prefix instead of going to makes.

The one-liner clones in-1 to ${TMPDIR:-/tmp}/in-1/bootstrap, independently of inherited IN1_ROOT. The install prefix follows an installed in-1, or defaults to ${TMPDIR:-/tmp}/in-1 on a fresh machine. Each version installs under $PREFIX/share/<tool>/<version>, with wrappers in $PREFIX/bin. So which node is $PREFIX/bin/node, the wrapper carries the tool's own environment (CARGO_HOME, ...), and your shell itself stays clean. Your shell also gets MANPATH entries and completions.

Multiple versions coexist. The primary command of a tool also gets a version-specific wrapper, so go GO-VERSION=1.23.4 gives you both go and go-1.23.4 on PATH.

Sourcing again is idempotent; PATH never collects duplicates. IN1_TOOLS in the environment lists what is active.

Aliases¶

Some tools can be requested by a command name they provide:

source <(curl -sL in-1.cc) cargo   # installs rust
source <(curl -sL in-1.cc) bb      # installs babashka

in-1 --list shows the available aliases along with the tools. Aliases are shown as bb (babashka); direct tool names are unannotated. Tab completion shows alias targets when there are multiple matches, but inserts only the command name.

Installed mode¶

in-1 is itself one of the tools, so the one-liner installs it too:

source <(curl -sL in-1.cc) in-1     # bash / zsh
curl -sL in-1.cc | source - in-1    # fish

For keeps, in-1 --local in-1 installs it under ~/.local (source <(curl -sL in-1.cc) --local in-1 does that and sets up the current shell too); then let the command point your shell rc file at its own .rc, so the line survives upgrades:

echo 'source <(in-1 --rc)' >> ~/.bashrc          # or .zshrc
echo 'in-1 --rc | source' >> ~/.config/fish/config.fish

Or clone the repo once and source its .rc from your shell rc file:

git clone https://github.com/in-1-cc/in-1 ~/.in-1
echo 'source ~/.in-1/.rc' >> ~/.bashrc  # or .zshrc, or config.fish

Each way puts the in-1 command, its man page and its tab completion in your shell, and wraps the command in a small shell function so that session installs work directly. .rc also sets IN1_ROOT, unless it is already set: to the clone it lives in, or for a --local installed in-1 to the stable ~/.local/share/in-1/local, which survives version changes.

in-1 rust node            # install alongside in-1
in-1 --temp jq            # force a temporary install
in-1 --list               # all available tools
in-1 --update             # update in-1
man in-1

Persistent installs¶

in-1 --local rust node

Selects an existing persistent prefix, otherwise ~/.local (or /usr/local when root), with each tool installed into $PREFIX/share/<tool>/<version>, and writes a wrapper for each command into $PREFIX/bin. The wrappers bake in the environment the tools need, so they work from any shell with no setup, and $PREFIX/bin/<cmd> is what which resolves.

in-1 never overwrites a file in $PREFIX/bin that it did not create.

Temporary installs¶

--temp forces ${TMPDIR:-/tmp}/in-1, ignoring inherited PREFIX and IN1_ROOT. It rejects PREFIX=DIR arguments and cannot be combined with --local. It also works with --show, --uninstall, and --reset. If an old temporary checkout conflicts, move it aside before retrying; in-1 will not overwrite or automatically migrate it.

Uninstalling¶

in-1 --uninstall rust node

removes the installs of the named tools from PREFIX: $PREFIX/share/<tool> with every version in it, and the wrappers in $PREFIX/bin that in-1 wrote for it. Files in $PREFIX/bin that in-1 did not create stay. The shell function and direct command use the same prefix as installation:

source <(curl -sL in-1.cc) in-1
in-1 rust node
in-1 --uninstall rust node

The curl one-liner rejects --uninstall; install the in-1 command into the session first, as above. An explicit PREFIX overrides normal and local defaults. Aliases work here too (in-1 --uninstall bb removes babashka), and in-1 --uninstall in-1 removes the command itself. --reset, below, removes other managed tools while preserving in-1 itself.

Updating¶

Before an install, in-1 checks whether its own clone is behind its origin, and says so. It also checks its makes clone and updates that automatically when it is behind:

√ makes is now at 1a2b3c4

Use --update to update in-1 as well as makes before carrying on with whatever else you asked for:

in-1 --update                             # just update
in-1 --update node                        # update, then install node
source <(curl -sL in-1.cc) --update node  # same, from the one-liner

The in-1 clone moves to the latest default branch (or to IN1_VERSION if set). The one-liner pins a fresh clone to the version it was published with, but leaves a clone that is already on a branch alone, so an update sticks.

For a persistent install, --update updates the clone containing the running command when IN1_ROOT is its state directory. Makes and logs stay under IN1_ROOT; tools live in the selected prefix.

Set IN1_OFFLINE=1 to skip both update checks, including the automatic makes update, for instance on a flaky connection.

Resetting¶

--reset removes managed versions and wrappers from the selected prefix, except in-1 itself, and clears makes/, log/ and cache/ under IN1_ROOT. Unrelated files, old nested installations, and external caches stay. Alone it does just that; with anything else it resets first and then carries on:

in-1 --reset                              # just reset
in-1 --reset node                         # reset, then install node
in-1 --reset --update node                # reset, update, then install
source <(curl -sL in-1.cc) --reset node   # same, from the one-liner

After a reset IN1_TOOLS lists only the tools installed since.

Command reference¶

in-1 TOOL... [VAR=VALUE]...  Install tools for this shell session
in-1 --local TOOL...         Install tools under PREFIX for keeps
in-1 --temp TOOL...          Use $TMPDIR/in-1, ignoring inherited PREFIX
in-1 --uninstall TOOL...     Remove tools from their install prefix
in-1 --list [PATTERN]        List available tools, optionally filtered
in-1 --show [PATTERN]        Show installed versions and locations
in-1 --env SHELL TOOL...     Print env setup code for SHELL
in-1 --complete SHELL        Print in-1 command completion for SHELL
in-1 --rc                    Print the shell setup line (source it)
in-1 -q|--quiet ARGS...      Suppress output on success
in-1 --update [ARGS]         Update in-1 and makes, then continue
in-1 --reset [ARGS]          Remove managed tools and state; keep in-1
in-1 --version               Print the in-1 version
in-1 --help                  Show help

in-1 --env is the plumbing everything else uses; you can call it yourself:

eval "$(in-1 --env bash rust)"     # bash / zsh
in-1 --env fish rust | source      # fish

Environment variables¶

IN1_ROOT: State directory for Makes, logs and downloads. Default: $PREFIX/share/in-1/local. The one-liner and --temp ignore an inherited value. A sourced development checkout may use its own directory for state. This variable does not choose the installation prefix. Sourcing .rc exports it.
IN1_CACHE: Download cache directory. Default: $IN1_ROOT/cache. Point this somewhere persistent to keep downloads across reboots.
PREFIX: Install prefix. Normally the public prefix of the installed in-1, otherwise ${TMPDIR:-/tmp}/in-1. --local falls back to ~/.local or /usr/local when root. --temp ignores this variable and rejects an argument override. A relative path is anchored to the current directory. A PREFIX=DIR argument sets it too, so the one-liner can pick a prefix: source <(curl -sL in-1.cc) jq PREFIX=/opt/tools.
IN1_VERSION: The in-1 git ref to use. The script served by in-1.cc pins a fresh clone to the version it was published with; set this to override.
IN1_REPO: The in-1 repo URL to clone. Default: https://github.com/in-1-cc/in-1.
IN1_MAKES_REPO: The makes repo URL to clone. Default: https://github.com/makeplus/makes.
IN1_UPDATE: Set to 1 for the same effect as --update.
IN1_OFFLINE: Set to 1 to skip update checks before installs, including the automatic makes update.
IN1_VERBOSE: Set to 1 to stream the full install output instead of the quiet per-tool progress lines. -q and --quiet take precedence when either is used.

Any makes version variable can also be passed in the environment, e.g. NODE-VERSION=22.11.0 in-1 node does what the NAME=VALUE argument does.

Requirements¶

git, curl, GNU make and bash on PATH. Everything else is auto-installed.