astrale-cli

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Astrale CLI

astrale

connects to existing Astrale Kernels. It selects an instance and identity, performs graph reads and mutations, invokes callables, installs running domains, reads the Kernel journal, and opens authenticated views.

The rendered command help is authoritative for flags and defaults:

bash

astrale --help
astrale <command> --help

Binary:
```
astrale
```
Package:
```
@astrale-os/cli
```
Runtime: Node 22 or newer; source development defaults to Node 26 and also supports Node 24 and Bun
Dev entrypoint:
```
bun cli/bin/astrale.ts <command>
```

astrale

可连接至已有的 Astrale Kernel。它会选择一个实例和身份，执行图读取与变更操作，调用可调用对象，安装运行中的域，读取Kernel日志，并打开经过身份验证的视图。

命令帮助的渲染结果是标志和默认值的权威参考：

bash

astrale --help
astrale <command> --help

二进制文件：
```
astrale
```
包：
```
@astrale-os/cli
```
运行环境：Node 22或更高版本；源码开发默认使用Node 26，同时支持Node 24和Bun
开发入口：
```
bun cli/bin/astrale.ts <command>
```

Command Surface

命令范围

Primary commands:

bash

astrale status
astrale whoami
astrale use <name>
astrale get <target>
astrale query [sources...]
astrale introspect <origin-or-path>
astrale mutate
astrale call <path> [key=value...]
astrale token
astrale logs
astrale view [target-or-view]
astrale ui ...
astrale instance ...
astrale domain ...
astrale identity ...
astrale auth ...
astrale idp ...
astrale admin ...

Kernel-touching commands share

--format

--json

--raw

--url

-i/--instance

--timeout

--as

--creds

--anonymous

, and

--debug

where applicable. The CLI creates one public Kernel

Call

, and its Client session owns remote routing, fresh credentials, and one safe stale-route retry.

astrale ui

is local project tooling and never takes Kernel, instance, identity, or credential options.

Use

--anonymous

to omit a caller credential even when a local or bookmark-default identity exists. It cannot be combined with

--as

--creds

; required callables reject anonymous requests.

核心命令：

bash

astrale status
astrale whoami
astrale use <name>
astrale get <target>
astrale query [sources...]
astrale introspect <origin-or-path>
astrale mutate
astrale call <path> [key=value...]
astrale token
astrale logs
astrale view [target-or-view]
astrale ui ...
astrale instance ...
astrale domain ...
astrale identity ...
astrale auth ...
astrale idp ...
astrale admin ...

涉及Kernel的命令会共享

--format

、

--json

、

--raw

、

--url

、

-i/--instance

、

--timeout

、

--as

、

--creds

、

--anonymous

和

--debug

（适用时）。CLI会创建一个公开的Kernel

Call

，其客户端会话拥有远程路由、全新凭据以及一次安全的陈旧路由重试机制。

astrale ui

是本地项目工具，不会接收Kernel、实例、身份或凭据相关选项。

即使存在本地或书签默认身份，也可使用

--anonymous

省略调用者凭据。它无法与

--as

或

--creds

组合使用；必填的可调用对象会拒绝匿名请求。

UI Projects

UI项目

Astrale UI is one tree-shakeable runtime package plus consumer-owned pattern, block, and theme source. Initialize a React and Tailwind CSS v4 project with the exact published UI release:

bash

astrale ui init --preset astrale
astrale ui list chart
astrale ui add pattern/chart/line-basic
astrale ui add theme/observatory
astrale ui add ./my-playground-export.css
astrale ui doctor
astrale ui doctor --project ./apps/web
astrale ui preset apply compact

Initialization writes Base UI + Nova shadcn configuration, theme and preset CSS imports, and

astrale-ui.lock.json

. The lock records the exact package version, Git tag, resolved commit SHA, shadcn version, Base UI version, preset, and hashes of installed source. Registry metadata, included manifests, and item files are always read from that single commit snapshot.

Run

astrale ui add

