Skill + Cloud onboarding

One command. One sign-in. Then ask the business question.

Install the skill in your coding agent. The first time it needs Cloud, it hands sign-in to the browser and resumes exactly where you left off.

( set -eu installer_path="$(mktemp)" trap 'rm -f "$installer_path"' 0 HUP INT TERM curl --fail --silent --show-error --proto '=https' --tlsv1.2 \ --output "$installer_path" https://soltura.ai/install.sh sh "$installer_path" )

Requires Node.js 22.12+ on arm64/x64 macOS or Linux, npm, curl, and SHA-256 tooling.

The skill stays in the terminal. Identity stays in the browser.

No API keys to paste into the agent. The skill pauses, opens a short-lived authorization request, and continues after Cloud confirms the session.

Install → authorize → continue

01 · Install and ask
(
  set -eu
  installer_path="$(mktemp)"
  trap 'rm -f "$installer_path"' 0 HUP INT TERM
  curl --fail --silent --show-error --proto '=https' --tlsv1.2 \
    --output "$installer_path" https://soltura.ai/install.sh
  sh "$installer_path"
)

✓ Soltura skill installed
✓ Coding agent: Codex
✓ Soltura CLI 0.1.10 installed

agent› Use Soltura. Can customers complete
       purchases reliably?

soltura› Secret-free doctor checks passed.
          Cloud connection required.
          Open https://soltura.ai/activate
          Enter code SLTR-M7Q4
          Waiting for authorization…
soltura.ai/activateSecure browser sign-in

Authorize this coding agent.

Match the code shown by the skill. Your repository and agent conversation stay local.

SLTRM7Q4
  • Identify your Cloud workspace
  • Create only the commitments you approve
  • Receive no source code or agent conversation
Continue to sign inCredentials stay in the browser. They never enter the coding agent.
soltura›

✓ Cloud connected. I’ll inspect only the repository scope you approve, then propose the minimum evidence for review.

03 · Resume the same session

Nothing is monitored until your change ships.

  1. LocalThe skill traces authorized code and proposes the evidence.
  2. ReviewYour team approves the instrumentation, tests, and contract.
  3. CloudAfter deployment, approved signals keep the question answered.