Directories
¶
| Path | Synopsis |
|---|---|
|
Package bootstrap handles first-run initialization of the akt config.
|
Package bootstrap handles first-run initialization of the akt config. |
|
Package capability derives a feature set from the active context's configuration: which transports are usable (chain RPC, Console API) and therefore which command groups can work.
|
Package capability derives a feature set from the active context's configuration: which transports are usable (chain RPC, Console API) and therefore which command groups can work. |
|
console
Package console implements the `akt console` CLI commands for the Akash Console managed-wallet API (SPEC §2.9, §7).
|
Package console implements the `akt console` CLI commands for the Akash Console managed-wallet API (SPEC §2.9, §7). |
|
keys
Package keys implements the `akt context keys` CLI commands for managing cryptographic keys within the context's keyring.
|
Package keys implements the `akt context keys` CLI commands for managing cryptographic keys within the context's keyring. |
|
provider
Package provider implements the `akt provider` CLI commands for interacting with provider gateway APIs.
|
Package provider implements the `akt provider` CLI commands for interacting with provider gateway APIs. |
|
sdl
Package sdl implements the transport-independent `akt sdl` command group: scaffold listing, SDL generation, and offline validation.
|
Package sdl implements the transport-independent `akt sdl` command group: scaffold listing, SDL generation, and offline validation. |
|
store
Package store implements the `akt store` CLI commands for managing the local deployment store.
|
Package store implements the `akt store` CLI commands for managing the local deployment store. |
|
workflow
Package workflow generates CLI commands dynamically from workflow definitions.
|
Package workflow generates CLI commands dynamically from workflow definitions. |
|
Package client builds the Cosmos SDK client.Context from the akt context system.
|
Package client builds the Cosmos SDK client.Context from the akt context system. |
|
Package cliutil provides shared CLI utilities (error types, status helpers, verbosity) that are safe to import from both internal/cli and internal/cli/chain without creating import cycles.
|
Package cliutil provides shared CLI utilities (error types, status helpers, verbosity) that are safe to import from both internal/cli and internal/cli/chain without creating import cycles. |
|
Package codec provides the application-wide encoding configuration.
|
Package codec provides the application-wide encoding configuration. |
|
Package console provides an HTTP client for the Akash Console API at https://console-api.akash.network (managed wallets, deployments, and the public marketplace/catalog endpoints).
|
Package console provides an HTTP client for the Akash Console API at https://console-api.akash.network (managed wallets, deployments, and the public marketplace/catalog endpoints). |
|
Package events provides a shared blockchain event service for the akt CLI.
|
Package events provides a shared blockchain event service for the akt CLI. |
|
Package glyphs provides a centralized registry of all PUA-range (Nerd Font) glyphs used throughout the akt UI, with ASCII fallbacks for terminals that do not have a Nerd Font installed.
|
Package glyphs provides a centralized registry of all PUA-range (Nerd Font) glyphs used throughout the akt UI, with ASCII fallbacks for terminals that do not have a Nerd Font installed. |
|
Package keyring provides multi-keyring management for akt.
|
Package keyring provides multi-keyring management for akt. |
|
Package mcp implements an MCP (Model Context Protocol) server that exposes Akash Network tools for AI assistant integration.
|
Package mcp implements an MCP (Model Context Protocol) server that exposes Akash Network tools for AI assistant integration. |
|
tools/console
Package console exposes the Console API as MCP tools, so an assistant working against a managed (console-api) context reaches the same rail the `akt console` commands use rather than the chain directly.
|
Package console exposes the Console API as MCP tools, so an assistant working against a managed (console-api) context reaches the same rail the `akt console` commands use rather than the chain directly. |
|
monitor
|
|
|
Package provider provides a thin wrapper around the chain-sdk's provider REST client, integrating it with the akt context system's auth configuration.
|
Package provider provides a thin wrapper around the chain-sdk's provider REST client, integrating it with the akt context system's auth configuration. |
|
Package sync provides a sync engine that maps chain events to local store CRUD operations.
|
Package sync provides a sync engine that maps chain events to local store CRUD operations. |
|
Package transport is the translation layer between workflow actions and the rails that execute them.
|
Package transport is the translation layer between workflow actions and the rails that execute them. |
|
ui
|
|
|
theme
Package theme provides the unified color palette and base styles for the entire akt UI — both CLI pretty output and TUI views.
|
Package theme provides the unified color palette and base styles for the entire akt UI — both CLI pretty output and TUI views. |
|
Package workflow provides a declarative workflow engine for orchestrating multi-step chain operations.
|
Package workflow provides a declarative workflow engine for orchestrating multi-step chain operations. |
|
adapters
Package adapters implements the narrow client interfaces the workflow engine's step executors depend on (steps.ChainClient and steps.ProviderClient), backed by the real Akash node and provider gateway clients.
|
Package adapters implements the narrow client interfaces the workflow engine's step executors depend on (steps.ChainClient and steps.ProviderClient), backed by the real Akash node and provider gateway clients. |
|
builtin
Package builtin provides embedded default workflow definitions.
|
Package builtin provides embedded default workflow definitions. |
|
steps
Package steps defines the StepExecutor interface and a registry of built-in step type implementations for the workflow engine.
|
Package steps defines the StepExecutor interface and a registry of built-in step type implementations for the workflow engine. |
Click to show internal directories.
Click to hide internal directories.