9 episodesq-ring 101
Nine short episodes, one q-ring command each: store, scope, inject, rotate, expire, move, import, audit, and govern secrets from your terminal.
Walkthroughs, tutorials and trailers for the I4C Studio products. Every video comes with a full transcript and a written guide with commands you can copy, so you can read instead of watch.
Videos and transcripts are in English.
9 episodesNine short episodes, one q-ring command each: store, scope, inject, rotate, expire, move, import, audit, and govern secrets from your terminal.
1:04q-ring keeps API keys in your OS keychain instead of a .env file and hands them to AI coding agents over MCP, with policy, redaction, and an audit log.
0:34Move an API key out of .env and into the OS keychain with qring set, then list what you stored by name without ever printing a value.
0:38One key name, separate values for dev, staging, and prod. q-ring resolves the right one per context, and qring inspect shows states without values.
0:32qring exec injects secrets into a command's environment and replaces every known value in its output with [QRING:REDACTED] before logs see it.
0:32Link secrets with qring entangle so a new value written to one reaches its partners, even across projects. One rotation instead of a hunt.
0:34Give a secret a lifetime with qring set --ttl. Stale at 75 percent, unreadable once expired, so forgotten tokens stop working on schedule.
0:33Pack secrets into one AES-256-GCM bundle with qring teleport, send it any way you like, and unpack it into the keychain on the new machine.
0:28qring import moves every variable in a .env file into the OS keychain in one command, so you can delete the file and keep the same key names.
0:35q-ring logs every read, write, and delete in a hash-chained audit log. qring audit shows who read what; audit:verify proves nobody rewrote it.
0:33A .q-ring.json policy sets which tools, keys, and commands AI agents may use over MCP, and sensitive reads wait for an expiring human approval.