A few
clear answers.
Current capabilities, practical limits, and the difference between permission and payment.
What is Yosh?
An economic permission layer for agents, currently implemented as a local macOS system for bounded purchases of registered demo resources.
Is Yosh a wallet?
It includes a dedicated local spending wallet. Its central role is controlling authority to use that wallet through identity, grants, limits, pause state, and purchase records.
Does the agent receive my private key?
No. The wallet secret is stored in macOS Keychain and used by the local backend signer. MCP does not expose it or provide key-export tools. This does not protect against every compromised process on the same machine.
Can I connect my existing wallet?
Wallet import and Phantom signing are not implemented. Yosh creates or reuses its dedicated product wallet.
Is Yosh tied to x402?
Current purchases execute through x402. Authority is modeled separately, but alternative payment rails are not implemented.
Can multiple members share one budget?
Yes. Local members share daily authority while keeping separate credentials, grants, and purchase ownership. Codex is the current supported named host integration.
Does each member have its own authority?
Each member can have its own SpendGrant: total allowance, per-transaction limit, and expiry. It remains subject to shared daily authority. The grant total is cumulative over its lifetime; a daily reset does not reset it.
What happens when a request exceeds authority?
The current grant-based path records a denial without starting payment. A per-purchase exception approval flow is not implemented.
Can authority be paused or changed?
Pause new payments globally, change the daily limit, or replace or revoke a member’s grant. Grant changes rotate connection credentials and require MCP to reconnect. Pause does not reverse submitted transactions.
Does Approved mean complete?
No. Approval, payment confirmation, and delivery are separate facts. Default simulated requests can be approved without any payment.
What gets recorded?
Member ownership, request and resource information, amount, execution mode, decision and reason, payment state, delivery state, and available receipt or transaction information.
Does closing or locking the app pause payments?
No. Closing the window leaves the backend running, and the native PIN lock protects UI access. Use Payments to pause new payments. Normal quit stops the service safely.
Which network is supported?
The released Beta supports x402 V2 purchases on Solana Mainnet with native USDC for supported resources. It does not provide arbitrary wallet access or signing.
Is RWA supported?
No. Tokenized assets and broader investment permissions are exploratory directions, not current capabilities.
Where can I read the source?
Visit the Yosh source repository and begin with the README and MCP guide. Some published examples still describe older versions.
What if payment status is unknown?
The original record and reservation remain while the original payment is reconciled. Recovery does not create a replacement payment, and it does not guarantee delivery or refunds from every external API.
What happens after restarting?
Wallet, settings, members, and records remain. Active grants and connection credentials are revoked; reconnect and create new authority for new requests. Original pending payments remain eligible for reconciliation.