GlowIDE

Every scenario DeepQA drove in the browser, in plan order, with the 33 screenshots it captured along the way. A passing scenario is evidence too.

1. S1

   Load primary routes and observe console errors

   5 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Navigated to /chat; page loaded with chat options, prompt input, and sidebar navigation intact.
   • Navigated to /wallet; wallet portfolio balance, asset breakdown (USDC, EURC, cirBTC, USYC), and action buttons loaded correctly.
   • Navigated to /defi; Stablecoin DeFi dashboard rendered with TVL metrics, action cards, and top pools.
   • Navigated to /chat: Chat interface, prompt suggestions, wallet address badge, and AI model selectors rendered cleanly with no broken components or error overlays.
   • Navigated to /wallet: Wallet portfolio overview, asset balances (USDC, EURC, cirBTC, USYC), and transaction action buttons loaded successfully without errors.
   • Navigated to /defi: Stablecoin DeFi dashboard rendered with TVL metrics, 24h volume, APY metrics, and liquidity pools.
   • Navigated to /editor: Web3 IDE editor loaded complete with file explorer, tools sidebar, editor pane, and initialized interactive bash terminal.
   • All primary routes (/chat, /wallet, /defi, /editor) loaded their respective UIs without triggering unhandled exceptions or broken visual states.
2. S2

   Send testnet asset via Wallet

   5 steps, 3 screenshots

   high⊘ blocked

   

   

   

   • Navigated to the Wallet page showing a portfolio balance of $4.63 with 2.895928 USDC available on Arc Testnet.
   • Opened the Send USDC modal with recipient and amount inputs.
   • Entered recipient address 0x000000000000000000000000000000000000dEaD and amount 1 USDC into the send form.
   • Navigated to the Wallet page at /wallet where the Arc testnet account and token [redacted] (2.895928 USDC) were loaded.
   • Clicked the Send button to open the Send USDC modal.
   • Entered a valid EVM recipient address 0x000000000000000000000000000000000000dEaD and amount 1 USDC.
   • Clicked 'Review Transfer' which successfully advanced to the transfer summary review screen showing 1 USDC to 0x000000000000000000000000000000000000dEaD on Arc Testnet.
   • Tool call budget was reached before the final 'Confirm & Send' submission could be triggered and its on-chain / UI success confirmation observed.
3. S3

   Send token using MAX shortcut to verify gas reservation

   5 steps, 3 screenshots

   high✕ fail

   

   

   

   • Navigated to the Wallet page showing a portfolio balance including 2.895928 USDC.
   • Opened the Send USDC modal with Recipient and Amount inputs.
   • Navigated to the /wallet route where the user portfolio displays a native gas USDC balance of 2.895928.
   • Clicked the Send button to open the Send USDC modal.
   • Entered a valid recipient address (0x70997970C51812dc3A010C7d01b50e0d17dc79C8) into the recipient input field.
   • Clicked the 'Max' shortcut button beside the Amount input.
   • The Max button failed to populate the Amount input field with the maximum sendable USDC balance (with gas reservation deducted), leaving the amount input at 0.00 and the 'Review Transfer' submit button disabled.
4. S4

   Swap native USDC on DeFi DEX

   5 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to /defi showing the Stablecoin DeFi dashboard.
   • Selected the Swap tab on the DeFi page displaying the Swap Stablecoins interface.
   • Selected USDC to EURC swap pair and entered 1 as amount, enabling the Swap Stablecoins button.
   • Navigated to /defi and clicked the Swap tab.
   • Configured the swap parameters by selecting USDC in the 'From' field and EURC in the 'To' field.
   • Entered '1' into the pay amount input, which updated the rate calculations and enabled the 'Swap Stablecoins' button.
   • Submitted the swap form, successfully initiating the swap transaction with the status feedback: 'Swap via Circle Programmable Wallets — approve in wallet'.
5. S5

   Load a starter project into the IDE

   3 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated to Arc Lab at /build showing starter templates across multiple categories.
   • Clicked ERC20 Token [redacted]; URL redirected to /editor and workspace opened with 'erc20-token' project and 'MyToken.sol' Solidity file.
   • Navigated to /build displaying Arc Lab starter project templates across categories.
   • Clicked the 'ERC20 Token' starter template card ('Load into Editor').
   • The URL successfully transitioned to /editor with status message indicating 'erc20-token' loaded.
   • In /editor, the 'erc20-token' project workspace opened with 'MyToken.sol' visible and active in the Solidity editor.
