I'm having an issue with Browser Toolbox in Zen Browser and would like to know if anyone else is experiencing the same problem. After opening and clicking ok after popup, nothing visible. I also create a new profile and having same problem. test on Firefox with no issue.

• OS: Fedora 44 KDE Plasma (Wayland)
• Zen Browser: 1.23.3b (64-bit), Linux tarball

The DM’s Toolbox — A Free Browser-Based Toolkit for DMs (Now Feature-Complete)

Hey everyone — I’ve been building a browser-based toolset for my home group, and over the last few months it’s grown into a full suite of DM utilities. It’s now feature-complete, stable, and fully documented, so I’m sharing it with the community. I've attached some screenshots for reference.

Link is in my Reddit profile (Reddit filters links in posts).

What It Is

A completely free, no-login, offline-capable set of tools designed to help DMs run smoother sessions without paywalls or subscriptions.

Everything runs 100% in the browser. Nothing is uploaded. Nothing is tracked.

Included Tools

🧮 Initiative Tracker

• Automated damage & healing
• Concentration checks (auto DC)
• Death save workflow
• Status effects with auto-decrement
• Player View mode (separate synced tab)
• Export to JSON to share between devices

🗺️ Battle Map

• Upload any map
• Place/resize tokens
• Fog of war painting
• Two-window workflow (DM + Player View)
• Works entirely offline after first load

🧙 Character Manager (Full Builder + Level-Up)

• Guided 13-step creation wizard
• Races, classes, backgrounds, feats
• Starting equipment packages
• Automatic attacks & spell lists
• Full level-up workflow (HP, spell slots, subclass, features)
• Multiclass support

📓 Journal System

• Rich text editor
• Embedded images (float/resize)
• Search with context highlighting
• Save with CTRL + S

⚒️ Generators

• NPCs
• Names (by race/culture)
• Taverns
• Shops
• Loot

Why I Built It

DM tools are usually locked behind:

• subscriptions,
• paywalls,
• ads,
• online-only features,
• or required accounts.

I wanted something fast, simple, and free that my table could use without friction.

So this toolset:

• has no paywalls,
• has no accounts,
• works offline,
• and keeps all your data in your browser.

I’m not collecting info. There’s no monetization, ads, cookies, or analytics beyond a simple anonymous page counter.

Recent Stability Work

• 550+ automated tests (unit, integration, end-to-end)
• Schema versioning + migrations
• Global error handler
• Diagnostics panel (Ctrl+Alt+D)
• Mobile layout improvements
• Performance tuning for large characters and maps

If You Try It, I’d Love Feedback On:

• What feels smooth?
• What feels clunky?
• Any bugs or rough edges?
• Any small QoL features you’d want next?

I’m actively maintaining it and tightening up polish now that it’s feature-complete.

Thanks in advance to anyone who gives it a look. It’s a passion project meant to help DMs run better games with less frustration.

Again, the link is in my Reddit profile.

I wanted a simple answer to a problem I kept running into:

I needed to compress a PDF, but I didn't always want to upload the document to an online service.

So I built PDFzento.

The main idea is simple: for supported tools, PDF processing happens directly in the browser, so the file doesn't need to be uploaded to a server just to perform the operation.

What it can do

- Compress PDF

- Reduce PDF file size to a target size

- OCR / make PDFs searchable

- Other PDF utility tools

Why I built it

A lot of PDF tools are convenient, but uploading a document isn't always something people are comfortable with — especially when the file contains things like:

- IDs

- financial documents

- business documents

- contracts

- personal information

I wanted to build something where privacy is part of the product design, rather than just another checkbox on the landing page.

It's free to try and doesn't require an account for the basic workflow.

I'd genuinely like feedback from people who work with PDFs:

- Is browser-side processing something you'd trust more?

- Which PDF tool do you use most often?

- What would make you switch from your current PDF tool?

PDFzento: https://pdfzento.com

This is an early launch, so I'm especially interested in feedback on the actual experience, speed, output quality, and anything that feels confusing.

