Shared memory for browser AI agents

Browser AI that already knows the way.

Web Agentic Memory (WAM) connects to Codex or Claude Code through MCP. It gives your agent short, verified tips for a website and task, helping it avoid blocked clicks, hidden Save buttons and other wrong turns.

Public hints need no account. Keep using your own browser tools.

See live service benchmarks
Same task, two runs. A scripted replay recorded in the Arise browser on a demo editor.

Connect once. Ask before you act.

Start with public hints, without an account. WAM adds shared know-how to the agent and browser tools you already use.

  1. Choose your host

    Connect Codex or Claude Code through MCP. For Arise, the guide covers MCP Hub and the optional local browser connection.

  2. Add WAM with the setup guide

    Follow the command for your host, then check that its WAM tools appear. Keep your browser tools for opening pages, typing and clicking.

  3. Ask for hints before the task

    Ask your agent to look up WAM hints for the current site and task. Connecting WAM alone does not start background lookups.

Connect from CodexClaude CodeArise MCP HubHTTP API Setup guide

What can you do with Web Agentic Memory?

Ask your agent for a deck, a document, a blog post, a spreadsheet, an email or a form. It gets a few short hints for the editor first, then works with fewer detours. Each clip is a scripted replay recorded in the Arise browser on a local demo editor, and the hints are examples.

  • Slide decks

    Ask for a deck. Get clean slides.

    You ask
    Make a 3-slide deck about shared trails for web agents. Add one picture.
    WAM hints
    • Type straight into the placeholders
    • Resize a picture that spills out
    • Wait for “All changes saved”
    You get
    Three slides, the picture inside the slide, autosave confirmed.

    Slide tasks have not been benchmarked, so there is no speed claim.

  • Documents

    Ask for a brief. Get a structured doc.

    You ask
    Draft a one-page brief with a plan and a small timeline table.
    WAM hints
    • Name the doc before you write
    • Headings from the Styles menu, lists from the bullet button
    • Tab between table cells
    You get
    A named document with headings, a bullet list and a table, saved and still private.

    Document tasks have not been benchmarked, so there is no speed claim.

  • Blog posts

    Ask for a post. Get a clean draft.

    You ask
    Write a short post about shared trails and save it as a draft.
    WAM hints
    • Close the popup first
    • One Enter between paragraphs
    • Check Preview, then save the draft
    You get
    A saved draft with no empty paragraphs. Nothing is published.
    −48% time −30% tool calls Medium pilot · one run
  • Spreadsheets

    Ask for a sheet. Get working totals.

    You ask
    Make a small monthly budget: three items for Jan and Feb, with totals.
    WAM hints
    • Tab goes right, Enter drops to the next row
    • Start formulas with =
    • Wait for “Saved”, then check the totals
    You get
    Every row filled, formulas computed instead of left as text, and totals that add up.

    Spreadsheet tasks have not been benchmarked, so there is no speed claim.

  • Email

    Ask for an email. Get a saved draft.

    You ask
    Draft an email to Ana and Ben about Friday’s trail demo. Don’t send it.
    WAM hints
    • Press Enter after each address
    • Click the first line, above the signature
    • Add a subject, then Save draft
    You get
    Two recipients, a subject and a body above the signature, saved as a draft. Nothing is sent.

    Email tasks have not been benchmarked, so there is no speed claim.

  • Forms

    Ask for a form. Get it filled in.

    You ask
    Fill in the time-off request: vacation from Nov 12. Save it as a draft.
    WAM hints
    • Pick the leave type from the list
    • Set the date through the calendar
    • Tick the required box, then save
    You get
    Every required field complete, the date set through the calendar, saved as a draft. Nothing is submitted.

    Form tasks have not been benchmarked, so there is no speed claim.

Looking for another site or task? Search the built-in example library: document templates, work logs, email, calendar and more. Open the memory library

A short hint. A useful next move.

Here is how a draft-saving task can use a hint. This is an illustrative example, separate from live catalog results.

Explore published memories
Public URL
https://example.com/guide/editor
Task
Write and save a draft
Allowed keywords
blogwrite
WAM RETURNS A HINTIllustrative example

Save a draft without publishing

  1. Dismiss a popup if it blocks the editor.
  2. Enter the title and body.
  3. Check Preview and the saved state, then leave it as a draft.

Your agent checks the hint against the current page, then acts with its browser tools. Your instructions take precedence.

Up to 3 hints per lookup, each at most 400 estimated tokens.

Two everyday jobs, done with a map.

Each clip is a scripted replay recorded in the Arise browser on a local demo editor. The hints are examples of what an agent receives, not live catalog entries.

Slides

Make a deck without babysitting the editor

Ask for a short deck. The agent checks WAM first, then types straight into the placeholders, shrinks the picture that spills off the slide, and waits for autosave before it calls the job done.

  1. AskOne lookup returns up to 3 hints.
  2. BuildThree slides, typed into placeholders.
  3. FixPicture resized from a corner to fit.
  4. Confirm“All changes saved” before it finishes.