6. S6

   Compile and Deploy a contract to Arc testnet

   3 steps, 1 screenshot

   high⊘ blocked

   

   • Navigated to /editor where file explorer shows MyToken.sol in the erc20-token [redacted]
   • Navigated to /editor and observed the file explorer and terminal interfaces.
   • The project erc20-token [redacted] MyToken.sol is present in the File Explorer tree, but the file item is rendered without an interactive file selection button or clickable trigger in the DOM, preventing opening the file directly into the code editor buffer.
   • Navigated to Arc Lab (/build) and clicked 'Load into Editor' on the ERC20 Token [redacted] project; the status confirmed project load but returning to the editor still showed 'No file open' with no contract source active for the Deploy & Run tool within the execution turn limit.
7. S7

   Validate Recipient Address on Send Token form

   5 steps, 2 screenshots

   medium✕ fail

   

   

   • Navigated to /wallet page showing Portfolio Balance and asset list.
   • Opened Send USDC modal with recipient address and amount inputs.
   • Navigated to the /wallet route and opened the Send USDC token [redacted] modal.
   • Entered 'invalid-address-string' into the Recipient address field and '1' into the Amount field.
   • The application enabled the 'Review Transfer' button without validating the recipient address format or showing an inline error.
   • Clicking 'Review Transfer' proceeded directly to the confirmation screen with 'To: invalid-address-string' ready for submission.
8. S8

   Validate empty Pay Amount on DeFi Swap

   4 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Navigated to /defi and observed the DeFi overview dashboard.
   • Selected the Swap view on DeFi page; observed the Pay Amount field is empty/placeholder '0.00' and the 'Swap Stablecoins' button is disabled.
   • Leaving the Pay Amount field empty keeps the 'Swap Stablecoins' submit button disabled, preventing empty or 0-value swap submissions.
   • Navigated to /defi and selected the 'Swap' tab.
   • Observed that when the Pay Amount field is empty, the 'Swap Stablecoins' submit button remains disabled.
   • Entering an amount enables the button, and removing/clearing the amount disables the button again.
   • Attempting submission with empty amount is blocked, preventing empty or 0-value swap transactions.
9. S9

   Import an existing deployed contract

   6 steps, 3 screenshots

   medium✕ fail

   

   

   

   • Navigated to /deployments where the Deployed Contracts list is displayed.
   • Navigated to /deployments and opened the 'Add Contract' modal dialog.
   • Entered valid contract address '0x1234567890123456789012345678901234567890', contract name 'My Test Contract', and a valid JSON ABI array.
   • Submitted the form by clicking 'Add Contract'.
   • Toast notification 'Contract added to dashboard' was displayed.
   • However, the viewable deployments list remained empty showing 'No contracts found' under both 'My Contracts' (default filter where deployer address did not match the connected wallet 0x28C2...39AF) and failed to render in the user's active view.
10. S10

    Validate required fields on Add Contract form

    5 steps, 3 screenshots

    medium✓ pass

    

    

    

    • Opened the Add Contract modal on the Deployments page; the Add Contract submit button is initially disabled.
    • Leaving Contract Address empty and attempting to submit or check validates the required address field: the Add Contract button remains disabled and clicking Check shows 'Invalid address format'.
    • Navigated to the Deployments page and clicked the 'Add Contract' button to open the modal.
    • Verified that with the Contract Address field empty and Contract Name set to 'Test Name', the 'Add Contract' submit button is strictly disabled.
    • Attempting to validate or check with an empty address displays an explicit validation message 'Invalid address format' and prevents submission without creating any blank or corrupt records.
11. S11

    Update and persist Editor preferences

    5 steps, 3 screenshots

    low✓ pass

    

    

    

    • Navigated to Settings and selected the Editor tab displaying initial editor preferences (VS Dark theme, 14px font size).
    • Selected High Contrast theme and changed font size to 18px.
    • Navigated to Settings (/settings) and switched to the Editor preferences tab.
    • Initial preferences were Theme: VS Dark, Font Size: 14px.
    • Updated the theme selection to High Contrast and font size slider to 18px.
    • Clicked Save Changes, which successfully applied and disabled the save button indicating changes were saved.
    • Observed the modified font size (18px) and High Contrast theme active in the Editor Preferences form.
