code: Coding agent for user scripts

Summary

Browser Code is a browser extension that allows Claude to interact with web pages as a virtual file system, enabling the creation, editing, and management of userscripts. It offers features like script persistence, automatic execution on matching URLs, and a two-phase workflow for safety.

Key Takeaways

1. Browser Code is a browser extension that gives Claude a virtual filesystem view of web pages.
2. Scripts persist via userScripts API - Saved scripts register with Chrome's userScripts API (Chrome 120+) or Firefox's equivalent, bypassing CSP restrictions
3. Browser Code uses a two-phase workflow for safety: Plan Mode (default) - Agent explores the page, reads files, proposes changes to plan.md.

Statement Breakdown

• Claimed Facts: 70% of statements the article presents as facts
• Opinions: 20% of statements classified as editorial or subjective
• Claims: 10% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article is technical documentation from a software repository, which generally has high accuracy. The claims are specific and verifiable against the linked repository. The writing is straightforward and avoids sensationalism, increasing confidence in its reliability.

Bias assessment: Technological Innovation. The article is biased towards showcasing the capabilities and benefits of the 'Browser Code' extension. It focuses on the technical aspects and advantages for developers, with minimal discussion of potential drawbacks or alternative solutions. The language is promotional, highlighting features and ease of use.

Note: This article describes a software tool. Evaluate its suitability for your specific needs and security context.

Credibility flag: Potentially Useful

Claimed Facts (8)

• This is a factual statement about the extension's functionality.
• This describes the extension's capabilities and how it interacts with existing APIs.
• This is a technical detail about how the extension handles script registration and security.
• This describes how scripts are executed based on URL patterns.
• This describes the version control mechanism.
• This describes how route parameters are handled.
• This describes the synchronization process in Chrome.
• This describes the synchronization process in Firefox.

Opinions (6)

• This is a subjective comparison to another tool.
• This is an assessment of the benefit of the version control mechanism.
• This is an assessment of the benefit of the two-phase workflow.
• This is a subjective choice of conflict resolution strategy.
• This is a generalization about the security policies of certain websites.
• This is a generalization about the practices of certain websites.

Claims (5)

• This is a simplification that may not accurately reflect the complexity of all websites.
• Bypassing CSP restrictions can have security implications and should be approached with caution.
• Using 'unsafe-inline' and 'unsafe-eval' in CSP can introduce security vulnerabilities.
• This is a simplification of how the DOM is represented, and may not be entirely accurate.
• While the two-phase workflow reduces the risk, it doesn't completely eliminate the possibility of unintended changes.

Key Sources

• Author — Creator of Browser Code
• Tampermonkey — Userscript manager