without item arguments for an interactive picker. In CI, provide canonical addresses explicitly. Ordinary add refuses locally edited installed files; review those files, then use

--overwrite --yes

only when replacement is intentional.

--dry-run

leaves project files and the lock unchanged. Use

astrale ui list --json

when registry metadata is needed by a script or agent.

Patterns, blocks, and themes are application-owned source after installation. A theme is copied to

components/astrale/theme/

and activated through one relative import in the configured host stylesheet; local playground exports require no registry fetch or shadcn invocation. Composition root

className

, inline

style

, controlled values/actions, and stable

data-slot

anatomy remain open to the host. The package owns reusable runtime behavior; neither the CLI nor the SDK embeds the UI package or Base UI.

Astrale UI是一个可摇树优化的运行时包，加上由使用者维护的模式、区块和主题源码。使用以下命令初始化一个基于React和Tailwind CSS v4的项目，匹配已发布的UI版本：

bash

astrale ui init --preset astrale
astrale ui list chart
astrale ui add pattern/chart/line-basic
astrale ui add theme/observatory
astrale ui add ./my-playground-export.css
astrale ui doctor
astrale ui doctor --project ./apps/web
astrale ui preset apply compact

初始化操作会写入Base UI + Nova shadcn配置、主题和预设CSS导入，以及

astrale-ui.lock.json

。该锁文件记录了确切的包版本、Git标签、解析后的提交SHA、shadcn版本、Base UI版本、预设，以及已安装源码的哈希值。注册表元数据、包含的清单和项目文件始终从该单一提交快照中读取。

不带项目参数运行

astrale ui add

会启动交互式选择器。在CI环境中，请明确提供规范地址。普通的add操作会拒绝覆盖本地已编辑的安装文件；如需替换，请先检查这些文件，仅在有意替换时使用

--overwrite --yes

。

--dry-run

不会修改项目文件和锁文件。当脚本或Agent需要注册表元数据时，请使用

astrale ui list --json

。

模式、区块和主题在安装后归应用程序所有。主题会被复制到

components/astrale/theme/

，并通过配置的宿主样式表中的一个相对导入激活；本地游乐场导出无需获取注册表或调用shadcn。宿主可自由控制组合根的

className

、内联

style

、受控值/操作以及稳定的

data-slot

结构。包负责可复用的运行时行为；CLI和SDK均不会嵌入UI包或Base UI。

Paths

路径

Use canonical Kernel V2 Paths:

Form	Example
Domain root	`/:notes.example.dev`
Class	`/:notes.example.dev:class.Note`
Static callable	`/:notes.example.dev:class.Note:list`
Instance callable	`@node-id::archive`
Node ID	`@node-id`
Active caller shorthand	`@self`

Static dispatch uses one colon before the method. Instance dispatch uses

::

@self

is expanded by the CLI before signing when it appears at the head of a call Path or a bare

key=@self

value. It is not rewritten inside

--data

, stdin JSON, URLs, or arbitrary substrings.

bash

astrale get @self --json
astrale call /:blog.example:class.Author:list limit=10
astrale call @self::deactivate

使用标准的Kernel V2路径：

格式	示例
域根	`/:notes.example.dev`
类	`/:notes.example.dev:class.Note`
静态可调用对象	`/:notes.example.dev:class.Note:list`
实例可调用对象	`@node-id::archive`
节点ID	`@node-id`
当前调用者简写	`@self`

静态调度在方法前使用一个冒号。实例调度使用

::

。当

@self

出现在调用路径的开头或

key=@self

的裸值中时，CLI会在签名前将其展开。它不会在

--data

、标准输入JSON、URL或任意子字符串中重写。

bash

astrale get @self --json
astrale call /:blog.example:class.Author:list limit=10
astrale call @self::deactivate

Instances And Domains

实例与域

astrale instance

combines admin-provisioned instances and local bookmarks:

bash

astrale instance create my-app
astrale instance status my-app
astrale instance status staging --bookmarked
astrale instance use my-app
astrale instance bookmark staging --url https://kernel.example.com
astrale instance forget staging

