npm package: @seamflux/cli
Description: SeamFlux CLI - Command line tool for seamflux.ai
Latest version: 0.1.72

# SeamFlux CLI

Command-line entry: `seamflux` or `sf` (same binary).

## Global options

| Option | Description |
|--------|-------------|
| `-h`, `--help` | Help |
| `-v`, `--version` | Version |
| `--json` | JSON output (where supported) |

---

## `config`

```
seamflux config apikey <key> [--force]
seamflux config apikey --oauth [--force]
seamflux config show
seamflux config set <key> <value> [--env]
seamflux config get <key> [--env]
seamflux config use <profile-name>
```

---

## `automation`

```
seamflux automation list [--json]
seamflux automation get <name> [--id <id>] [--json]
seamflux automation delete <name> [--id <id>] [--force] [--json]
seamflux automation download --slug <workflow-slug> [--output <dir-name>] [--json]
seamflux automation download @<workflow-slug> [--output <dir-name>] [--json]
seamflux automation deploy <name> [--json]
seamflux automation run <workflow-slug> [--json]
seamflux automation stop <workflow-slug> [--json]
```

Workflow refs match the agent runtime: `<workflow-slug>` may be a nested path under `automations/` (for example `monitoring/my-wf`).

---

## `invoke`

```
seamflux invoke <service> <method> [options]
seamflux invoke --service <service> --method <method> [options]
```

| Option | Description |
|--------|-------------|
| `--full` | Full result JSON line on stdout |
| `--pipe` | Raw payload JSON on stdout; logs on stderr |
| `-p`, `--param` | `key=value` or `key:type=value` (repeatable) |
| `-b`, `--body` | JSON body string |
| `--params` | Same as `--body` (tooling compatibility) |
| `--service`, `--method` | Alternative to the two positional arguments |
| `-f`, `--file` | Read parameters from JSON file |
| `--stdin` | Read parameters from stdin |
| `--use-log` | `"<service> <method>"` for log context |
| `--map` | Mapping flags (repeatable) |

---

## `service`

```
seamflux service list
seamflux service query --query <search> [--service <name>] [--method <name>] 
seamflux service query --service <name> --method <method> 
seamflux service meta --service <name> --method <method> 
seamflux service get <name>
```

---

## `connection`

```
seamflux connection list --type <type>
seamflux connection list <type>
seamflux connection add <type> --name <name> [--remark <text>] [--raw] [--body '<json>'] [--field key=value] [--uri <uri>] [--token <json>] [--wallet <address>] [--json]
seamflux connection connect --name <name> --type <type> [--token '<json>']
seamflux connection remove --name <name> --type <type> [--json]
seamflux connection delete --name <name> --type <type> [--json]
```

(`delete` is an alias of `remove`.)

---

## `chat`

```
seamflux chat reply <session-id> <message> [--json]
seamflux chat reply [--session-id <id>] [--body '<json>' | --file <path> | --stdin] [--json]
```

---

## `signer`

```
seamflux signer create [<name>]
seamflux signer create --name <name>
seamflux signer list [--json]
seamflux signer sign <address> [json] [--name <signer>] [--caip2 <caip2>] [--sui-rpc <url>] [--stdin] [-f|--file <path>] [-b|--body <json>] [-p|--param key=value] [--use-log "<service> <method>"] [--map ...] [--sign-typed-data | --sign-transaction | --send-transaction | --sign-message | --sign-sui-transaction | --send-sui-transaction]
```

Use at most one of: `--sign-typed-data`, `--sign-transaction`, `--send-transaction`, `--sign-message`, `--sign-sui-transaction`, `--send-sui-transaction`.

**Sui** (`--sign-sui-transaction` / `--send-sui-transaction`): body must include `"transactions"` (string, same serialized form as `@mysten/sui` `Transaction.from`). Uses `SEAMFLUX_SIGNER_<name>` as the **Privy authorization** private key (same as EVM); optional `"signerKey"` in JSON overrides. Resolves `walletId` from the address mapping or optional `"walletId"` in JSON. Default Sui RPC is `https://sui-rpc.publicnode.com`; set `SUI_RPC_URL` or `--sui-rpc` to override.

---

## `walletconnect`

Global passthrough flags for these subcommands (where applicable): `--wallet <0x-address|suffix>`, `--browser`, `--qrcode`, `--json`, `--foreground`, `--chain` (repeatable for `connect`).

```
seamflux walletconnect status [--wallet <0x-address|suffix>]
seamflux walletconnect disconnect [--wallet <0x-address|suffix>]
seamflux walletconnect connect [--chain <id> ...] [--wallet <0x-address|suffix>] [--foreground]
seamflux walletconnect connect --browser | --qrcode [--wallet <0x-address|suffix>]
seamflux walletconnect whoami [--json] [--wallet <0x-address|suffix>]
seamflux walletconnect sign <message> [--browser|--qrcode] [--wallet <0x-address|suffix>]
seamflux walletconnect sign-typed-data <json> [--browser|--qrcode] [--wallet <0x-address|suffix>]
seamflux walletconnect sign-transaction '<json>' [--browser|--qrcode] [--wallet <0x-address|suffix>]
seamflux walletconnect send-transaction '<json>' [--browser|--qrcode] [--wallet <0x-address|suffix>]
seamflux walletconnect config get project-id
```

`sign-transaction` calls `eth_signTransaction` (EVM only); JSON shape matches `send-transaction` (`chainId`, `from`, `to`, `data`, `value`, `gas`, plus optional EIP-1559 fields). For Solana signing, use `send-transaction` with `chainId` `solana:…`. Sessions paired before `eth_signTransaction` was offered may need `walletconnect disconnect` then connect again.

Place `walletconnect` immediately after global options; arguments after `walletconnect` are passed through to the WalletConnect handler.

---

## Top-level usage

```
seamflux [global-options] <module> <command> [args...]
seamflux walletconnect <subcommand> [args...]
```

Help:

```
seamflux -h | --help
seamflux <module> -h | --help
```

If `--help` appears before the module, include the module as the next positional (e.g. `seamflux --help automation`).