Install the plugins

Install the NomosX plugins

On your phone? Follow this guide on your computer. Send this page to yours & open it there.

NomosX shows one sponsored result, always labeled "Sponsored", next to your assistant's answer when you are choosing a product or service, and in Claude Code a line in the status line. You earn 60% of each one's placement value and never have to click or buy anything.

Last updated November 10 2026

One command installs NomosX for the AI coding apps on your machine: Claude Code (with Claude Desktop), Antigravity CLI and Codex CLI. Re-running it is the update.

curl -fsSL https://nomosx.io/install.sh | sh

On Windows, in PowerShell:

irm https://nomosx.io/install.ps1 | iex

The installer verifies the release's signature and checksum before it changes anything, and everything it downloads comes from nomosx.io. The script is short; read it at https://nomosx.io/install.sh (or https://nomosx.io/install.ps1) first if you like.

No terminal apps? Add NomosX to Claude Cowork and Add NomosX to ChatGPT need no install.

Requirements

  • macOS, Linux, or Windows 10 or newer.
  • curl, tar and node 20 or newer (Windows 10 and 11 ship curl and tar). Checking for an update and uninstalling also work with an older node.
  • At least one of Claude Code (claude), Antigravity CLI (agy) or Codex CLI (codex). Claude Desktop is added along with Claude Code when it is installed.
  • On Windows, Git for Windows (opens in a new tab): Claude Code runs its hooks and status line through Git Bash there, and the NomosX plugin needs both.

On Windows

Everything in this guide reads the same on Windows, with the PowerShell commands in place of the curl ones. Options go after the script, in this form:

& ([scriptblock]::Create((irm https://nomosx.io/install.ps1))) codex --signin

and uninstalling is irm https://nomosx.io/uninstall.ps1 | iex (options the same way, such as --purge). The environment variables work as they do elsewhere ($env:NOMOSX_SURFACES = "claude,codex" before the command). The installer asks its questions on the console you ran it from. Claude Code installed with npm comes with a claude.cmd launcher; the installer runs the program behind it, so either Claude Code install works. Windows Subsystem for Linux works too, with the curl commands, for the apps installed inside it.

Let your AI agent install it

Paste this into Claude Code, Codex or Antigravity:

Install NomosX for me: run `curl -fsSL https://nomosx.io/install.sh | sh -s -- --all --yes --signin`

An agent's shell has no terminal to ask questions on, so the installer adds NomosX to every supported app it finds. --signin opens the sign-in in your browser and waits up to five minutes; if the agent stops the command first, the install is already done, and you sign in later with /nomosx:signin (in Codex: $nomosx-signin).

Choosing apps

With one supported app found, NomosX is added to it. With several, at a terminal, a picker asks which: an All surfaces row above one row per app, everything selected; arrows move, space picks, enter confirms. A terminal that cannot draw the picker shows a numbered menu instead: answer with numbers (1 3), names (claude codex), all or none, or press enter for all.

Your choice is remembered, so a bare re-run updates the same apps. Naming an app adds it to the remembered set; --reset forgets the set and asks again; none downloads NomosX and adds it to nothing. Narrowing the set never removes NomosX from an app (uninstall it by name for that). With no terminal, such as an agent's shell or CI, the installer uses the remembered choice, or else every supported app it finds.

When several of these name the apps, the first wins: app names you type, then --all, then NOMOSX_SURFACES, then the remembered choice, then detection.

Signing in, and the program

Until you sign in, nothing calls NomosX. At a terminal the installer offers to sign you in once NomosX is added to your apps; say no, or pass --no-signin, and nothing is transmitted. Runs with --yes, in CI or with no terminal never sign you in on their own (add --signin), and neither does the update command inside your apps. Sign in later from any app:

/nomosx:signin          # Claude Code and Antigravity CLI
$nomosx-signin          # Codex CLI

Sign-in opens your browser (Google, GitHub, a passkey, or email and password; you must be 18 or older) and prints the address in case no browser opens. It gives up after five minutes (NOMOSX_SIGNIN_TIMEOUT_MS changes the wait). One sign-in covers every app on this machine, including the commerce tool, the tool your assistant calls for a sponsored result. Sign in before you open an app session, or start a new session afterwards.

One program, one switch. Sponsored results, your earnings and the personalization that matches results to you start together when you create an account and sign in; none is offered without the others. The toggle at https://console.nomosx.io/account (opens in a new tab) turns the whole program off, on every machine, and back on. Set up payouts on that page so you can be paid.

Check that it works

Start a new session (in Antigravity, restart agy) and ask about something you are choosing, such as "what should I use for error tracking in a new Node service?". When a relevant sponsored option exists, your assistant shows one result labeled "Sponsored"; most answers show nothing sponsored, which is normal. The status command, /nomosx:status (Codex: $nomosx-status), says whether you are signed in and whether the program is on.

Installer options

Options go after sh -s --. For example, Codex only, signing in during the install:

curl -fsSL https://nomosx.io/install.sh | sh -s -- codex --signin
OptionWhat it does
claudeClaude Code, and Claude Desktop when it is installed
antigravity (or agy)Antigravity CLI; its desktop app and IDE share it
codexCodex CLI; the ChatGPT desktop app and the Codex IDE extension share it
noneDownload and verify NomosX, and add it to nothing (remembered)
--all (or all)Every supported app found, no question
--yes (or -y)Never ask: the remembered choice, else every app found. Skips the sign-in offer and the waitline unless you add --signin
--resetForget the remembered choice and choose again
--version <version>Install exactly that version, one of the recent releases; also how you roll back
--checkCompare installed with latest and change nothing. Exit 0 when current, 2 when an update is available or nothing is installed, 1 when the release check fails
--signinSign in as part of installing, even with no terminal; on Claude Code it also adds the waitline
--no-signinNever offer sign-in, never add the waitline
--from <file>Used by the update command inside your apps to apply an update already downloaded and verified; you do not type it
--verbose (or -v)Every detail as it happens, instead of the short checklist
--help (or -h)Every option

--check, --help and --from use the installer already on your machine when there is one. Environment variables: NOMOSX_SURFACES (the apps, comma or space separated), NOMOSX_YES=1, NOMOSX_SIGNIN=1 or NOMOSX_SIGNIN=0, NOMOSX_VERBOSE=1, NOMOSX_PROGRESS=0 (plain lines instead of the live checklist), NOMOSX_SIGNIN_TIMEOUT_MS, and CI or NO_COLOR as usual:

curl -fsSL https://nomosx.io/install.sh | NOMOSX_SURFACES="claude,codex" sh

What NomosX adds to each app

Claude Code

The nomosx plugin: the /nomosx:* commands, the commerce tool (run without asking each time while the program is on), and quiet background hooks that read your account's switch at most once a day and, while the program is on, check for updates, check each prompt on your machine for a product decision (nothing is sent for that), keep the waitline fresh and run the wiki builder when a turn ends. The installer switches the plugin on, and every run switches it back on; to keep it off, run claude plugin disable nomosx@nomosx after each install or update, or uninstall from Claude Code. Open a new session, or run /reload-plugins (in Claude Code's VS Code extension, reload the window).

The waitline is NomosX's place in Claude Code's status line: one line labeled "Sponsored", shown with your model name and, while it is live, as the thinking verb and among the tips. Only a line the status line actually draws earns anything. /nomosx:install adds it; the install command adds it too, without asking, whenever it runs at a terminal (or with --signin) while you are signed in and it is missing, updates included. To leave it out, run with --no-signin (or NOMOSX_SIGNIN=0). Your own status line, thinking verbs and tips are backed up and put back exactly when you turn NomosX off here or uninstall.

Claude Desktop

Added with Claude Code when it is installed: the commerce tool, as a local connection that uses your sign-in. Nothing else in its settings changes, and the uninstaller removes the entry again (Claude Desktop goes with Claude Code; there is no option for it alone). Quit Claude Desktop fully (Cmd+Q) and open it again. For claude.ai, Cowork and the mobile app, add NomosX to your Claude account instead: Add NomosX to Claude Cowork.

Antigravity CLI

The NomosX plugin, shared with the Antigravity desktop app and IDE: the /nomosx:* commands, the commerce tool (approved ahead of time, so it does not stop at "Allow using this MCP tool?") and the same hooks as Claude Code's. Nothing else in your settings changes. Restart agy.

Codex CLI

The commerce tool (no approval prompt, no codex mcp login), the $nomosx-* skills (they run only when you name them: type $ and the name, or pick from /skills), a short set of instructions on when to call the tool and how to show its result, and a background task on each turn that reads your account's switch at most once a day and checks for updates. If you already run a notification program of your own in Codex, NomosX leaves it alone and adds no task; a Codex-only machine then has no background checks, so run $nomosx-update and $nomosx-status yourself now and then. Codex has no waitline. The ChatGPT desktop app and the Codex IDE extension share Codex's settings, so they get the tool too (CODEX_HOME is honored). Start a new Codex session.

Everyday commands

WhatClaude CodeAntigravity CLICodex CLI
Sign in/nomosx:signin/nomosx:signin$nomosx-signin
Earnings: all time, today, pending, verified/nomosx:earnings/nomosx:earnings$nomosx-earnings
Status: what is showing, sign-in, the program, a waiting update/nomosx:status/nomosx:status$nomosx-status
What personalization would send/nomosx:signals/nomosx:signals$nomosx-signals
Update NomosX/nomosx:update/nomosx:update$nomosx-update
Turn NomosX off on this machine only/nomosx:off/nomosx:off$nomosx-off
Turn it back on here/nomosx:install/nomosx:on$nomosx-on
Add the waitline/nomosx:install--
Sign out (this machine, every app)/nomosx:signout--

Antigravity and Codex have no sign-out command: use /nomosx:signout in Claude Code, or the off command on a machine without it. Claude Desktop, Cowork, claude.ai, the Claude mobile app and the ChatGPT desktop app have no NomosX commands; your account page covers them.

What leaves your machine

Section 3 of the Privacy Policy is the precise version; this is the short one.

Your conversations never reach NomosX. The wiki builder reads the prompts you typed from the transcripts your assistants keep on this machine, only from an assistant NomosX is installed and enabled in (Claude Code; Codex and the apps that share its sessions, such as the ChatGPT desktop app and the Codex IDE extension; Antigravity's CLI, desktop app and IDE). It runs at most once a day while the program is on and writes a local profile wiki with your own Claude Code or Antigravity CLI, on your own subscription. Those excerpts go to your model provider through that CLI, as your sessions already do; NomosX never receives them. Codex has no wiki builder of its own.

While the program is on, this leaves your machine, tied to your account: interest categories with weights, and the names of vendors you turned down; for the status line, the short name and category of your newest open need, never page text; the short query your assistant writes when it calls the commerce tool, with its category (filtered and cut to 500 characters on arrival); the events that credit your earnings; and a filtered copy of your wiki, in which keys, tokens, email addresses, long numbers, IP addresses and local paths are replaced and links to your own machine keep only their host. Every request names the app and NomosX version. A click on a sponsored link passes through https://api.nomosx.io/go/<click id> on its way to the advertiser. /nomosx:signals (Codex: $nomosx-signals) shows what personalization would send.

While the program is off, nothing is served, earned, personalized or sent; a signed-in machine only reads your account's switch, at most once a day. Signed out, or after the off command, a machine makes no calls of its own.

Erasing your data. "Erase my synced data", in the Close your account card at https://console.nomosx.io/account (opens in a new tab), deletes the synced copy of your wiki at any time; closing your account erases it too. Once your account has been opted out for 90 days, NomosX anonymizes your data.

Updating

Re-run the install command, then reload or restart each app. Or from inside the app:

AppUpdateThen
Claude Code/nomosx:update/reload-plugins, or restart Claude Code
Antigravity CLI/nomosx:updaterestart agy
Codex CLI$nomosx-updatethe next session

Desktop apps pick up a new version when they restart. An update keeps your sign-in and wiki, never turns the program on when your account has it off and never undoes the off command. Like any installer run, it switches the Claude Code plugin back on, and at a terminal it adds the waitline when you are signed in and it is missing.

In the background, while you are signed in and the program is on, NomosX checks for a new version as you use your apps (a quick check at most once a day, and a check of the signed release every six to seven hours) and may download and verify it ahead of time, so the update command is instant. Nothing is installed until you run the update command, unless you set NOMOSX_AUTOUPDATE=1. With the waitline in place the status line then shows

NomosX update: /nomosx:update

and the status command reports the version and its release notes in every app. NOMOSX_NO_UPDATE_CHECK=1 stops the checks and the daily account read; DISABLE_AUTOUPDATER or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, Claude Code's own settings, stop the background download.

When an update is required, nothing is served or earned until you update. Claude Code's thinking verb goes back to your own and the status line shows your model name and

NomosX: update required · /nomosx:update

The commerce tool answers in plain text: "NomosX needs an update before it can show results: run curl -fsSL https://nomosx.io/install.sh | sh".

Pinning and rollback. Compare the installed version with the latest:

curl -fsSL https://nomosx.io/install.sh | sh -s -- --check

It prints a line such as

[nomosx] installed: <installed>; latest: <latest> - update available: curl -fsSL https://nomosx.io/install.sh | sh

To install exactly one version, which is also how you roll back:

curl -fsSL https://nomosx.io/install.sh | sh -s -- --version <version>

The 20 most recent releases are available this way. If the newest release is still rolling out, the installer keeps this machine on the previous one for now (--version takes it early); if a release has been withdrawn, it installs the previous one instead.

The integrity self-check

Each time a NomosX command, hook or the commerce tool runs, NomosX first checks that none of its own files was changed or deleted. If one was, it stops working in that app and prints:

[nomosx] disabled: this installation failed its integrity check (modified: <file>).
[nomosx] files were changed or deleted after install; re-install to repair: curl -fsSL https://nomosx.io/install.sh | sh

Re-running the install command repairs it. Home folders synced between machines (iCloud, Dropbox) can trip the check on every machine at once. Uninstalling always works.

Turning it off, and uninstalling

Everywhere: the toggle at https://console.nomosx.io/account (opens in a new tab). Off means nothing is served, earned, personalized or sent. A signed-in machine follows within a day as you use your apps, or at once when you run the status command there; an opt-out can reach it sooner, because a refused request switches the machine off at once.

In the chat and desktop apps: Claude Desktop, Cowork, claude.ai, the Claude mobile app and the ChatGPT desktop app have no NomosX command. The toggle covers them. To take NomosX out of those apps and keep the program on, remove the connector: one you added yourself comes out in the app's settings (see Add NomosX to Claude Cowork and Add NomosX to ChatGPT); entries the installer added come out with the uninstaller.

On this machine only: the off command, /nomosx:off in Claude Code and Antigravity, $nomosx-off in Codex. It turns NomosX off in every app on this machine, makes no call and leaves your account alone. It takes the waitline out of Claude Code, putting your own status line, thinking verbs and tips back exactly, and stops personalization, the wiki sync and Claude Code's automatic approval of the commerce tool. In Claude Code with the waitline in place it prints:

NomosX is off on this machine and the waitline is out of your Claude Code settings: nothing is served, earned, personalized or sent from here. Your account is unchanged; the toggle at https://console.nomosx.io/account turns NomosX off everywhere. /nomosx:install turns it back on here.

The machine stays off, through sign-ins, installer re-runs and a turn-on in your account, until a turn-on command in any app here: /nomosx:install in Claude Code (which also adds the waitline), /nomosx:on in Antigravity, $nomosx-on in Codex. They read your account and never change it: with the account opted out they refuse and point at the toggle. Then start a new session. There is no command that removes only the waitline: taking the status line out by hand stops only the status line, and a terminal re-run of the install command puts it back.

Uninstalling:

curl -fsSL https://nomosx.io/uninstall.sh | sh

It removes everything it added to each app, puts your own Claude Code status line, thinking verbs and tips back exactly, and deletes NomosX's own files from ~/.nomosx. It keeps your sign-in, whether the program is on or off on this machine, your local profile wiki and the backup of your Claude Code settings, so a later re-install picks up where you left off; uninstalling is not opting out. To be gone rather than uninstalled, turn the program off with the toggle first, then uninstall with --purge, which deletes the whole ~/.nomosx folder (at a terminal, it asks first). Reload your AI sessions or restart your desktop apps to finish. To remove NomosX from some apps only, name them:

curl -fsSL https://nomosx.io/uninstall.sh | sh -s -- antigravity
Uninstall optionWhat it does
claude, antigravity (or agy), codexRemove NomosX from just these apps. claude covers Claude Desktop too
--all (or all)Remove it from Claude Code, Antigravity and Codex, whatever the installer recorded. Add it if you ever narrowed your app choice with --reset or none
--purgeAlso delete the whole ~/.nomosx folder (asks first at a terminal). Skipped while another app still has NomosX
--yes (or -y)Do not ask before --purge; also NOMOSX_YES=1
--verbose (or -v)Every detail, including what was kept; also NOMOSX_VERBOSE=1
--help (or -h)Every option

Troubleshooting

No supported app found

[nomosx] WARNING: no supported CLI found (claude/agy/codex) - nothing was wired

NomosX was downloaded but added to nothing. Install Claude Code, Antigravity CLI or Codex CLI and run the installer again, naming the app (curl -fsSL https://nomosx.io/install.sh | sh -s -- claude); to remove the download instead, run the uninstaller. If you use only Claude Desktop, claude.ai or the ChatGPT desktop app, use the Cowork or ChatGPT guide instead. If you name Claude Code and the claude command is missing, the installer skips it:

skip claude: 'claude' CLI not found (install Claude Code, then re-run: curl -fsSL https://nomosx.io/install.sh | sh -s -- claude)

Claude Code says the plugin is disabled

Claude Code: the plugin is installed but disabled - enable it with: claude plugin enable nomosx@nomosx

Run that command, then /reload-plugins or start a new session.

"disabled: this installation failed its integrity check"

Re-run the install command (see "The integrity self-check"). If the Claude Code status line stops showing sponsored lines, the part that draws it was edited: /nomosx:install repairs that; a re-install alone does not.

"another NomosX install is running"

[nomosx] ERROR: another NomosX install is running (lock: <folder>). Wait for it to finish, or remove that directory if no installer is running.

Wait for the first run to finish. If none is running (the machine was switched off mid-install), remove the folder it names and run the install again.

The installer refuses the release

It stops when the release is UNSIGNED, is signed with a key this installer does not trust, predates signed release digests, is older than one this machine already installed (refusing what looks like a replayed pointer), or when the installer package does not match its signed checksum. Nothing on your machine changed. Run the install command again, which fetches everything fresh; if it keeps happening, tell us (below). A release that is not reachable, or a failed download, is a network problem: check your connection and proxy.

Nothing is appearing

Run the status command (/nomosx:status, in Codex $nomosx-status); your assistant sums it up, and you can ask for the full output. In order: are you signed in, and is the waitline in place (installed is false where only Antigravity or Codex has NomosX, or where you left it out)? Did the app reload (below)? Is the program on (account; after the off command the status shows offHere, and a turn-on command in any app here turns it back on)? Is there simply nothing to show (an empty slot is the normal case; the status line's line is fetched at most every 10 minutes, only on a Claude Code prompt, and dropped after 30 minutes)? Is this version blocked (update says so; see "When an update is required")?

An app does not show NomosX

Every app reads its setup when it starts. Claude Code: a new session, /reload-plugins, or a restart; in its VS Code extension, run Developer: Reload Window from the Command Palette and start a new conversation. Antigravity CLI: restart agy. Codex CLI: a new session. Claude Desktop and other desktop apps: quit fully (Cmd+Q on macOS) and open them again. If you signed in while an app was open, start a new session there.

Claude Desktop does not have NomosX

Quit it fully and open it again. If it is still missing, run the install command with --verbose (curl -fsSL https://nomosx.io/install.sh | sh -s -- --verbose). This line means Claude Desktop's configuration file is not valid JSON, usually after a hand edit; NomosX never overwrites a file it cannot read:

[nomosx] claude desktop: skipped (see docs/install-plugins.md)

Open it from Claude Desktop (Settings, Developer, Edit Config), fix it, and run the install command again.

Antigravity asks "Allow using this MCP tool?"

One of Antigravity's settings files is not valid JSON, so the installer left it alone. Allow the tool once, or fix the file and run the install command again; with --verbose the installer names it:

[nomosx] <file> is not valid JSON - leaving it alone (the tool will Ask in <app> until you allow it once)

Seeing more detail

Add --verbose (or NOMOSX_VERBOSE=1) to print every step. If an install fails after the download starts, a Details: line names a file with the full account of the run. The background hooks print nothing, on purpose; the status command shows the state they would have reported.

Still stuck? Use the contact form with the command you ran and what it printed.


Terms of Service · Privacy Policy

Other surfaces

Need help?

Email hello@nomosx.io or use the contact form.

Buying the moment of decision?Advertisers