Files
browser-use/browser_use
Magnus Müller bbd34cab80 Fix two extension-related bugs
1. Remove Reader View from description - extension not actually loaded
   - Updated enable_default_extensions description to only mention extensions that are actually loaded
   - Removed misleading reference to Reader View functionality

2. Resolve Chrome flag conflict for extension activity logging
   - Removed --disable-extension-activity-logging from CHROME_DEFAULT_ARGS
   - Keeps --enable-extension-activity-logging in _get_extension_args() when extensions enabled
   - Eliminates contradictory flags that caused unpredictable logging behavior
2025-07-19 16:07:52 +02:00
..
2025-07-19 01:40:41 +02:00
2025-07-19 16:07:52 +02:00
2025-07-18 23:42:37 +02:00
2025-07-11 18:14:03 +02:00
2025-07-04 17:29:22 +02:00
2025-03-28 18:11:36 -07:00
2025-07-09 22:27:22 +02:00
2024-11-06 18:18:00 +01:00
2025-07-08 03:16:22 -07:00

Codebase Structure

The code structure inspired by https://github.com/Netflix/dispatch.

Very good structure on how to make a scalable codebase is also in this repo.

Just a brief document about how we should structure our backend codebase.

Code Structure

src/
/<service name>/
models.py
services.py
prompts.py
views.py
utils.py
routers.py

    	/_<subservice name>/

Service.py

Always a single file, except if it becomes too long - more than ~500 lines, split it into _subservices

Views.py

Always split the views into two parts

# All
...

# Requests
...

# Responses
...

If too long → split into multiple files

Prompts.py

Single file; if too long → split into multiple files (one prompt per file or so)

Routers.py

Never split into more than one file