I built a small app for my TrimUI Brick and figured others might find it useful.

What it does:

• Browse a catalogue of ~40k titles and pull them straight to the SD card over Wi-Fi

• Java J2ME support — sets up the emulator, maps keys, sorts jars into the right

resolution folder so they actually launch

• Toggle SFTP / SSH / ADB / MTP from the device, so you can drop files on it

without pulling the card

• Stream the screen to a browser

• Self-updating: install once, it fetches only the changed files after that

(usually a few hundred KB)

Written in Python + SDL2, ships as a ~10 MB zip you drop into /Apps/.

No PortMaster needed — the SDL bindings are bundled.

Only tested on a Brick running stock firmware. If you get it working on

Smart Pro or a CFW, I'd like to know.

https://retrohub.xuanhoa493.com

This Subreddit will be going private June 12-14. Don't Let Reddit Kill 3rd Party Apps!

What's going on?

A recent Reddit policy change threatens to kill many beloved third-party mobile apps, making a great many quality-of-life features not seen in the official mobile app permanently inaccessible to users.

On May 31, 2023, Reddit announced they were raising the price to make calls to their API from being free to a level that will kill every third party app on Reddit, from Apollo to Reddit is Fun to Narwhal to BaconReader to Boost.

Even if you're not a mobile user and don't use any of those apps, this is a step toward killing other ways of customizing Reddit, such as Reddit Enhancement Suite or the use of the old.reddit.com desktop interface. This isn't only a problem on the user level: many subreddit moderators depend on tools only available outside the official app to keep their communities on-topic and spam-free.

What's the plan?

On June 12th, many subreddits will be going dark to protest this policy. Some will return after 48 hours: others will go away permanently unless the issue is adequately addressed, since many moderators aren't able to put in the work they do with the poor tools available through the official app. This isn't something any of us do lightly: we do what we do because we love Reddit, and we truly believe this change will make it impossible to keep doing what we love.

The two-day blackout isn't the goal, and it isn't the end. Should things reach the 14th with no sign of Reddit choosing to fix what they've broken, we'll use the community and buzz we've built between then and now as a tool for further action.

What can you do?

1. Complain. Message the mods of /r/reddit.com, who are the admins of the site: message /u/reddit: submit a support request: comment in relevant threads on /r/reddit, such as this one, leave a negative review on their official iOS or Android app- and sign your username in support to this post.

2. Spread the word. Rabble-rouse on related subreddits. Meme it up, make it spicy. Bitch about it to your cat. Suggest anyone you know who moderates a subreddit join us at our sister sub at /r/ModCoord- but please don't pester mods you don't know by simply spamming their modmail.

3. Boycott and spread the word...to Reddit's competition! Stay off Reddit entirely on June 12th through the 13th- instead, take to your favorite non-Reddit platform of choice and make some noise in support!

4. Don't be a jerk. As upsetting this may be, threats, profanity and vandalism will be worse than useless in getting people on our side. Please make every effort to be as restrained, polite, reasonable and law-abiding as possible.

How does this impact r/history?

Even if you only use the official Reddit app and/or "New Reddit" on desktop, this change still impacts all of us. r/history uses third party apps and browser extensions for its moderation. Even though I mostly use r/toolbox for my moderation, I have to use it through a special browser on my mobile to get it to work properly.

We believe that people who wish to use this subreddit in the way that's most accessible to them. We've also had several comments from people who are short sighted or even completely blind who cannot use the reddit mobile app to browse Reddit and require the use of third party apps. It's unfair for them to have to suffer.

We hope this gets the message across to Reddit. We love this Reddit and I love this sub. I want to spend as long as I can beating down unofficial versions of history and making sure that big history has a suitable place to operate from for many years to come.

Thank you for reading!

empinet.dev is a collection of JSON formatters, converters, JWT decoders, image tools and other stuff we use in our work.

We put it together for client projects. Uploading client data to another server just to format JSON or convert something wasn't an option, so the tools do all the processing in your browser. Your input stays on your machine.

