chore: regenerate API client from latest OpenAPI spec - #94
Conversation
andreakiro
left a comment
There was a problem hiding this comment.
Auto-approved: scheduled API client regeneration.
|
| Filename | Overview |
|---|---|
| internal/api/client.gen.go | Regenerates the API contract around session files but removes symbols still required by hand-written commands, causing compile failures. |
| internal/cmd/sessionstart_flags.gen.go | Removes the use-file-storage flag while the hand-written opt-out implementation and existing CLI contract still depend on it. |
Prompt To Fix All With AI
### Issue 1
internal/api/client.gen.go:721-724
**Session storage field breaks build**
When the command package is built, `sessionstart_optout.go` still assigns `ApiSessionStartRequest.UseFileStorage`, but this regeneration removes that field, causing the CLI build to fail. It also removes the still-documented `--use-file-storage` flag.
### Issue 2
internal/api/client.gen.go:9689-9699
**Removed file APIs break commands**
When the CLI is built, `internal/cmd/files.go` still references the removed `FileListUploads`, `FileListDownloads`, `FileUpload`, and `FileDownload` types and methods, causing undefined-symbol compilation failures. The command callers need to be migrated with the new session-scoped file API.
### Issue 3
internal/api/client.gen.go:9689-9699
**Session file changes lack tests**
This PR changes generated request fields, CLI flags, and file endpoint names without adding unit or integration coverage. Add regression coverage for the new session-file contract so incompatibilities with hand-written command code are caught.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "chore: regenerate API client from latest..." | Re-trigger Greptile
| // SolveCaptchas Whether to try to automatically solve captchas | ||
| SolveCaptchas *bool `json:"solve_captchas,omitempty"` | ||
|
|
||
| // UseFileStorage Whether FileStorage should be attached to the session. | ||
| UseFileStorage *bool `json:"use_file_storage,omitempty"` | ||
|
|
||
| // UserAgent The user agent to use for the session |
There was a problem hiding this comment.
Session storage field breaks build
When the command package is built, sessionstart_optout.go still assigns ApiSessionStartRequest.UseFileStorage, but this regeneration removes that field, causing the CLI build to fail. It also removes the still-documented --use-file-storage flag.
Knowledge Base Used:
Prompt To Fix With AI
This is a comment left during a code review.
Path: internal/api/client.gen.go
Line: 721-724
Comment:
**Session storage field breaks build**
When the command package is built, `sessionstart_optout.go` still assigns `ApiSessionStartRequest.UseFileStorage`, but this regeneration removes that field, causing the CLI build to fail. It also removes the still-documented `--use-file-storage` flag.
**Knowledge Base Used:**
- [Browser automation workflows](https://app.greptile.com/nottelabs/-/custom-context/knowledge-base/nottelabs/notte-cli/-/docs/browser-automation.md)
- [Session lifecycle and execution](https://app.greptile.com/nottelabs/-/custom-context/knowledge-base/nottelabs/notte-cli/-/docs/session-lifecycle.md)
- [Command bootstrap and shared behavior](https://app.greptile.com/nottelabs/-/custom-context/knowledge-base/nottelabs/notte-cli/-/docs/command-bootstrap.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.03f31da to
fe8fbf8
Compare
andreakiro
left a comment
There was a problem hiding this comment.
Auto-approved: scheduled API client regeneration.
fe8fbf8 to
5f5fc04
Compare
andreakiro
left a comment
There was a problem hiding this comment.
Auto-approved: scheduled API client regeneration.
Automated regeneration of the generated API client (
internal/api,internal/cmd/*_flags.gen.go) from the latest OpenAPI spec.Last regenerated: 2026-09-04 05:14 UTC