Refactor: Consistent state access in attemptApiRequest

Author: Your Name

src/core/task/Task.ts

@@ -1563,7 +1563,7 @@ export class Task extends EventEmitter<ClineEvents> {
 
 			const contextWindow = modelInfo.contextWindow
 
-			const autoCondenseContext = state?.experiments?.autoCondenseContext ?? false
+			const autoCondenseContext = experiments?.autoCondenseContext ?? false
 			const truncateResult = await truncateConversationIfNeeded({
 				messages: this.apiConversationHistory,
 				totalTokens: contextTokens,
@@ -1627,7 +1627,7 @@ export class Task extends EventEmitter<ClineEvents> {
 		} catch (error) {
 			this.isWaitingForFirstChunk = false
 			// note that this api_req_failed ask is unique in that we only present this option if the api hasn't streamed any content yet (ie it fails on the first chunk due), as it would allow them to hit a retry button. However if the api failed mid-stream, it could be in any arbitrary state where some tools may have executed, so that error is handled differently and requires cancelling the task entirely.
-			if (state?.autoApprovalEnabled && state?.alwaysApproveResubmit) {
+			if (autoApprovalEnabled && alwaysApproveResubmit) {
 				let errorMsg
 
 				if (error.error?.metadata?.raw) {
@@ -1638,7 +1638,7 @@ export class Task extends EventEmitter<ClineEvents> {
 					errorMsg = "Unknown error"
 				}
 
-				const baseDelay = state.requestDelaySeconds || 5
+				const baseDelay = requestDelaySeconds || 5
 				let exponentialDelay = Math.ceil(baseDelay * Math.pow(2, retryAttempt))
 
 				// If the error is a 429, and the error details contain a retry delay, use that delay instead of exponential backoff