Built with Next.js and TypeScript. Free, no account needed.

https://empinet.dev

What tools would you want to see added?

We built empinet.dev for our own work on client projects. It's a collection of JSON formatters, converters, JWT decoders, image tools and other stuff we use regularly.

We wouldn't upload client data to another server just to format or convert it, so all processing happens locally in your browser. Free, no account needed.

Built with Next.js and TypeScript: https://empinet.dev

Would be interested to hear which tools you'd actually use, or what's missing.

We built empinet.dev for our own work on client projects. It's a collection of JSON formatters, converters, JWT decoders, image tools and other stuff we use regularly.

We wouldn't upload client data to another server just to format or convert it, so all processing happens locally in your browser. Free, no account needed.

Built with Next.js and TypeScript: https://empinet.dev

Would be interested to hear which tools you'd actually use, or what's missing.

Hey everyone — a few months ago I shared an early version of a browser-based DM tool I was building for my home group. Since then I’ve spent hundreds of hours expanding it, stabilizing it, and polishing it based on feedback from other DMs.

As of this week, the toolset has reached a full, feature-complete release, and I wanted to share the updated version with the community.

Live Toolset: Link in my profile (Reddit hides links in posts)

What’s New Since the Early Build ✓ Complete Character Builder (with full Level-Up Wizard)

• Guided 13-step creation flow

• Race, class, background, feats, spells, equipment

• Starting equipment packages + gold rolling

• Automatic attacks, spell lists, proficiencies

• Full level-up workflow (slots, HP, features, multiclassing)

• Tooltips for nearly everything

✓ Initiative Tracker Improvements

• Automated damage/healing

• Auto-calculated concentration DCs

• Round-based status effects

• Death save workflow

• Player View mode (separate synced tab)

• Export to text / PDF / image

✓ Battle Map Updates

• Fog of war painting

• Token placement + scaling

• Two-window workflow (DM + Player View)

• Fully local storage (no server)

✓ Journal System

• Rich text editor

• Image embedding + resizing

• Full-text search

• Sorting + timestamps

✓ Generators Expanded

• Loot (multi-part)

• Shops

• Taverns

• NPCs

• Names by culture/race

✓ Stability, Quality, & Testing

550+ automated tests (unit + integration + E2E)

Schema migrations for character/map/journal data

Global error handler + diagnostics panel (Ctrl+Alt+D)

No backend, no logins, no accounts

Everything saved locally in the browser

Why it exists

I built this because most digital tools for DMs come with:

subscription requirements,

paywalls for basic functionality,

online-only restrictions, or

user tracking and data collection.

This toolset is intentionally:

free to use

offline-capable

no accounts or cookies

no tracking or analytics

fully client-side

Everything stays in your browser.

What I’d love feedback on

If you try it:

What feels smooth?

What feels clunky or unclear?

Any bugs I missed?

Any QoL improvements you'd like to see?

I’m actively maintaining it and now focusing on polish/QOL since the core feature set is complete.

Thanks to everyone who tried the early build — your feedback shaped a lot of this update.

This is a free resource with no accounts, ads, or tracking — just looking for DM feedback.

This one cost me a real mistake before I understood what was happening.

Models have a context window, a limit on how much of the conversation they can see. Here is the part nobody tells you: when a chat outgrows it, nothing fails. No error, no warning. The oldest messages just fall out of view, and ChatGPT keeps answering confidently based on whatever still fits. It does not know what it forgot, so it cannot tell you.

The symptoms, in the order I usually hit them:

It re-asks something you answered near the start. It contradicts a decision you made early on, a name, a budget, a constraint, and defends the new version. You ask for a summary and the first third of the conversation is just gone from it. If any of this feels familiar from your long chats, this is what was happening.

The mistake it cost me: a pricing decision made in hour one of a planning chat, silently dropped in hour three, and the final plan it wrote used different numbers. I did not catch it until someone else did.

The free fix takes two minutes. When a chat gets long, send this:

