fjall accounts lists the provider accounts in your organisation that carry a workload stage. It is read-only and never touches AWS.
Prerequisites
Prerequisites
- Node.js 22 or later with the Fjall CLI installed
- A signed-in session (
fjall login), because the account list comes from your organisation config over the Fjall API - At least one connected AWS account (
fjall connect)
infrastructure.ts are required. Run this command from anywhere.List connected accounts
list is the only supported subcommand, and it is the default when the positional is omitted.
jq to pull a single field:
What Happens
The command runs two steps, then prints and exits.
Organisation-tier and platform-tier accounts are filtered out. What remains is the set of accounts that hold workloads, which is why the command is an alias surface for non-structural deployment targets.
Human output
[no stage]. A (managed) suffix appears when the account record carries the managed flag.
With no matching accounts, the command prints:
JSON output
--output json writes exactly one line of strict JSON to stdout, with no banners or progress lines:
Failures
A failed fetch (not signed in, no organisation, network error) exits1.
- Human mode writes
Failed to list accounts: <message>to stderr. - JSON mode writes one line of
{"ok":false,"error":"<message>"}to stdout.
Agent mode
fjall accounts has no agent output path. Passing --agent, --budget, --fields, or --full is refused with an error naming the alternative rather than silently printing a human table. Use fjall accounts list --output json instead, which is the same surface the Fjall MCP server parses.
Options
The command always prints plain text, so
--non-interactive changes nothing about its output.
Next Steps
fjall connect
Connect an AWS account so it appears in this list.
Deploy an account
Use
fjall account deploy (singular) to deploy the account tier.fjall deploy
Deploy an application into one of these accounts.
Deploy an organisation
Set up the organisation and platform tiers above your accounts.