You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds a "Stellar CLI for Agents" section at docs/tools/cli/agent-cli/ covering how to use the Stellar CLI and CLI Skills as an agent wallet. It includes a quickstart, the skills overview, seven cookbook guides (send tokens, balances and metadata, delegated spending, message signing, build and submit, x402 payments, USDT0 on mainnet), and four reference pages (architecture, authority model, output and errors, troubleshooting).
The section sits in the Tools sidebar under Stellar CLI, directly below the Stellar CLI Manual, and in the Tools navbar dropdown directly below Stellar CLI. Subsections are collapsed by default.
This description is too broad: direct RPC reads such as network health, ledger latest, and tx fetch do not simulate a transaction; simulation applies to contract/SAC-style reads. Scope the statement so agents do not infer that every read has simulation semantics.
Not all state-modifying commands use the five-stage pipeline
Not every state-modifying command goes through these five stages: a classic tx new payment/tx send path does not simulate or authorize Soroban entries. This overstates the write path and conflicts with the later guidance that a custom Soroban pipeline must call tx simulate explicitly.
The same overstatement appears here: 2>&1 can hide a successful submit, but retrying the exact same signed envelope is not a double spend; only rebuilding a new envelope can repeat the operation. State that distinction so agents do not treat every retry path as equivalent.
Distinguish rebuilding transactions from resending envelopes
confirmed double-spend is too strong and conflates rebuilding with resending. A parse failure followed by rebuilding the command can submit a second transaction, but resending the same signed envelope is sequence-protected and will not execute it twice.
Soroban transactions require resource fees beyond the base fee
The base fee is not the whole requirement here. Soroban-backed commands such as token transfer also need a resource fee, so a zero-XLM account can produce this error even when it could cover the 100-stroop classic base fee; describe the required transaction fees instead of only the base fee.
Restrict simulation claims to Soroban transactions
every tx new command run simulation is incorrect for classic operations such as payment and change-trust; those are built, signed, and submitted without Soroban simulation. Restrict this sentence to Soroban flows, otherwise an agent will look for a simulation result the CLI never produces.
stellar tx fetch result --hash "$TX" --network testnet
```
**Never retry a timed-out write blindly.** On `transaction submission timeout` the RPC accepted the transaction but never reported a final status, so the outcome is unknown. It can still land later. The command exits 1 and `$TX` can be empty, exactly like a real failure. Take the hash from the stderr line `ℹ️ Signing transaction: <HASH>` (text mode only, since JSON mode writes nothing to stderr) and check `stellar tx fetch result --hash <HASH>`. If it is still not found, read both balances and the source account's sequence number before you decide. Only rebuild the payment once you have confirmed the first one did not land.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a "Stellar CLI for Agents" section at
docs/tools/cli/agent-cli/covering how to use the Stellar CLI and CLI Skills as an agent wallet. It includes a quickstart, the skills overview, seven cookbook guides (send tokens, balances and metadata, delegated spending, message signing, build and submit, x402 payments, USDT0 on mainnet), and four reference pages (architecture, authority model, output and errors, troubleshooting).The section sits in the Tools sidebar under Stellar CLI, directly below the Stellar CLI Manual, and in the Tools navbar dropdown directly below Stellar CLI. Subsections are collapsed by default.