v1.22.0Web App
•2 min read

The docs browser terminal now matches CLI 1.8

The Interactive Shell on the docs now follows CLI 1.8. It runs the logs and projects commands, accepts the global -p, --project <id> option, and prints the same --help text as the installed CLI for every command.

In Live mode:

  • apivault projects list shows the projects on your account. apivault projects use <id>, apivault link <id>, or apivault config set project <id> sets the project that later commands go to, and apivault projects current shows it. Until you set one, commands go to the first project you joined.
  • apivault -p <id> keys list runs a single command against another project. A project you can't reach is reported as an error rather than an empty vault.
  • apivault logs lists a project's audit log with the CLI's filters, such as --status error, --source cli, --event-type KEY_REVEALED, and -n 20. apivault logs get <id> shows one entry in full.

Demo mode has a sample project and audit log, so the same commands work without signing in.

More docs examples now have a Run in shell button, including the logs filters, projects list, and projects use <id>. Examples with an <id> or <log-id> placeholder open the terminal with a list of your own projects, keys, or log entries to pick from. Examples that set up or check your own machine, such as linking a directory, still only offer Copy code.

Some things still differ from the installed CLI, because a browser has no files, credential store, or environment variables:

  • Settings are kept in the terminal itself, so --local and --global aren't available.
  • A vault key set with apivault config set vaultKey stays in the tab's memory until the page reloads. apivault config get vaultKey now only reports whether a key is set and shows its last two characters. It no longer prints the key, and apivault config list no longer includes it.
  • run, env, logs --follow, and logs tail only work in the installed CLI.

See the CLI documentation for the full command list.