Resume after "ask user" tool fails to provide Open AI key

[jjlampart]

Will trying out some of the agent features, I ran into a problem with the "ask user" tool. After selecting an answer, it produces an "no API key provided" error and ends the discussion. This was specific to Chat GPT. The function works as expected with Claude.

• Version: v0.8.8-rc2
• Configuration: OPENAI_API_KEY=user_provided, Agent based on GPT 5.6 with Ask User enabled.
• Trigger: Agentsconversation pauses for Ask User, then resumes
• Result: resume fails with {"type":"no_user_key"}
• Key remains active and can be used in new chats

With help from Chat GPT I was able to track down the problem:

• Cause: the OpenAI initializer loads the stored key only when the resumed request contains expiresAt; resume requests omit it.
• Expected behavior: retrieve the stored key whenever userProvidesKey is true; check expiry only when expiry metadata is present.

The following patch resolved the issue in my local installation:

In

packages/api/src/endpoints/openai/initialize.ts

after

const userProvidesKey = isUserProvided(OPENAI_API_KEY);
const userProvidesURL = isUserProvided(OPENAI_REVERSE_PROXY);
let userValues = null;

replace

if (expiresAt && (userProvidesKey || userProvidesURL)) {
  checkUserKeyExpiry(expiresAt, endpoint);
  userValues = await db.getUserKeyValues({
    userId: user,
    names: ['OPENAI_API_KEY', 'OPENAI_REVERSE_PROXY'],
  });
}

with

if (expiresAt && (userProvidesKey || userProvidesURL)) {
  checkUserKeyExpiry(expiresAt, endpoint);
}
if (userProvidesKey || userProvidesURL) {
  userValues = await db.getUserKeyValues({
    userId: user,
    names: ['OPENAI_API_KEY', 'OPENAI_REVERSE_PROXY'],
  });
}

With this patch, the key is provided also when there is expiration information.

From a search on the code, this could also affect Google endpoints, but I did not confirm due to lack of a key for testing.

Thanks to the developers for creating this great program!

[redbotster]

the patch looks correct. the root cause is that getUserKeyValues is gated on expiresAt being present, but resume requests don't carry it, so the key never gets fetched even though userProvidesKey is true. separating the expiry check from the key lookup is the right fix. worth also adding a test that exercises the resume path without expiresAt to prevent regression.

[danny-avila]

Sorry I didn't quite understand this report at first glance so I moved to discussions, but I've got a fix now

#15749