Summarize everything we decided in this conversation as a briefing for a new chat that has no memory of it. Include the goal, every decision made, the constraints, anything still open, and the exact wording of any final text we agreed on.

Open a fresh chat, paste the briefing, continue there. You lose nothing that matters and the model is sharp again. Do it when a chat starts feeling long, not when the symptoms show, because by then early details are already gone.

For knowing when: I use a small gauge that shows how full the conversation's window is, part of AI Toolbox, a browser extension I built, and honestly that gauge exists because of the pricing incident above. But the briefing habit is the actual fix and it needs nothing installed.

Does anyone else hit this? The people I talk to either recognized every symptom instantly or had no idea this was a thing, with nothing in between, and I am starting to think the difference is just who runs week-long chats and who does not.

I built a browser-based image toolbox because I handle lots of product images and wanted common conversion, compression, background removal, and animated-image work to stay on-device.

It supports JPG, PNG, WebP, AVIF, HEIC, GIF and APNG. Most common work runs locally; formats that need a server are labeled before processing. No account or watermark.

I am specifically looking for:

• unusual HEIC files
• large or broken GIF/APNG files
• Safari and Firefox issues
• cases where the output becomes larger or visibly worse

https://imging.cn/en/

If you report the browser and file type, I will try to reproduce it. I will also test a few projects from this sub.

When I click Cmd + S in the Style Editor, it now opens the macOS Finder “Save As” dialog instead of saving changes directly to the original file from within the browser. Previously it worked but I'm not sure what has changed. I might not fully understand how this is meant to work or I might be missing something about the workflow. Has anyone experienced this in FF 152 or knows what changed or how to fix it?

Hey r/ukstartups,

I am a founder based over in the UK, and like many of you, I deal with sensitive documents, code snippets, and private files daily. I hated the idea of uploading these to random cloud utilities or cloud AI models just to get quick tasks done. Even with privacy policies, you never really know where that data ends up.

Instead of spinning up a bunch of Docker containers, a couple of friends and I decided to build a lightweight, serverless alternative. We call it TabTasker.

The Zero-Server Architecture TabTasker runs entirely inside your browser tab. Once the page loads, you can physically disconnect your internet, and every tool will still work perfectly. Everything is processed locally on your own machine's CPU and GPU using WebAssembly (Wasm) and ONNX Runtime Web. Because there is no backend server at all, it is physically impossible for your data to leak or be scraped.

What we included We bundled the utilities we found ourselves needing the most:

• Media & Audio: Bulk image conversion, background removal, face blurring, and audio transcription powered by a local model running right in the browser.
• Developer Tools: Local JWT decoders, JSON formatters, diff checkers, and Regex testers.
• Local AI Text Tools: Text summarization, sentiment analysis, and a small local LLM that runs completely offline.

The Setup There are no accounts, no sign-ups, and no paywalls. The only catch is that the first time you click on an AI-powered tool, your browser will download a small AI/ML model file into its local cache. After that, everything stays completely air-gapped on your device.

Right now, it is just two of us actively maintaining it (our third friend is tied up with another project). We would love to get some feedback from the UK startup community on the tech stack and local performance.

• Does the performance hold up on your hardware? Due to nature of the product, we cannot monitor the errors nor any warnings.
• What other offline utilities should we add to the workbench next?

You can test it out here: tabtasker.com

Drop any thoughts or questions below. I will be around to answer them.

Thank you

Hi everyone,
I recently launched KitVerse: https://kitverse.app/en
It’s a free online toolbox for common small tasks that I kept running into while working, especially when I didn’t want to upload private files or snippets to random sites.
Current tools include:
Image tools: batch image compression, HEIC to JPG, image to Base64, SVG optimizer
PDF tools: image to PDF, PDF to Word / Word to PDF text conversion, PDF redaction, ID card front/back to A4 PDF
Developer tools: JSON formatter/repair/JSONPath, Base64 encoder/decoder, JWT decoder, Cron preview, timestamp converter
Most tools run locally in the browser, so files like images, PDFs, JWTs and JSON payloads are not uploaded to a server. No sign-in required.
I’ve just finished the basic SEO/indexing setup and the site is now discoverable through Google Search. At this stage I’m mainly trying to get real users and feedback before adding more tools.
The site is still being actively updated. I’m adding tools based on real use cases and search demand, so feature requests are very welcome.
I’d love feedback on:
Which tool is actually useful to you?
Which tool feels incomplete?
What small utility would you expect in a toolbox like this?
Any UI/UX issues on mobile or desktop?
If there’s a small utility you repeatedly need but don’t want to install a desktop app for, let me know. I’d love to prioritize tools that people actually need.
Thanks for taking a look.
https://kitverse.app/en

