Google Analytics, Vercel Web Analytics, Leadsy, the Ship or Die traffic check, the TikTok Pixel, the OpenAI Ads Measurement Pixel and Behavly stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.Google Analytics, Vercel Web Analytics, Leadsy, the Ship or Die traffic check, the TikTok Pixel, the Meta Pixel, Google Ads, the LinkedIn Insight Tag, Microsoft Advertising, the OpenAI Ads Measurement Pixel and Behavly stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.
Connect Entire for the Coder: how to copy your token from the Entire command line, where to paste it, how the Coder clones and pushes, and how to fix the usual errors.
Connect Entire and the Coder works on your Entire repositories the way it works on GitHub: it copies a repository into its own workspace, makes the change, and pushes it to a branch of its own for you to review.
Checkpoint
Entire connects on stellarfirm.ai, under Integrations. It is not in the desktop app yet.
The token comes from the Entire command line on your own computer.
Install the Entire command line, then run entire login and sign in.
Copy the token straight to your clipboard:
bash
entire auth token | tr -d '\n' | pbcopy
On Linux, use xclip -selection clipboard in place of pbcopy.
Tip
Copy it with that command, not by selecting the text in your terminal. The token is one long line, and a terminal that wraps it can add line breaks when you copy it by hand. A token with a line break in it is refused by Entire.
The token works for everything your Entire account can reach, and it lasts a few hours. When it runs out, the Coder's next clone or push stops with a sign-in error: copy a new one the same way and paste it again.
Make sure Use live Entire is on, then press Connect (or Save changes if a token was saved before).
The switch reads Your assistants use this integration. Your token is stored encrypted in StellarFirm cloud, is never shown back to you, and is handed to one git command at a time.
The Coder needs the repository's Entire clone address. To see it, run entire repo clone /et/<project>/<repository> on your computer, or copy it from the repository's page on Entire. It looks like this:
Coder, Entire is connected. Clone https://<region>.entire.io/et/<project>/<repository>.git, create the branch stellarfirm/coder/entire-test, add one empty commit, and push only that branch. Change no files.
When that branch shows up on Entire, the connection works end to end.
Your house rules still apply. Pushing the Coder's own branch runs on its own. A merge, a deploy, a delete, and anything that spends money wait for your Approve. See house rules.
One command at a time. StellarFirm hands the token to a git command only when the command is git and nothing else: no pipes, scripts, or other programs on the same line. A command like git clone ... | tail runs without it and fails to sign in.
Switch it off at any time. Turn off Use live Entire to pause it, or choose Turn off to remove the token. Signing out of the Entire command line on your computer does not remove the copy saved in StellarFirm.
Coder, Entire is connected. In https://<region>.entire.io/et/<project>/<repository>.git, [describe the change], and push it to a new stellarfirm/coder/ branch for review.
PromptExplain a repository
Coder, clone https://<region>.entire.io/et/<project>/<repository>.git and give me a short tour: what it does, how it is laid out, and how to run its tests.