12. S12

    Submit query to AI assistant

    3 steps, 3 screenshots

    low✕ fail

    

    

    

    • Navigated to /chat and observed the chat input interface.
    • Navigated to /chat and observed the chat assistant input form.
    • Entered a Web3 prompt 'How do I write a simple ERC-20 token [redacted] in Solidity?' into the prompt textarea.
    • Submitted the prompt; the conversation was created and listed in history, navigating to /chat/tsyakt4reamu5x1ndg.
    • The AI assistant failed to generate a response and instead returned an error message indicating '❌ OpenRouter API key not set. Add OPENROUTER_API_KEY to Vercel env vars or set it in Admin → Settings.'.

Findings that survived the Critic's audit. Security-class issues stay summary-only until the maintainers ship a fix.

highconfirmed ✓functionalF1 · S3

Max shortcut button in Send USDC modal is unresponsive and does not populate amount

I followed the steps, entered a recipient address, and clicked the 'Max' button. The Amount field remained '0.00' and the 'Review Transfer' button remained disabled. The page reported 1 console error during the scenario.

Expected

Clicking 'Max' populates the amount input with the maximum available USDC balance minus estimated gas fees.

Actual

Clicking 'Max' has no effect: the Amount field remains empty/0.00 and the 'Review Transfer' button remains disabled.

Repro · 4 steps

1. Navigate to /wallet
2. Click the 'Send' button under the portfolio balance card to open the Send USDC modal
3. Enter a valid recipient address into the 'Recipient' field
4. Click the 'Max' button next to the Amount field

S3-7.pngS3-12.png

highconfirmed ✓functionalF2 · S7

Send Token modal accepts invalid recipient address and advances to confirmation

The observation shows the application accepted 'invalid-address-string' in the address field and proceeded to the review screen without validation errors. The live replay was inconclusive: The replay ran out of tool calls before it reached the reported state. The page reported 1 console error during the scenario.

Expected

The form should validate that the recipient is a valid Ethereum/Arc address (0x format, 40 hex chars), prevent progression, and display an inline validation error.

Actual

The form enabled 'Review Transfer' and allowed proceeding to the 'Review Transfer' / 'Confirm & Send' step with the invalid address string without any error message.

Repro · 5 steps

1. Navigate to /wallet
2. Click the 'Send' button to open the token transfer modal
3. Enter 'invalid-address-string' into the recipient address field
4. Enter '1' into the amount field
5. Click 'Review Transfer'

S7-5.pngS7-7.png

highconfirmed ✓functionalF4 · S12

AI Chat fails to respond due to missing OpenRouter API key configuration

I navigated to the chat page, entered a prompt asking how to write a simple ERC-20 token [redacted], and submitted it. The AI assistant replied with '❌ OpenRouter API key not set. Add OPENROUTER_API_KEY to Vercel env vars or set it in Admin → Settings.', matching the reported bug. The page reported 1 console error during the scenario.

Expected

The AI assistant responds with a relevant answer/code in the chat stream.

Actual

The AI assistant returns an error message: '❌ OpenRouter API key not set. Add OPENROUTER_API_KEY to Vercel env vars or set it in Admin → Settings.'

Repro · 3 steps

1. Navigate to /chat
2. Enter a prompt into the chat textarea (e.g., 'How do I write a simple ERC-20 token contract in Solidity?')
3. Click the submit button or press Enter to send the prompt

S12-1.pngS12-5.pngS12-8.png

mediumconfirmed ✓functionalF3 · S9

Imported contract does not appear in default 'My Contracts' deployments list when deployer address is not populated

The observation confirms that after receiving a success notification for adding the contract, it failed to render in the user's active view. The page reported 1 console error during the scenario.

Expected

The newly added contract appears in the user's viewable deployments list.

Actual

Notification 'Contract added to dashboard' appears, but the deployments list remains showing 'No contracts found'.

Repro · 4 steps

1. Navigate to /deployments
2. Click the 'Add Contract' button
3. Enter contract address '0x1234567890123456789012345678901234567890', name 'My Test Contract', and ABI JSON array '[{"inputs":[],"name":"name","outputs":[{"internalType":"string","name":"","type":"string"}],"stateMutability":"view","type":"function"}]'
4. Click 'Add Contract' to submit

S9-11.png