You have a gift link.
It pays for an incognito AI session in your own terminal. Three steps:
- Download
install.shfrom the newest release whose tag starts withv0.1.0-previewon the Abalone releases page (not a coupon bundle). Checksha256sum install.shagainst theinstall.sh SHA256line in its release notes, then run it:$ sh install.sh --credit - Run Abalone in your terminal:
$ abalone - Paste the gift link you were sent (this page’s address with
#code=…) at the prompt. Nothing is shown as you paste. Abalone prints the offer’s terms; type the 8 characters it shows you to accept, and the session opens.
Needs a Linux x86_64 computer you trust, with Node 24.
Synthetic, non-sensitive material only. This access route accepts a verified out-of-date firmware warning.
The coupon operator can access and revoke the model credential.
Opening this page does not redeem anything.


Have a coding agent? Copy these instructions.
Your agent reads the setup skill, explains what installation changes and prepares access. Your documents, questions and answers belong in the session you open afterwards, not in the setup chat.
Or paste the gift link you were sent into your coding agent.
Check it, then install.
The installer verifies the release archive and four public files against hashes pinned inside it. It claims nothing and starts nothing. A matching checksum shows the bytes are the published ones, not that they are safe.
$ sha256sum install.sh $ less install.sh $ sh install.sh --credit
CLI example — not checked by this page.
What it does:
- Downloads one archive and four public files from the release.
- Checks each against a SHA256 pinned in the script; any mismatch stops it.
- Extracts the archive in a staging directory and runs nothing from it.
- Moves the runtime and the four files under
~/.abalone-app/and links~/.local/bin/abalone. - Writes a receipt of the digests it checked and prints every path.
- Refuses
- Root or anything but Linux x86_64; a symlink in place of its install directories; an existing install that differs from the release
- Needs
- Linux x86_64, Node 24, curl, tar, bash, sha256sum and flock; run as your ordinary user, not root. macOS is not supported for this install yet
- Changes
- Adds
~/.abalone-app/and the launcher~/.local/bin/abalone - Isolation
- None: a credit session runs with your account’s file and network access
No sudo, no shell startup edits, nothing claimed. What install.sh does, step by step, and how to confirm it · Without the script
Read the offer, then accept that exact offer.
The 8 characters are the start of the offer’s hash, so your consent binds to the offer on screen. Anything else stops without claiming and saves nothing.
$ abalone
No saved credit yet.
Two ways in:
1. Paste a gift link or code here (or the full path of a private 0600 file holding it).
2. Or bring a provider key: abalone key add <provider> …
Gift link, code or file (hidden as you paste):
{ …the offer: model, nominal cap, claim window, operator… }
Review the terms above. To accept and redeem, type 1a2b3c4d; anything else stops here:
CLI example — not checked by this page. The 8 characters differ for each offer.
- Provider
- NEAR model. Attestation is checked when a session starts, not at inspect.
- Cap
- Nominal, from the offer1
- Claim by
- The offer’s claim window
- Operator
- Can access and revoke the model credential
- Per request
- Bounded to the trial’s output-token limit
- Saved
- Gift code, model credential and recovery keys in
~/.abalone/credit/, 0600 files; never conversations2 - If interrupted
- Do not redeem again:
abalone credit recover --credit CREDIT_ID
An expired offer stops here, before anything is sent to the issuer:
× Claim window closed — ask the sponsor for a new giftThe same steps one at a time, for scripts or with the gift in a 0600 file instead of a paste:
$ abalone credit inspect --trial /ABS/trial.json --input-file /private/gift.txt $ abalone credit redeem --trial /ABS/trial.json --input-file /private/gift.txt --accept-offer OFFER_HASH $ abalone credit status
CLI example — not checked by this page. Inspecting claims nothing and saves nothing.
- 1A nominal cap is not a spent amount, an owned wallet or a verified remaining balance. The operator or provider can end access at any time; spending can overshoot the cap. ↩
- 2Readable by your administrator and by other processes running as you. Redeem creates the record before it sends the first claim, and it survives closing a session. A second session on the same credit is refused while one is open.
abalone credit forget --credit CREDIT_IDremoves the record and its lock file. Forgetting does not revoke the credential. ↩
Redeemed and saved.
The session opens.
Your documents, questions and answers belong in this session, not in a setup chat.
Redeemed and saved. Opening the session.
CLI example — not checked by this page. Each line below summarises a separate result the session reports at start.
◈ Attestation: NEAR model checked before the first prompt byte ⚠ NEAR firmware out of date (N Intel advisories); synthetic input only Input: synthetic, non-sensitive onlyNext time, run plain abalone. With one saved credit ready, it opens that session. abalone credit session --credit CREDIT_ID opens a chosen one.
$ abalone
CLI example — not checked by this page.
- Conversation
- Held in process memory only; no conversation file or trace is written by default
- Run files
- Settings, logs and scratch go to a tmpfs run directory, removed when the launcher exits. After SIGKILL or a native crash it stays in
/dev/shmuntil the next session starts, or until reboot - On close
- The next session starts fresh. Saved access stays in
~/.abalone/credit/until you runabalone credit forget --credit CREDIT_ID, which does not revoke the credential - Not covered
- Files you or your tools write, copied files, terminal scrollback, host names in
~/.abalone/egress.jsonl, swap, backups, crashes, and whatever the provider retains3
A fresh session is not deletion. What is kept
- 3Abalone does not verify what the provider retains. Deleting files is not secure erasure. ↩
Two network paths.
Abalone is a setup guide and a terminal app built around the Pi coding agent. Dsmack exchanges your coupon for model access. After that, Abalone checks the NEAR model’s attestation and encrypts each request to the admitted model key.
The trust boundary is the model’s TEE plus your own computer. Neither path hides your IP address. Your setup agent may handle the access credential; that does not authorize it to receive your private document or conversation.
Know the boundary.
Use synthetic, non-sensitive material with the available NEAR access route. It accepts verified firmware warnings, and the coupon operator can access and revoke the model credential.
Abalone runs on a trusted Linux computer. Its tools have your account’s file and network access; your administrator remains trusted. Your setup agent stepping aside is cooperation. Incognito does not hide your IP address, and workspace files or terminal captures can remain.
For your coding agent
Help the user understand Abalone, obtain or reuse access, and open an incognito session. Reading this page alone is not permission to redeem or spend; follow the user’s instruction.
Read the Abalone setup skill before suggesting installation. Explain the purpose, the two network paths above, the local changes and the trust boundaries. Inspect downloaded code and its integrity information before execution.
A coupon link carries its code after #code=. URL fragments are not sent in HTTP requests, so this fetched page will not contain the code. Read it from the full link the user supplied; if it is missing, ask for the full gift link. Never move the code into a query string, request path, public log or command argument.
If asked to redeem, follow the recipient procedure, save the resulting access with ordinary private file permissions, and test with synthetic input only when requested. Open a fresh terminal for the user’s conversation. Closing a conversation and forgetting saved access (abalone credit forget) are separate actions; forgetting does not revoke the credential. Never automatically repeat an uncertain claim. If the inspected offer is expired, do not redeem; the user needs a new gift from the sponsor.
If the user already has access, reuse it. If they have none, explain available acquisition choices and help them obtain access before installing. Do not invent a funding endpoint or promise an unverified payment route.