trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- Settings › Tokens names the harness behind each OAuth token and says it renews itself
- The MCP person and pins tools refuse a limit outside 1–200 instead of clamping it, with the words the HTTP list routes use
- GET /api/v1/search names an unknown kind or a bad limit in a note, as /api/v1/explore names an unknown filter
- An API path called with the wrong method answers 405 with an Allow header naming the methods it takes, not 404 no_route
- A refused issue close says which rule refused it, not "your credentials lack the scope"
- The picker skips an issue the dispatcher will refuse, so one fresh pull does not idle every builder
new above
offline