Skip to content

Say where install.sh puts entire on Linux - #2724

Open
HighnessAtharva wants to merge 1 commit into
entireio:mainfrom
HighnessAtharva:firstrun/linux-install-path
Open

HighnessAtharva wants to merge 1 commit into
entireio:mainfrom
HighnessAtharva:firstrun/linux-install-path

Conversation

@HighnessAtharva

Copy link
Copy Markdown

On a fresh Linux shell, curl -fsSL https://entire.io/install.sh | bash succeeds, and the next step, entire version, fails with entire: command not found. The script installs entire and git-remote-entire to ~/.local/bin, which is not on PATH in a clean shell.

The Windows section already says where the binaries go and that the installer adds the folder to PATH. This PR adds the Linux equivalent after the install block.

Thank you for Entire. I used it to record every agent session behind every commit while building FirstRun at neatHack, and FirstRun found this on its own run of the Entire install docs in a clean python:3.11-slim container. A second clean container ran the patched steps and passed.

🤖 Generated with Claude Code

@HighnessAtharva
HighnessAtharva requested a review from a team as a code owner October 10, 2026 10:00
HighnessAtharva added a commit to HighnessAtharva/firstrun that referenced this pull request Oct 10, 2026
…ng numbers

README gains the v1 to v2 table from neatlogs traces (2 to 3 of 4
quickstarts finish, 0 to 3 failed steps recovered, 0.0262 to 0.0200 USD
per run) and the real-world table: dbt, Entire, AccuKnox and MkDocs
verified, with dbt-labs/docs.getdbt.com#10149, #10150 and
entireio/cli#2724 open. The landing page shows the same numbers.
Evidence refreshed: graph saved about 32,939 tokens.

Entire-Checkpoint: 01M4JN70QQ1ZMYN74WRQD4R7H2
@HighnessAtharva

Copy link
Copy Markdown
Author

Public proof for this change:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant