DOCUMENTATION / Team access

Connect the team Trigger CLI

Install the client after the team approves access to its existing project.

Runs on

The team-approved Trigger project and environment

Before you start

Team approval, Node.js 22+ and a securely supplied Trigger environment key

Which key do I need?

1. 1

   Request team access first

   Ask the team administrator to approve your access to the existing project and select the intended environment. The team supplies its runtime key securely. You do not need a new Trigger project or deployment login.

   Team access requirements ↗
2. 2

   Check Node.js

   Install Node.js 22 or later first if this command is unavailable. Open a new terminal after installation.

   node --version

   Copy

   You should see A version of v22 or later.

   Get Node.js ↗
3. 3

   Install the package

   Run from any folder. No GitHub or npm login is needed. The preview includes the native executable; a repository checkout is not required.

   npm.cmd install --global @10signals/cli@preview

   Copy

   You should see npm reports that the package was added.

4. 4

   Verify the installed client

   This prints the client revision. It is different from the Trigger worker version.

   marketsignal-trigger.cmd version

   Copy

   You should see A build revision, not ‘command not found’.

5. 5

   Connect the approved environment

   Use the environment key supplied securely by the team after it approves your access. Paste it only at the hidden prompt. The client verifies it and saves it in your OS credential store. TRIGGER_SECRET_KEY in your terminal overrides that saved key. Never put a key in chat, screenshots or command arguments.

   marketsignal-trigger.cmd configure

   Copy

   You should see The key is verified and saved. No report is started.

   Team-issued runtime credentials ↗
6. 6

   Check the deployed tools

   This check makes no AI/search-provider calls. It must finish successfully. If providerConfigured is false, ask your operator to configure the research provider in Trigger before creating a report. If it stays PENDING_VERSION, your operator must promote a worker containing the Direct CLI tasks. Waiting longer is not a repair.

   marketsignal-trigger.cmd doctor

   Copy

   You should see COMPLETED, status ready, and four Direct CLI tasks. Research additionally requires providerConfigured true.

7. 7

   Create your first report

   Answer the domain, comparison count, and search-mode questions. The final confirmation starts paid research. Request IDs are automatic, and results appear in this command without a second wait command.

   marketsignal-trigger.cmd report

   Copy

   You should see A run ID, progress messages, then structured JSON with comparisons, competitors, metrics and limitations.

8. 8

   Use it from another agent

   Replace the domain placeholder. Argument mode submits immediately without the interactive confirmation. Add --close-price for the default ±30% same-currency displayed-price range. Never auto-retry a submission when its outcome is uncertain.

   marketsignal-trigger.cmd report "<your-domain>" --comparisons 20 --close-price

   Copy
9. 9

   Read an existing result

   Use the run ID printed by your report command. Retrieving does not launch new research. The Windows command displays JSON directly; the macOS/Linux command saves it. Avoid Windows PowerShell 5.1 redirection for JSON files because it changes their encoding.

   marketsignal-trigger.cmd result "<run-id>"

   Copy