In the development of the HonoGear extension, the long-standing challenge of “unstable Note.com integration” has finally been resolved. With the v2.1 update, the workflow from Amazon product selection to draft creation and posting to Note.com now literally completes with one click (or even zero clicks).

Key Changes in v2.1

This update focuses on improving User Experience (UX) and enhancing the robustness of the automation process.

1. Robust Note.com Posting Automation

Previously, the auto-script could lose track of the “Post” button due to changes in Note.com’s dashboard structure or DOM loading timing.

In v2.1, we implemented the following improvements:

  • Multi-Selector Strategy : We implemented a logic that searches for multiple elements with priority, such as href="/notes/new, aria-label="Post,” and SVG icons, making it resilient to UI changes.
  • Enhanced Editor Auto-Paste : After transitioning from the dashboard to the editor, the system automatically reads article data saved in local storage and injects the title and body into the appropriate areas.
  • Relaxed Validation : Previously, the system would refuse to paste without strict Markdown headers. This has been changed to a warning only, allowing for more flexible text formats.

2. Eliminating Extension Context Invalidated Errors

A common pitfall in Chrome Extension development is when scripts continue to run in old tabs after an update, stopping with the Extension context invalidated error. To address this, we added runtime ID checks (chrome.runtime?.id) to all polling processes, ensuring scripts stop immediately when the extension is invalidated.

Chrome Extension Context Invalidated Fix

Stack Overflow
Chrome Extension Context Invalidated Fix

3. Streamlined Developer Workflow

As the primary user of this tool, I’ve also refined the debugging and verification workflow:

  • Local Verification with Puppeteer : Created scripts/test-extension-flow.mjs to automate UI injection tests without requiring login.
  • Error Check Workflow : Compiled standard troubleshooting procedures in .agent/workflows/check-extension-errors.md.

Future Outlook

The friction coefficient for the act of “writing” has now approached zero. Next, we will focus on the quality of the generated content itself, moving forward with improvements to AI prompts.

Automation is not just about speed, it’s about removing friction.