Talk in goals. Work in clear steps.
Describe your task in natural language. Keep the network, wallet context, parameters and approval steps visible in the resulting plan.
AI chat, crypto trading agents and local execution in one Windows workspace. Describe the task, review the plan and approve the operation.
A visual map of the conversation, operation plan and local execution boundary.
A plain-language instruction opens a reviewable workflow. Missing context stays visible.
Plan generation is not a signature. Provider acceptance is not confirmation. Review the actual result before retrying.
Follow a task from conversation to local signing and the submission lifecycle.
Static overview. Open the walkthrough to explore each stage.
Start with your goal. The conversation captures the task, not your private keys.
Turn the instruction into ordered operations with explicit inputs and dependencies.
Inspect the selected wallets, network, destinations and fee reserve together.
The approval boundary separates a proposed plan from permission to sign.
Signing remains on Windows. The selected provider receives the prepared submission, not your keys.
Inspect the provider response. Accepting the submission does not establish inclusion or execution.
Check whether the operation was included. An inclusion result still needs the relevant confirmation checks.
Review the actual confirmation state and each operation outcome before preparing another action or retry.
Describe your task in natural language. Keep the network, wallet context, parameters and approval steps visible in the resulting plan.
Bring transfers, token tasks, liquidity operations and private bundle preparation into a shared workflow instead of switching between disconnected tools.
Separate preparation, simulation, signing, submission and confirmation. Understand what has happened, what needs your approval and which result still needs checking.
Give the agent a specific goal and the wallet and network context it needs. Resolve missing inputs before moving on.
Keep amounts, destinations, permissions and execution limits explicit. Review the proposed actions instead of granting an open-ended mandate.
Inspect preparation and simulation separately from approval, local signing and submission. Check each returned outcome.
Review chain ID, wallet permissions, nonce, gas and the configured RPC or private-submission provider. Flashbots routes depend on chain and provider support.
Review accounts, token programs, blockhash validity, fees and the selected RPC or Jito route. Bundle acceptance, inclusion and confirmation are different states.
Local transaction signing and AI inference are different boundaries. Review the AI provider and what context it receives. Keep private keys, seed phrases and provider credentials out of chat. Protect your Windows device and verify every operation before approval.
Control stays visible.FRB is a non-custodial execution workspace for your wallets. It organizes network context, operations and approvals while transaction signing stays on your Windows device. You control the wallets and provider connections; FRB is not a hosted account holding your balance.
FRB connects AI chat to structured trading workflows: wallet and network context, a reviewable operation plan, approval and local execution. A chat response alone is not an executed trade.
No. Define the task and its boundaries, review the proposed actions and retain approval over signing. Do not treat an agent as an unrestricted mandate.
Local signing does not imply local AI inference. Review your chosen AI provider and the context sent to it. Never put private keys or seed phrases into a prompt.
No. Market prices, liquidity, fees, ordering and provider conditions still affect the outcome. Simulation, AI output and submission acceptance do not guarantee execution or returns.
FRB Agent runs on Windows. You can read these guides on mobile and copy the download link for your Windows computer. Use the matching EVM or Solana dashboard to connect the installed agent.