Skip to main content

​
One token for the whole repository set

A run can now declare additional GitHub repositories that its stages may access through the managed GITHUB_TOKEN:
The run origin stays implicit, and Fabro mints one installation token scoped to the origin plus every declared repository with the shared permission map. Inside stages, gh commands, raw GitHub API calls, plain Git over HTTPS, and the common SSH URL spellings (git@github.com:owner/repo and ssh://git@github.com/owner/repo) all work against the declared set — the SSH forms are transparently rewritten to authenticated HTTPS with no secret placed in Git configuration. Every repository must share one owner and be reachable by the origin’s GitHub App installation. Preflight resolves each repository’s installation, mints the scoped token once, and probes every repository with git ls-remote, naming the exact repository when something is not accessible; run initialization enforces the same checks. A declared-but-inaccessible repository fails the run before its first stage. Declaring additional repositories requires contents = "read" or contents = "write". With contents = "write", any stage can push to any declared repository — declare the smallest set and weakest permissions that work. See Additional repositories for details, including layering rules and GH_TOKEN precedence. The built-in web_search tool now supports Venice as an automatic alternative to direct Brave Search. Fabro uses BRAVE_SEARCH_API_KEY when present. Otherwise it uses VENICE_API_KEY with Venice’s Brave search engine. If neither key is present, the tool is not registered. Failed calls do not fall back between providers. See Venice Search and Brave Search.