A little context.
A clearer next move.

Meet your sidekick.

Start with a specific task. Check a public wallet’s native balance, inspect a token contract, request a route quote, or screen a URL’s structure. Priv Agents chooses a tool and presents the result for your review.

Guided mode works without model credentials. The included Zeline Python worker provides a real LLM tool-calling loop after the operator configures a provider. A fixed read-only allowlist controls its tools. Monitoring supports explicitly created recurring balance and contract watches while the worker is online. Private execution and automated trading remain unavailable.

Robinhood Chain is the default network. Ethereum and Base are also available in the network selector. Each capability depends on the selected network’s RPC provider and the route provider’s current support. The public Robinhood RPC is rate-limited; a dedicated provider is needed for production capacity.

What’s live, clearly.

Quotes are a review step.

Swap and bridge requests use LI.FI’s quote endpoint and require a source wallet address. The result includes the route, estimated received amount, minimum received, slippage, estimated gas, and provider-reported fees. A missing route is reported as unavailable. The workspace does not submit swaps or bridge transactions.

Checks have limits.

Contract inspection reads deployed bytecode and contract-reported metadata. It is not an audit. URL screening examines the address text for a small set of suspicious patterns. It does not visit the page, check malware, simulate transactions, or establish that a website is safe.

Your wallet. Your call.

Priv Agents connects to an injected EVM wallet only after you click Connect wallet. It never requests a seed phrase or private key. Connecting requests access to an address; it does not grant a token allowance or delegated spending permission.

The native ETH transfer flow checks the selected chain, validates the address and amount, estimates gas through your wallet, and shows a review. Only “Confirm in wallet” requests a transaction signature. Your wallet displays the final fee and transaction details.

A transaction hash means submitted, not confirmed. Use Check status or the network explorer to verify the receipt. An unknown result should be investigated before another transfer. This version does not automatically retry a submitted transaction.

Privacy has different guarantees.

Recipient-only stealth native ETH payments are implemented in the Privacy workspace. The sender generates a fresh address using the recipient’s public meta-address. Only the recipient’s local spending and viewing keys derive its spending key. The browser uses the pinned ScopeLift stealth-address SDK. No key is given to the agent, server or LLM.

The source wallet, amount, one-time address and later spending are public. This does not hide the sender or amount and is not a shielded transfer or private bridge. A public funding transaction is used explicitly for recipient-address privacy, with a separate review and signature.

This build uses receipt-based discovery, not onchain announcements or a registry. The sender must download and give the recovery receipt to the recipient; the recipient must keep their encrypted private vault backup and passphrase. Later spending to a known address can reveal a link. Wallet RPC providers see the one-time addresses queried. Importing arbitrary vaults or receipts never changes the derived ownership requirement.

Native ETH is supported in source for Robinhood, Ethereum and Base. Browser logic has been tested against an isolated local EVM. Real wallet, RPC and mainnet checks remain necessary before production use. No production funds were used during development.

Shielded transfers and private bridge.

These are not integrated. Existing RAILGUN deployment references cover Ethereum, Arbitrum, Polygon and BSC; this application has no verified native Robinhood shielded deployment. A complete private route needs its own protocol, proof, key, relayer and chain verification. See PRIVATE_GUIDE.md in the source package for the implemented payment flow and limitations.

A shielded route has visible edges.

In a shielded system, a deposit can reveal the depositing address, token, and amount. Private transfers may use encrypted notes and zero-knowledge proofs to verify valid spending without publicly revealing the full relationship between participants. The exact guarantees depend on the protocol and how it is used.

Unshielding exposes the public receiving address and amount. Timing, token amounts, relayer behavior, application logs, and cross-chain legs can create correlations. A private swap can still expose the external DEX interaction. A private bridge requires a review of every leg, including the destination and exit.

A private relay is different.

A relay can reduce exposure before transaction inclusion and help with some mempool concerns. It does not make a settled public transaction confidential. MPC wallets protect signing keys; they do not, by themselves, hide activity on a public blockchain.

Priv Agents will never silently replace a requested private route with a public transfer. The agent itself does not generate a proof or move funds. The separate stealth workspace requires an explicit recipient-privacy review.

A place for context.

Tasks submitted to the guided agent endpoint may include the task text, selected chain, and connected public address. Read requests go to the selected public RPC provider; route requests go to LI.FI. Do not put secrets into tasks.

Activity is stored locally and unencrypted in this browser. AI-mode conversation transcripts, monitoring jobs, and snapshots are also stored in the worker’s SQLite databases, separate from the encrypted Memory vault. AI task text and relevant public addresses are sent to the configured model provider. A server-generated device session scopes worker state; clearing that cookie removes this browser’s access to the old scope. It may contain task text, public addresses, tool results, and transaction hashes. You can export it as JSON or clear it from Activity. It is not synced across devices.

Encrypted memory.

Memory uses AES-GCM with a fresh random IV for each save. A non-exportable key is derived from your passphrase using PBKDF2-SHA-256 with 250,000 iterations and a random salt. Only ciphertext, the salt, and the IV are stored locally. Notes are not sent to the task endpoint.

The passphrase and unlocked notes exist in the current browser session. Lock the vault when finished. Encryption at rest does not protect an already unlocked session or a compromised browser. There is no recovery service, and clearing browser storage deletes the local vault. Do not use it for seed phrases or private keys.

The building blocks.

We’re studying existing protocols and agent tooling as integration candidates. Some provide integration references. Zeline core and selected comparison utilities are vendored under their upstream license; no partnership is implied.

Community

The official X account and domain have not been configured. The operator can set NEXT_PUBLIC_X_URL to the verified account URL before building. Use links from the official website once announced.