browse-now
Browser automation CLI for AI agents. Control your real browser from the command line with reliable element targeting through accessibility tree refs.
Part of Nowledge Mem - Personal memory for AI agents.
Now a compiled binary.
browse-nowships the Rust-builtbrowse-nowbinary instead of a Python module.pip install browse-nowdownloads a platform wheel that contains the compiled CLI and putsbrowse-nowon yourPATH. No Python runtime requirement beyond pip, and no Python dependencies. It drives your browser through the Nowledge Mem Exchange extension over the local WebSocket bridge the Nowledge Mem app already serves. The command surface is unchanged.
Why browse-now?
- Low overhead: No tool definitions loaded into LLM context (unlike MCP)
- Reliable targeting: Uses accessibility tree refs (
@e1,@e2) for high click reliability - AI-agent optimized: Designed for the
snapshot → click → repeatworkflow - Multi-browser support: Works with Chrome, Arc, Edge, and other Chromium browsers
Installation
pip install browse-now
The wheel bundles the compiled browse-now binary for your platform (macOS
arm64/x86_64, Linux x86_64/aarch64, Windows x64). It must still run on the same
machine as the Nowledge Mem app and the connected browser extension.
Prerequisites
- Nowledge Memory Exchange Chrome extension installed and active
- Nowledge Mem app running on the same machine (provides the local browser bridge)
Quick Start
# Navigate to a page
browse-now open https://example.com
# Get interactive elements with refs
browse-now snapshot -i
# textbox "Search" [e1]
# button "Submit" [e2]
# Click by ref
browse-now click @e2
# Fill input
browse-now fill @e1 "AI agents" --submit
# Show version
browse-now --version
Core Workflow
1. browse-now open <url> # Open page (isolated agent tab)
2. browse-now snapshot -i # Get refs [e1], [e2]...
3. browse-now click @e5 # Click by ref
4. browse-now fill @e3 "text" # Fill by ref
5. (If page changed) → snapshot -i again
For the full command reference (navigation, interactions, screenshots, tabs, multi-browser, JSON output) see mem.nowledge.co/docs.
Local-only security model
browse-now talks to the browser bridge endpoints exposed by the Nowledge Mem
app. Those endpoints are intentionally local-only: they are not exposed
through Access Anywhere, Cloudflare tunnels, or other remote-access paths.
browse-nowmust run on the same machine as the Nowledge Mem app- the controlled browser must also be on that same machine with the Exchange extension active
- publishing to PyPI makes the CLI easier to install, but does not turn browser automation into a remote-access surface
Documentation
- Full Documentation
- Nowledge Mem - Personal memory for AI agents
- Chrome Extension
License
Proprietary - see Nowledge Terms of Service
Metadata
Release files for browse-now 2.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| browse_now-2.10.0.tar.gz | 86.0 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| browse_now-2.10.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| browse_now-2.10.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| browse_now-2.10.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| browse_now-2.10.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| browse_now-2.10.0-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 15.3 MB
Release files / browse_now-2.10.0.tar.gz
| Download URL | browse_now-2.10.0.tar.gz |
|---|---|
| Size | 86.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e3ea50ed4ee6cc81c9b133bac638253a1da1d925b9c15b4233904a59740843c
|
|
BLAKE2b-256 checksum How to use checksums |
273603a2c6f8095150ddf903591fd2ef46b94c5be4c895c702001b64448407da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logRelease files / browse_now-2.10.0-py3-none-win_amd64.whl
| Download URL | browse_now-2.10.0-py3-none-win_amd64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6f9ea77e3cd665c111d8bf87203ee771de961d94ff6ed66bece8bc99466cfd30
|
|
BLAKE2b-256 checksum How to use checksums |
af96b265cc49540160727e8291b1a53fca114c340f1a4f6eab0b1b18f11fe88b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logRelease files / browse_now-2.10.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | browse_now-2.10.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
b9833da28c082ce15ffec47269fc06d9e46fb72b029a16281157e6796cf53a2c
|
|
BLAKE2b-256 checksum How to use checksums |
35a1b12437e2fdfd599222a7c09a931fc6e0d884f2809400f6d34f155457bb58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logRelease files / browse_now-2.10.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | browse_now-2.10.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
4c4421c1b4debb25dc8174a1614e39820de0d49eb95d41bf86e12539feed631d
|
|
BLAKE2b-256 checksum How to use checksums |
4dcaf42dfafff5486a60247de73b26237811cb45a28b31431e96a12d2d32c041
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logRelease files / browse_now-2.10.0-py3-none-macosx_11_0_arm64.whl
| Download URL | browse_now-2.10.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
29016916728b715d925ad2696bdfa787b322346dfa89ab7a5642b3d139accda7
|
|
BLAKE2b-256 checksum How to use checksums |
f7aed12fb0d20859032ee6de170f481b7a249c843344444b53b6c5883ac3cc68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logRelease files / browse_now-2.10.0-py3-none-macosx_10_12_x86_64.whl
| Download URL | browse_now-2.10.0-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
53f28d0b1c394c2982ebbf83f7bc01f5a454028acea5beec3fcc51d711bfbbc3
|
|
BLAKE2b-256 checksum How to use checksums |
fdd50fe498d86cc6634a426c3d7b9d3ab33e73599ef31c9f9edea824214c9881
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logSecurity for browse-now 2.10.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for browse_now-2.10.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.