Use explicit

-i <instance>

in scripts.

instance delete

affects an admin-managed instance;

instance forget

removes only the local bookmark.

instance status

reports Admin-owned lifecycle by default; add

--bookmarked

to probe one local bookmark's exact issuer, JWKS, and TLS trust instead. Without a deployed Admin Domain,

astrale instance list

cannot fetch managed instances (key-backed identities have no Admin token). Use

astrale instance list --bookmarked

The CLI is connect-only: it does not build or run domains. The SDK's

astrale-domain

binary owns

dev

prod

build

, and deploy workflows.

astrale domain install

has two modes:

Default: install a published catalog origin or URL through the admin control plane onto an admin-managed instance.
```
--direct
```
: call the public Kernel install syscall with a running domain URL. This works for any instance you can authenticate to and owns the explicit identity-override consent prompt.

bash

astrale domain install crm.example -i staging
astrale domain install https://crm.example --direct -i staging
astrale domain uninstall crm.example -i staging

A replacement cannot change an installed Domain issuer. If that identity change is intentional, uninstall the origin first and then install it again. Uninstall removes the installed Domain but never deletes business data. It requires typing the exact origin interactively (or

--yes

in automation), and is refused by the Kernel while dependents or business data remain.

Bookmarks retain their own TLS trust (

--ca

instance use

probes OIDC and JWKS with that exact CA. If two bookmarks point to the same normalized URL with different CA settings, the CLI warns and

instance list --bookmarked --json

shows each bookmark's

caFile

, issuer, and default identity.

A deployment-only Publication change does not inherently require reinstalling the Domain. Reinstall or run a schema plan only when installation/schema intent actually changes.

astrale instance

整合了管理员配置的实例和本地书签：

bash

astrale instance create my-app
astrale instance status my-app
astrale instance status staging --bookmarked
astrale instance use my-app
astrale instance bookmark staging --url https://kernel.example.com
astrale instance forget staging

在脚本中使用显式的

-i <instance>

。

instance delete

会影响管理员管理的实例；

instance forget

仅移除本地书签。

instance status

默认报告管理员拥有的生命周期；添加

--bookmarked

可探测本地书签的确切颁发者、JWKS和TLS信任。如果未部署Admin Domain，

astrale instance list

无法获取托管实例（密钥身份没有Admin令牌）。请使用

astrale instance list --bookmarked

。

CLI仅负责连接：它不构建或运行域。SDK的

astrale-domain

二进制文件负责

dev

、

prod

、

build

和部署工作流。

astrale domain install

有两种模式：

默认模式：通过管理控制平面将已发布的目录源或URL安装到管理员管理的实例上。
```
--direct
```
模式：使用运行中的域URL调用公开的Kernel安装系统调用。这适用于任何您可以进行身份验证的实例，并会触发明确的身份覆盖同意提示。

bash

astrale domain install crm.example -i staging
astrale domain install https://crm.example --direct -i staging
astrale domain uninstall crm.example -i staging

替换操作无法更改已安装域的颁发者。如果有意更改身份，请先卸载源，然后重新安装。卸载操作会移除已安装的域，但绝不会删除业务数据。它要求交互式输入确切的源（或在自动化中使用

--yes

），并且当存在依赖项或业务数据时，Kernel会拒绝该操作。

书签保留自己的TLS信任（

--ca

）。

instance use

会使用该确切的CA探测OIDC和JWKS。如果两个书签指向同一标准化URL但CA设置不同，CLI会发出警告，且

instance list --bookmarked --json

会显示每个书签的

caFile

、颁发者和默认身份。

仅部署的发布变更本质上不需要重新安装域。仅当安装/架构意图实际更改时，才需要重新安装或运行架构计划。

Identity And Delegation

身份与委托

astrale auth login

stores an IdP-backed identity.

astrale identity create

creates a local key identity. Registering a key identity on a Kernel is an atomic V2 provision operation and requires the exact Node Class:

bash

astrale identity create alice
astrale identity register alice \
  --class /:accounts.example:class.User \
  --props '{"accounts.example:class.User.property.name":"Alice"}' \
  -i staging

There is no caller-chosen storage

--path

: Kernel V2 Node IDs are opaque. The proof is bound to the exact provision fingerprint and target Kernel audience. For an application-owned Identity Class, direct Kernel submission is correctly denied unless the caller owns that Class. Name the Domain's authorizing registration callable explicitly; the CLI sends the same self-proven request through it and stores only the admitted target-bound result:

bash

astrale identity register operator \
  --class /:operations.example:class.Operator \
  --props '{"operations.example:class.Operator.property.name":"Operator"}' \
  --via /:operations.example:function.provisionOperator \
  -i staging

astrale token

issues an audience-bound credential for the selected authenticated identity. When the audience is the target Kernel issuer (the default), it mints a top-level Grant credential that can be reused with

--creds

. A different

--audience

creates a delegated service envelope for that receiver instead. TTL defaults to 240 seconds so it remains below the five-minute local key proof; an explicit TTL still cannot outlive the selected source credential. Use

--raw

for shell assignment.

bash

TOKEN=$(astrale token --raw -i staging)
astrale call /:notes.example:class.Note:list --creds "$TOKEN" -i staging

astrale auth token

is different: it prints the cached upstream IdP token.

astrale auth login

存储一个基于IdP的身份。

astrale identity create

创建一个本地密钥身份。在Kernel上注册密钥身份是一个原子性的V2配置操作，需要确切的节点类：

bash

astrale identity create alice
astrale identity register alice \
  --class /:accounts.example:class.User \
  --props '{"accounts.example:class.User.property.name":"Alice"}' \
  -i staging

没有调用者可选的存储

--path

：Kernel V2节点ID是不透明的。证明与确切的配置指纹和目标Kernel受众绑定。对于应用程序拥有的身份类，除非调用者拥有该类，否则Kernel会直接拒绝提交。请明确指定域的授权注册可调用对象；CLI会通过它发送相同的自证明请求，并仅存储被认可的目标绑定结果：

bash

astrale identity register operator \
  --class /:operations.example:class.Operator \
  --props '{"operations.example:class.Operator.property.name":"Operator"}' \
  --via /:operations.example:function.provisionOperator \
  -i staging

astrale token

为所选的已认证身份颁发一个受众绑定的凭据。当受众是目标Kernel颁发者（默认值）时，它会生成一个顶级Grant凭据，可与

--creds

复用。不同的

--audience

会为该接收者创建一个委托服务信封。TTL默认值为240秒，以保持在五分钟本地密钥证明的范围内；显式TTL仍不能超过所选源凭据的有效期。使用

--raw

以便在Shell中赋值。

bash

TOKEN=$(astrale token --raw -i staging)
astrale call /:notes.example:class.Note:list --creds "$TOKEN" -i staging

astrale auth token

有所不同：它会打印缓存的上游IdP令牌。

Graph Reads

图读取

get

get

get

reads one exact canonical Node:

json

{ "id": "opaque-id", "class": "/:notes.example:class.Note", "props": {} }

Nodes do not carry synthetic

path

__labels

, or backend

classId

fields. It does not infer operations or children.

bash

astrale get @note --json
astrale get /:notes.example:class.Note
astrale get /:kernel.astrale.ai --schema

astrale describe

is not a command. Use

get

for one Node. Method Paths are not Nodes — use

call

introspect

. Schema-valued properties are omitted unless

--schema

is passed.

get

读取一个确切的标准节点：

json

{ "id": "opaque-id", "class": "/:notes.example:class.Note", "props": {} }

节点不包含合成的

path

、

__labels

或后端

classId

字段。它不会推断操作或子节点。

bash

astrale get @note --json
astrale get /:notes.example:class.Note
astrale get /:kernel.astrale.ai --schema

astrale describe

不是一个命令。请使用

get

获取单个节点。方法路径不是节点——请使用

call

或

introspect

。除非传递

--schema

，否则会省略架构值属性。

introspect

introspect

introspect

reads the Kernel Schema syscall for one installed Domain.

bash

astrale introspect kernel.astrale.ai
astrale introspect /:kernel.astrale.ai --bundle
astrale introspect /:kernel.astrale.ai:class.Identity:whois

A method or Function Path projects that callable's input/output from the installed bundle.

astrale call --describe

is not a flag.

introspect

读取已安装域的Kernel Schema系统调用。

bash

astrale introspect kernel.astrale.ai
astrale introspect /:kernel.astrale.ai --bundle
astrale introspect /:kernel.astrale.ai:class.Identity:whois

方法或函数路径会从已安装的包中投影该可调用对象的输入/输出。

astrale call --describe

不是一个标志。

query

query

query

executes canonical

astrale.graph.query/v6

. Its machine result is

{ kind: "graph", graph: { nodes, edges }, page?: { next } }

; pass the opaque

page.next

value to

--cursor

until it is absent.

Positional Paths create Path source terms.
```
--definition <path>
```
selects Nodes implementing one exact Class.
```
--edge <class>
```
adds one exact expansion; direction is
```
outgoing
```
,
```
incoming
```
, or
```
incident
```
.
```
--limit
```
is finite and defaults to 100.
```
--cursor
```
resumes the same caller-bound query scope.
```
--ast
```
and
```
--file
```
admit a complete canonical Query V6 document.

bash

astrale query /:notes.example:class.Note --limit 50 --json
astrale query --definition /:notes.example:class.Note --limit 50 --json
astrale query @note \
  --edge /:notes.example:class.references \
  --direction outgoing --limit 25 --json
astrale query --file query.v6.json --cursor "$CURSOR"

Raw Cypher, recursive depth, and historical children/edges selector JSON are not portable Kernel V2 contracts and are not accepted.

astrale ls

is not a command. Use

query

with

--edge

for an exact neighborhood.

query

执行标准的

astrale.graph.query/v6

。其机器结果为

{ kind: "graph", graph: { nodes, edges }, page?: { next } }

；传递不透明的

page.next

值到

--cursor

，直到它不存在。

位置路径创建路径源术语。
```
--definition <path>
```
选择实现一个确切类的节点。
```
--edge <class>
```
添加一个确切的扩展；方向为
```
outgoing
```
、
```
incoming
```
或
```
incident
```
。
```
--limit
```
是有限的，默认值为100。
```
--cursor
```
恢复相同的调用者绑定查询范围。
```
--ast
```
和
```
--file
```
接受完整的标准Query V6文档。

bash

astrale query /:notes.example:class.Note --limit 50 --json
astrale query --definition /:notes.example:class.Note --limit 50 --json
astrale query @note \
  --edge /:notes.example:class.references \
  --direction outgoing --limit 25 --json
astrale query --file query.v6.json --cursor "$CURSOR"

原生Cypher、递归深度和历史子节点/边选择器JSON不是可移植的Kernel V2契约，不会被接受。

astrale ls

不是一个命令。请使用带

--edge

的

query

获取确切的邻域。

Mutations

变更操作

astrale mutate

accepts canonical

astrale.graph.mutation/v3

or its exact

{ preconditions, operations }

authoring input from

--data

--file

, or stdin. The transition is atomic.

--dry

admits and prints the canonical document without opening a Kernel connection. Legacy PatchData

{ nodes, edges }

is rejected.

bash

astrale mutate --file mutation.v3.json
astrale mutate --data '{"preconditions":[],"operations":[]}' --dry

The result is

{ createdNodes }

. Historical PatchData arms and

createdEdges

are not emulated.

astrale mutate

接受标准的

astrale.graph.mutation/v3

或其确切的

{ preconditions, operations }

创作输入，来源为

--data

、

--file

或标准输入。转换是原子性的。

--dry

接受并打印标准文档，但不会建立Kernel连接。旧版PatchData

{ nodes, edges }

会被拒绝。

bash

astrale mutate --file mutation.v3.json
astrale mutate --data '{"preconditions":[],"operations":[]}' --dry

结果为

{ createdNodes }

。不会模拟历史PatchData的arms和

createdEdges

。

Calls

调用

astrale call

creates one Path-targeted Call. Input priority is

--data

, piped stdin,

key=value

, then

{}

--dry-run

admits the Path and prints the call input. Value, binary, and stream results are handled explicitly, and

--output

writes binary data. A streaming binary is drained with backpressure while the command-scoped Client session is live, then presented through the same raw/file/JSON paths as buffered binary. JSON preserves application status and encodes the body as text or base64. Callable input/output is

astrale introspect <path>

bash

astrale call /:blog.example:class.Author:list limit=10
astrale call /:blog.example:class.Author:create \
  --data '{"name":"Ada"}' --json
astrale call /:assets.example:class.Asset:render id=123 --output asset.png

Top-level

key=value

values coerce booleans, null, numbers, arrays, and objects. Use

--data

for nested or digits-only string values.

astrale call

创建一个路径目标的Call。输入优先级为

--data

、管道标准输入、

key=value

，最后是

{}

。

--dry-run

接受路径并打印调用输入。显式处理值、二进制和流结果，

--output

写入二进制数据。流式二进制会在命令范围的客户端会话活跃时通过背压排出，然后通过与缓冲二进制相同的原始/文件/JSON路径呈现。JSON保留应用程序状态，并将正文编码为文本或base64。可调用对象的输入/输出可通过

astrale introspect <path>

查看。

bash

astrale call /:blog.example:class.Author:list limit=10
astrale call /:blog.example:class.Author:create \
  --data '{"name":"Ada"}' --json
astrale call /:assets.example:class.Asset:render id=123 --output asset.png

顶级

key=value

值会强制转换为布尔值、null、数字、数组和对象。对于嵌套或纯数字的字符串值，请使用

--data

。

Journal

日志

astrale logs

reads the public Kernel journal syscall and returns

{ records, cursor? }

. Filters are exact, not legacy glob lowering:

bash

astrale logs -i staging --limit 50
astrale logs --topic op:function.failed
astrale logs --topic-prefix op:function. --follow

Use

--principal

--since

--until

, or an opaque

--cursor

as needed.

--follow

retains one Client session and advances only with returned cursors. Application-service console buffers are not part of this command. Machine output retains the admitted structured

correlation

object, including invocation root and parent identifiers, and also keeps the compatibility

correlationId

projection of

invocationId

. Machine

--follow

output is NDJSON with one complete admitted record per line; YAML follow is rejected.

astrale logs

读取公开的Kernel日志系统调用，并返回

{ records, cursor? }

。过滤器是精确匹配，而非旧版的全局模糊匹配：

bash

astrale logs -i staging --limit 50
astrale logs --topic op:function.failed
astrale logs --topic-prefix op:function. --follow

根据需要使用

--principal

、

--since

、

--until

或不透明的

--cursor

。

--follow

会保留一个客户端会话，并仅通过返回的游标推进。应用程序服务控制台缓冲区不属于此命令。机器输出保留已接受的结构化

correlation

对象，包括调用根和父标识符，同时保留

correlationId

对

invocationId

的兼容性投影。机器

--follow

输出为NDJSON，每行一个完整的已接受记录；不支持YAML格式的follow输出。

Views And Browser Sessions

视图与浏览器会话

astrale view

opens one resolved View through a local browser shell:

bash

astrale view @customer --list
astrale view @customer --snapshot
astrale view /:crm.example:view.dashboard --target @customer
astrale view --sessions
astrale view --close <session-id>

astrale browser

prepares a persistent authenticated GUI browser profile. Use

astrale browser --check

to verify it, then drive the printed profile with

agent-browser

astrale view

通过本地浏览器Shell打开一个已解析的视图：

bash

astrale view @customer --list
astrale view @customer --snapshot
astrale view /:crm.example:view.dashboard --target @customer
astrale view --sessions
astrale view --close <session-id>

astrale browser

准备一个持久化的已认证GUI浏览器配置文件。使用

astrale browser --check

进行验证，然后使用

agent-browser

驱动打印的配置文件。

Output And Automation

输出与自动化

TTY defaults are human-readable.
```
--json
```
emits one JSON document for finite commands;
```
logs --follow
```
emits an NDJSON stream.
```
--raw
```
unwraps scalars and writes raw binary bytes.
```
--format yaml|json
```
selects finite structured rendering;
```
logs --follow
```
supports JSON/NDJSON only.
Use
```
--ci --no-prompt
```
for automation.
Use explicit
```
-i
```
,
```
--as
```
, and
```
--timeout
```
rather than ambient state.
Pipe large JSON through stdin; command-line argument size is limited by the operating system.

TTY默认输出为人类可读格式。
```
--json
```
为有限命令输出一个JSON文档；
```
logs --follow
```
输出NDJSON流。
```
--raw
```
展开标量并写入原始二进制字节。
```
--format yaml|json
```
选择有限的结构化渲染；
```
logs --follow
```
仅支持JSON/NDJSON。
自动化环境中使用
```
--ci --no-prompt
```
。
使用显式的
```
-i
```
、
```
--as
```
和
```
--timeout
```
，而非环境状态。
通过标准输入传输大型JSON；命令行参数大小受操作系统限制。

Debugging

调试

Start with:

bash

astrale status
astrale instance active
astrale auth status
astrale whoami

Add

--debug

for full Kernel error diagnostics. A missing and an authorization-masked graph Node may intentionally be indistinguishable. For callable input/output shape, use

astrale introspect <path>

从以下命令开始：

bash

astrale status
astrale instance active
astrale auth status
astrale whoami

添加

--debug

以获取完整的Kernel错误诊断信息。缺失的图节点和授权掩码的图节点可能在故意设计上无法区分。如需查看可调用对象的输入/输出形状，请使用

astrale introspect <path>

。

Storage

存储

State lives under

ASTRALE_HOME

, or

~/.astrale

by default:

text

config.json
instances.json
identities.json
idps/
idp-sessions/
keys/
browser.json
browser/

Optional roots are

ASTRALE_HOME

ASTRALE_KEYS_DIR

, and

ASTRALE_DATA_DIR

状态存储在

ASTRALE_HOME

下，默认路径为

~/.astrale

：

text

config.json
instances.json
identities.json
idps/
idp-sessions/
keys/
browser.json
browser/

可选根目录包括

ASTRALE_HOME

、

ASTRALE_KEYS_DIR

和

ASTRALE_DATA_DIR

。

Source Map

源码映射

Entry:
```
cli/bin/astrale.ts
```
Program and shared options:
```
cli/src/program/
```
Public Kernel connection boundary:
```
cli/src/connection/
```
Query/Mutation document preparation:
```
cli/src/graph/
```
Commands:
```
cli/src/commands/
```
Shared presentation and local stores:
```
cli/src/lib/
```
Studio bridge:
```
cli/studio/server/
```
Tests: owner-local
```
__tests__/
```
directories

入口：
```
cli/bin/astrale.ts
```
程序和共享选项：
```
cli/src/program/
```
公开Kernel连接边界：
```
cli/src/connection/
```
查询/变更文档准备：
```
cli/src/graph/
```
命令：
```
cli/src/commands/
```
共享展示和本地存储：
```
cli/src/lib/
```
Studio桥接：
```
cli/studio/server/
```
测试：所有者本地的
```
__tests__/
```
目录

astrale-cli

Original

Translation

Astrale CLI

Astrale CLI

Command Surface

命令范围

UI Projects

UI项目

Paths

路径

Instances And Domains

实例与域

Identity And Delegation

身份与委托

Graph Reads

图读取

`get`

`get`

`introspect`

`introspect`

`query`

`query`

Mutations

变更操作

Calls

调用

Journal

日志

Views And Browser Sessions

视图与浏览器会话

Output And Automation

输出与自动化

Debugging

调试

Storage

存储

Source Map

源码映射