mirror of
https://github.com/browser-use/browser-use.git
synced 2026-09-14 19:59:47 +08:00
Saurav Panda
47a52790a6
Drop the bu-3 and bu-3-max model ids everywhere they were surfaced: - ChatBrowserUse no longer lists them as valid bu-* aliases (provider-prefixed ids like openai/gpt-5.5 are still accepted by the gateway). - Remove their custom pricing entries and the README pricing blocks. - Update docstrings, README quickstart, and the beta_agent example to use openai/gpt-5.5 as the default, with bu-2-0 shown as a commented alternative. - Drop the tests that asserted bu-3/bu-3-max acceptance and pricing.
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