brave-history
@readwithai - X - blog - machine-aided reading - 📖⚡️🖋️
Search Brave browser history from the command-line.
Caveats
This program uses the History sqlite database provided by Chrome. This is not updated immediately. I was getting delays in the order of 8 seconds when I tested this out.
mozeidon seems to give virtually instant data but requires considerably more configuarion than this tool which just works.
Motivation
History is useful; GUIs are irritating; the command-line has a lot of features.
People often remeber information about the pages they have visiting on the internet and then want to refer to it for further work, quote it, or share it. This is one of the values of the history functionality in most browsers, but using the GUI interface that browser provides can be time consuming and fiddly. The command-line has a number of utilities (include custom one's generated by the user) for interacting with data. Additionally the command-line makes it possible to use data once found.
Installation
You can install brave-history from PyPi using pipx.
pipx install brave-history
Usage
To search your history for some terms run:
brave-history github brave
This searches the url and the titleof the page.
brave-history has many flags, some not documented here, you can see this with brave-history --help
Alternatives and prior work
It should be noted that much of the tooling for Chrome can be adapted to Brave.
Brave exposes and sqlite database with history. You may prefer to access this directly for your use cases, particularly if you want to remove dependencies.
mozeidon is a command-line tool with a corresponding browser extension for Chrome which can fetch history, bookmarks and control tabs. I deemed the extension too heavy-weight for my purposes - it requires the installation of a browser extension, two command-line programs, and editing Chrome's configuration files. It does perform certain other functionality such as querying and interacting with tabs where there may be no alternative to using this approach.
References
About me
I am @readwithai. I create tools for reading, research and agency sometimes using the markdown editor Obsidian.
I also create a stream of tools that are related to carrying out my work.
I write about lots of things - including tools like this - on X. My blog is more about reading and research and agency.
Metadata
Release files for brave-history 1.2.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 | Actions |
|---|---|---|---|---|
| brave-history-1.2.0.tar.gz | 4.3 kB | Without provenance | Details for brave-history-1.2.0.tar.gz |
Release files / brave-history-1.2.0.tar.gz
| Download URL | brave-history-1.2.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c512fcde763a0e79a94a25951cf175156bacc004a5b1e85dc7adb20dd2dd4b1
|
|
BLAKE2b-256 checksum How to use checksums |
2ccef938e8ad0c055074e4309ac2983000b64a6e1b4e8d7ae117004c36ba4577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for brave-history 1.2.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.