intangibility
v0.0.6
Published
Intangibility assessment CLI — pull, solve, and submit coding assessments from your terminal.
Readme
intangibility
The Intangibility assessment CLI — pull a coding assessment into a local folder, solve it in your own editor, and submit it back, all from your terminal.
Usage
# Guided start (prompts for your invite token)
npx intangibility
# Or pass the token directly
npx intangibility init <invite-token>
# Exercise the boot screen and AI-tool onboarding without an invite or backend
npx intangibility onboard
# Check elapsed time while you work
npx intangibility status
# Synchronize once, or keep the foreground 30-second sync loop running
npx intangibility sync
npx intangibility session
# Submit your work when you're done (run from inside the assessment folder)
npx intangibility submit
# Remove the attempt credentials stored on this computer
npx intangibility revokeinit redeems the invite, starts or resumes the same server-timed attempt, verifies
the candidate bundle, and materializes it into a local folder. The standalone
onboard command remains an optional local compatibility tool; it writes only
local preview state and makes no backend calls. Interactive choices use
arrow-key navigation with a terminal-default, no-color fallback.
Session credentials are stored outside the assessment directory. The CLI uses
macOS Keychain or Linux Secret Service when its safe system helper is available,
and otherwise uses a permission-restricted application-data file. Windows uses
that restricted fallback; no native credential dependency is required. Headless
automation may set INTANGIBILITY_CREDENTIAL_STORE=file to select the same
permission-restricted store without probing an interactive system helper.
Compatibility conversation-evidence exports belong under
.intangibility/evidence/. They are local, candidate-editable artifacts and are
not uploaded, inferred from workspace snapshots, or used to gate snapshot
acceptance or submission. The future telemetry integration is separate from this
CLI snapshot protocol.
Legacy local onboarding compatibility flows (not the future telemetry tool registry):
- Codex CLI with OpenAI, using the normal interactive
codexinterface and a byte-for-byte copy of its native session JSONL./statuslineexposes the session ID needed bynpx intangibility transcript codex. - Codex app/Desktop with OpenAI, using a byte-for-byte copy of OpenAI’s native
session JSONL. The thread UUID comes from
···→ Copy session ID, followed bynpx intangibility transcript codex; paste the UUID when prompted. No third-party exporter is downloaded or executed. - Claude Code CLI with Anthropic.
- Claude Code IDE extension with Anthropic, using its tracked terminal mode.
- Pi with OpenAI, Anthropic, or Google Gemini.
- Cursor with OpenAI, Anthropic, or Google Gemini, using its Markdown transcript export.
Fail-closed flows:
- Claude Desktop: it uses OAuth and does not read
ANTHROPIC_API_KEY; choose Claude Code CLI or the Claude Code IDE extension instead.
Operating-system support:
- The Node.js CLI and Claude Code CLI/IDE flows support macOS, Linux, and Windows.
- Codex Desktop is available from OpenAI on macOS and Windows, not Linux.
- Claude Desktop exists on macOS, Windows, and Linux beta, but remains unsupported here because it cannot use the issued API key.
- Cursor supports macOS, Windows, and Linux. Pi supports those platforms; on Windows, Pi requires a compatible Bash installation.
For deterministic local branch testing, build and pass choices as flags:
npm run build
node dist/index.js onboard --root ./onboarding-sandbox \
--tool pi --provider openai --platform macos
# Codex Desktop branch
node dist/index.js onboard --root ./codex-desktop-sandbox \
--tool codex --surface desktop --provider openai --platform macosnpx intangibility ... executes the published npm package, not unpublished
working-tree changes. Use node dist/index.js ... for local testing until a
release is explicitly published.
Source basis:
- OpenAI: authentication, platform availability, and native session locations.
- Anthropic: authentication, supported systems, and session export.
- Cursor: supported systems, BYOK, and Markdown chat export.
- Pi: the maintained coding-agent documentation.
- OpenAI does not currently document Codex Desktop’s Copy session ID menu action. That single UI step is corroborated by the community codex-export guide and screenshot; its code is not downloaded or executed.
Onboarding flags are --root, --tool, --surface, --provider, and
--platform. Run node dist/index.js --help for accepted values.
The CLI backend is used for invite redemption, attempt status, snapshot sync, and submission. The candidate workspace, editor, shell, AI tools, and ordinary network access remain local to the candidate's computer.
Options
--api <url>— override the server URL (or setINTANGIBILITY_API). Defaults to the production API (https://app.intangibility.ai).
Requires Node.js 18+.