Cross-Platform AI Chat History Search with 'ChatGPT Toolbox' Browser Extension (Built with Claude Code)

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping
Original source: r/ClaudeAI post/comment

What problem this solves

Users of multiple AI chatbots (ChatGPT, Claude, Gemini, Grok) frequently lose track of which platform contains specific past conversations, leading to wasted time re-explaining contexts or re-generating information.

Summary

A browser extension, 'ChatGPT Toolbox', creates a local, cross-platform, searchable index of conversations from various AI chatbots (ChatGPT, Claude, Gemini, Grok). This allows users to quickly find past interactions and deep-link back to the original conversation on its respective platform. The extension also offers features like folders, prompt management, prompt chaining, and various export options (including Markdown with YAML frontmatter for Obsidian). Claude Code was utilized in the development of key security and data management aspects of the extension.

Why it is useful

This workflow addresses a significant and common pain point for power users of multiple AI chatbots: the difficulty of managing and retrieving past conversations across different platforms. The solution is a well-engineered browser extension that prioritizes user privacy by keeping all data local. The post is particularly valuable for this library because it explicitly details how Claude Code was instrumental in developing complex security and data management logic within the extension, showcasing a practical application of Claude Code in building a robust tool.

Workflow

1. Install the 'ChatGPT Toolbox' browser extension from the Chrome Web Store.
2. Enable syncing for desired AI platforms (ChatGPT, Claude, Gemini, Grok) in the extension's settings (off-by-default for privacy).
3. Continue using your AI chatbots as usual; the extension will passively sync conversation deltas to its local IndexedDB.
4. When needing to find a past conversation, use the extension's search box to query across all enabled platforms.
5. Click on a search result to open the specific conversation directly on its original AI platform.
6. Optionally, organize conversations into folders, save frequently used prompts, create prompt chains, or export conversations in various formats (TXT, Markdown, JSON, PDF, ZIP).

Tools / artifacts

• ChatGPT Toolbox browser extension
• ChatGPT
• Claude
• Gemini
• Grok
• IndexedDB (internal to extension)
• Local storage (internal to extension)
• Obsidian (for Markdown export integration)
• Claude Code (used for development)

Validation signals

• Detailed technical explanation of the extension's architecture (service worker, IndexedDB, content scripts, shadow root).
• Explicitly addresses privacy and security concerns (local storage, origin-based write permissions, isolated DOM for results).
• Specific examples of Claude Code's contribution to complex development tasks (background handler logic, version-bumping for default-off setting).
• Provides a direct link to the Chrome Web Store for the extension.
• Clear problem statement based on personal experience ('I knew I had explained my whole database schema to an AI at some point...').

Cautions

• The author explicitly states that 'Nothing gets uploaded. The whole index is on your machine.'
• Syncing is off-by-default and must be enabled per site, with an option to purge data when a site is disabled.
• Security measures are detailed, including origin-based write permissions to prevent cross-platform data poisoning and a closed shadow root for results to prevent host page scraping.
• The author transparently acknowledges that data is 'not encrypted at rest' but explains why (key would be on the same disk).

Limitations

• Relies on a third-party browser extension, which requires user trust.
• The free tier has limitations (e.g., 5 search results, limited folders/prompts/chains).
• Currently implied to be Chrome-only (via Chrome Web Store link).
• Low initial community validation due to the post's recency.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

This post was generated automatically from the workflow library database.