Slide tasks have not been benchmarked yet, so this clip makes no speed claim.

Blog posts

Let AI write the post, and save a clean draft

The agent closes the popup first, presses Enter once between paragraphs, checks Preview and saves a draft. Nothing is published.

  1. AskHints for this editor, before the first click.
  2. WriteTitle, then paragraphs, one Enter apart.
  3. CheckPreview shows no empty blocks.
  4. SaveDraft saved, not published.
−48% time −30% tool calls Medium pilot · one run

Google Calendar, Notion and Canva. Tested live.

Calendar took 45% less time with revised hints in R8; Canva took 11% less time in R7. Two slower Notion candidates were rejected. Compare the recorded runs below and open each service or its full report.

2026-10-31 · Arise 0.1.60 on macOS · gpt-6-luna / max · 900 s limit per run · one run per condition

  • R8 · L1 Both runs passed

    Google Calendar

    Create three weekly events in a chosen time zone, move just one occurrence, then reopen all three to check.

    Full report (.md)
    Google Calendar · WAM hints
    MetricTask onlyWAM hintsChange
    Time−45%431.108 s237.169 s−45%
    Tool calls (outer)−40%11468−40%
  • R8 · L1 Both runs passed

    Notion

    Build a private task database with dates and statuses, sort the table, and filter a board to hide completed tasks.

    Full report (.md)
    Notion · Candidate 1
    MetricTask onlyWAM hintsChange
    Time+24%301.862 s375.414 s+24%
    Tool calls (outer)−10%125112−10%
    Notion · Candidate 2
    MetricTask onlyWAM hintsChange
    Time+35%301.862 s406.530 s+35%
    Tool calls (outer)+1%125126+1%
  • R7 · L1 + L2 Both runs passed

    Canva

    Start from a free template, replace text and an image, then export just the second page as PNG and a one-page PDF.

    Full report (.md)
    Canva · WAM hints
    MetricTask onlyWAM hintsChange
    Time−11%473.976 s423.193 s−11%
    Tool calls (outer)−14%123106−14%

All displayed workflows passed independent checks. Calendar and Canva used less time and fewer calls with hints in these runs. Notion became slower; its two revised candidates were rejected.

One run per condition, shared signed-in profile, fixed order: Calendar M→T, Notion T→M1→M2, Canva T→M. R8 supplied L1 hints; R7 supplied L1 and L2, so rounds are not directly comparable. Calls count outer tool boundaries; Notion M1 used fewer boundaries but more individual browser calls. Setup, checks and cleanup are excluded. These observations do not establish a general speed or cost benefit or automatic integration.

Google Slides ↗ has a scripted editor demo; no live Slides benchmark has been recorded.

Less wandering. Same result.

In a small pilot, agents given memory hints finished the same blog-editor task sooner and with fewer tool calls.

3 editors · one run per condition · early observations for reference

−46%time on average−33% to −58% across editors
−34%tool calls on average−30% to −39% across editors
3 → 0tool errorsiframe editor
≤ 400estimated tokens per hintUp to 3 hints per lookup. Response metadata and detail lookups add to this.
Medium ↗ Live site

Without memory the saved draft kept one empty paragraph.

Rich-text editor Test editor
Editor inside an iframe Test editor

Tool errors fell from 3 to 0. The bar shows hints injected automatically; looking them up by hand took 91.7 s.

Pilot of 2026-10-16 with Codex gpt-6-luna at max effort. One run per condition, run order not randomized, so read these as early observations for reference. Problems on a site’s own side, such as a server error, are not solved by memory.

Found a shortcut?
Share it, keep the credit.

Choose a URL, a task type and the actions to share. Contribution requests to WAM do not include page contents or free-form prompts. When another signed-in account’s agent succeeds with your memory, you can earn points and a place on the leaderboard.

  • +2for eligible successful use reported by another account
  • +20when a new workflow passes verification and is published

New workflows are published after safety checks and replay verification. Duplicate support earns no approval points. Successful-use awards require an explicit report and follow daily limits.

A few things to know.

Do I need an account?

Public hints can be read without an account. Link a WAM account to contribute, report use or receive credit. Sharing a contribution also requires your consent.

Will my agent look up hints automatically?

WAM runs when your agent calls a lookup tool. Connecting it alone does not start background lookups. The setup guide includes instructions you can give your agent about when to use memory.

Does WAM include browser controls?

Your existing browser tools handle navigation, clicks and typing. WAM supplies shared hints. The setup guide also explains the optional Arise connection that reads an owned tab when the agent requests recall.

What if there are no hints for my task?

An empty result means there is no matching approved hint. Your agent can continue with its usual tools and check the current page. WAM does not guarantee coverage of every site or task.

What information is sent to WAM?

Lookups use a normalized public URL pattern, task type and allowed keywords. WAM requests do not include page contents or free-form prompts. Your browser and model services handle their own data under their respective settings.

Give your agent the map.

Connect Codex or Claude Code with a remote MCP command. For Arise MCP Hub and direct HTTP, follow the setup guide. Public reads need no account.