@lazehq/cli 0.1.130 → 0.1.131

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/laze.mjs +40 -1
  2. package/package.json +1 -1
package/dist/laze.mjs CHANGED
@@ -36960,7 +36960,7 @@ function shadowedLinkLineOf({ shadow }) {
36960
36960
  }
36961
36961
 
36962
36962
  // src/rules/cli-version.rules.ts
36963
- var STAMPED = "0.1.130";
36963
+ var STAMPED = "0.1.131";
36964
36964
  function cliVersionOf({ stamped = STAMPED } = {}) {
36965
36965
  return stamped.startsWith("__") ? "dev" : stamped;
36966
36966
  }
@@ -62716,6 +62716,25 @@ var vaultSecretOfferedSchemaDefinition = external_exports.object({
62716
62716
  state: external_exports.enum(["pending", "denied", "expired"])
62717
62717
  });
62718
62718
 
62719
+ // ../../modules/vault/contract/src/vault-agent-setup.ts
62720
+ var VAULT_CLI_INSTALL = "npm i -g @lazehq/cli";
62721
+ var VAULT_CLI_LOGIN = "laze login";
62722
+ var VAULT_AGENT_PROMPT = `I keep my API keys and passwords in the Laze vault. Use them through the laze CLI, which is signed in as me. I approve uses on my phone or computer, so a command may wait for me.
62723
+
62724
+ If \`laze\` is missing, run \`${VAULT_CLI_INSTALL}\`, then ask me to run \`${VAULT_CLI_LOGIN}\`.
62725
+
62726
+ Commands:
62727
+ - \`laze vault list\` shows the keys you may use: names, fields and levels, never values.
62728
+ - \`laze vault run <name> --reason "<one plain sentence>" -- <command>\` runs the command with the key's fields as environment variables. To put a value in an argument, let a shell expand it inside the run, for example: \`laze vault run openai --reason "List the models our account can use" -- sh -c 'curl -s https://api.openai.com/v1/models -H "Authorization: Bearer $OPENAI_API_KEY"'\`
62729
+ - \`laze vault env --reason "<one plain sentence>" -- <command>\` runs the command with every key a \`.env.vault\` file names, in this folder or a parent. One line per variable: \`KEY\` (the key that holds that field), \`KEY={{vault:<name>}}\`, or a key's name for all its fields. \`--env <x>\` reads \`.env.<x>.vault\` instead. \`laze vault env --names\` shows what each line resolves to, never a value.
62730
+ - \`laze vault aws <name> --reason "<one plain sentence>" -- <aws command>\` runs the command with a short-lived AWS session made from that key.
62731
+
62732
+ Rules:
62733
+ - The reason is one short sentence I can read on my phone: what you want to do and why. Never a command.
62734
+ - A run may wait until I answer its approval card. Let it wait and do not start it again. Exit 75: the wait ran out, run it again. Exit 77: I denied it, so stop and ask me. Exit 2: rewrite the reason.
62735
+ - Never print, echo or log a value. Never write one into a file, a commit, a message or your notes.
62736
+ - If no key fits, tell me the name and fields you need. Never ask me to paste a secret into the chat.`;
62737
+
62719
62738
  // ../../modules/chat/contract/src/chat.close.ts
62720
62739
  var conversationOpenDaysSchemaDefinition = external_exports.union([external_exports.literal(7), external_exports.literal(14), external_exports.literal(30), external_exports.literal(90)]).nullable();
62721
62740
  var conversationOpenDaysSchema = conversationOpenDaysSchemaDefinition;
@@ -79855,6 +79874,26 @@ someone an action cannot be done because Laze refused it earlier, run \`laze cha
79855
79874
  again. When a change lifts a refusal you hit in a conversation, tell the people there once that
79856
79875
  it works now.
79857
79876
 
79877
+ ## Keys from the vault
79878
+
79879
+ Your owner keeps API keys and passwords in the Laze vault. Use them only through these commands:
79880
+
79881
+ - \`laze vault list\` shows the keys you may use: names, fields and levels, never values.
79882
+ - \`laze vault run <name> --reason "<one plain sentence>" -- <command>\` runs the command with the
79883
+ key's fields as environment variables. To put a value in an argument, let a shell expand it
79884
+ inside the run: \`-- sh -c 'curl -H "Authorization: Bearer $OPENAI_API_KEY" <url>'\`.
79885
+ - \`laze vault env --reason "<one plain sentence>" -- <command>\` runs it with every key a
79886
+ \`.env.vault\` file names (\`--env <x>\` reads \`.env.<x>.vault\`, \`--names\` shows what each line
79887
+ resolves to, never a value).
79888
+ - \`laze vault aws <name> --reason "<one plain sentence>" -- <aws command>\` runs it with a
79889
+ short-lived AWS session made from that key.
79890
+
79891
+ The reason is one short sentence a person reads on a phone: what you want to do and why, never a
79892
+ command. A run may wait for an approval card: let it wait and do not start it again. Exit 75: the
79893
+ wait ran out, run it again. Exit 77: denied, so stop and ask. Exit 2: rewrite the reason. Never
79894
+ print, echo or log a value, and never write one into a file, a commit, a message or your notes.
79895
+ If no key fits, ask for it by name; never ask anyone to paste a secret into the chat.
79896
+
79858
79897
  ## Browser tabs and sign-ins
79859
79898
 
79860
79899
  - \`laze browser tabs\` lists the live browser tabs of your conversations. You drive every tab
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lazehq/cli",
3
- "version": "0.1.130",
3
+ "version": "0.1.131",
4
4
  "description": "The Laze command line: sign in, read and post in chat, and connect your own Claude Code or Codex session as an agent.",
5
5
  "license": "UNLICENSED",
6
6
  "type": "module",