Skip to main content
Myrqen is two things on your machine: the myrqen CLI, which owns session state, policy gates, finding intake, and reports; and a portable Agent Skill, which is the behavioural source of truth your coding agent reads.

​
Requirements

​
Build the CLI

The myrqen npm package is not published yet — apps/cli/package.json still carries "private": true, and registry.npmjs.org/myrqen returns 404. Any documentation or marketing copy showing npx myrqen link is describing a future state. Build from source until that changes.
pnpm build produces a single bundled entry point:

​
Make myrqen runnable

Quick, per-shell, and easy to undo.
An alias is not visible to a subprocess, so an agent that shells out may not see it. Prefer one of the other options when an agent will be driving the CLI.
Confirm what the CLI thinks it can do:
doctor reports capability, not alarm. A missing convenience integration is info; attention is reserved for something that actually blocks the product.

​
Install the Agent Skill

packages/skill/myrqen is the single behavioural source of truth. myrqen install (and myrqen link) copies that same bundle to the locations each agent actually reads: Notes that matter in practice:
  • Claude Code derives the slash command from the directory name, so the bundle installs as myrqen/ and is invoked as /myrqen auto. The frontmatter name is only the display label, and $ARGUMENTS carries the requested effort.
  • OpenCode also reads .claude/skills and .agents/skills, so one install can satisfy several agents. The installer deduplicates by destination path.
  • Codex has no slash-command mechanism, so the universal myrqen auto invocation is the documented path there.
  • A directory Myrqen manages carries a .myrqen-managed.json marker with the bundle version and a content digest, so a reinstall is a no-op when nothing changed. An existing directory Myrqen did not write is moved to myrqen.backup-<timestamp> first.
Find the source bundle at any time:
A missing convenience integration does not mean the scanner is broken. The universal myrqen <effort> invocation works from any agent with shell access.

​
Where local state lives

Two locations, and nothing outside them. Per machine — configuration and the device credential: config.json holds the API base URL, the linked account, update preferences, and the telemetry flag. The device token itself goes to the OS keystore — Keychain, Windows Credential Manager, or Secret Service — and falls back to a 0600 file only when no keystore is available. Per scanned repository — session and report state, under .myrqen/:
The repository’s own .gitignore already excludes .myrqen/local.json, .myrqen/reports/, .myrqen/sessions/, and .myrqen/current-session. Add the same lines to the project you are scanning. Override the config directory with MYRQEN_CONFIG_DIR — useful for keeping an experiment away from your real credential. See Environment variables.

​
Next

Link a device

Only needed for cloud reports and sharing. Scanning works unlinked.

Run your first assessment

What session start hands your agent, and what to do with it.