Add missing details for Client resource

[SarahSoutoul]

🔎 Previews:

• https://clerk.com/docs/pr/ss-docs-11422/reference/javascript/client

What does this solve?

Linear.

This PR is a follow up from an external contributor PR, that renamed the deprecated activeSessions property to signedInSessions.

While reviewing that PR, @manovotny and I discovered that the type of signedInSessions didn't seem right. On the JS repo, it shows that signedInSessions is typed as SignedInSession[], but the docs currently list it as Session[].

However, after further investigating while working on this ticket, it became clear that SignedInSession[] is a more specific version of Session[], narrowing the session type to user-associated sessions with well-defined sign-in states.

So what I ended up doing is the following:

• Changed the type of signedInSessions to be SignedInSession[] instead of Session[], but it still links to the Session object page. This is actually already done on this page for e..g: https://clerk.com/docs/nextjs/reference/hooks/use-session.
• Improved the description of signedInSessions to be clearer.
• Noticed some properties and methods were missing for the Client object, so documented these as well.
• Moved properties around to ensure they are in alphabetical order.
• Added some refs to simplify the links.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
clerk-docs	Ready	Preview	Jan 21, 2026 8:50pm

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[manovotny]

Is the await here unnecessary or does line 93 need to change to function isNew(): Promise<boolean>?

[manovotny]

Same as the isNew() comment. Is the await here unnecessary or does line 149 need to change to return a promise?

[manovotny]

function and arrow function here seems wrong, unless clearCache returns a function?

[manovotny]

Same question here. Does it return a boolean or Promise<boolean>?

[manovotny]

Same question here. Are we returning a string or a function that returns a string?

[manovotny]

Does it return a string or Promise<string>?

[SarahSoutoul]

@manovotny to answer all of your comments, here is what there is in the JS repo:

So the following methods don't return Promises like create, or destroy:

• isNew()
• clearCache()
• isEligibleForTouch()
• buildTouchUrl()

Since they're not returning Promises, it makes sense to remove the await. I was following the way we write our examples for the other JS objects, but most of the methods for those return Promises to be honest.

For the following comment: function and arrow function here seems wrong, unless clearCache returns a function?, this is what we have in the JS repo and I then followed how that's translated in our docs for other methods:

[manovotny]

@manovotny to answer all of your comments, here is what there is in the JS repo:

So the following methods don't return Promises like create, or destroy:

• isNew()
• clearCache()
• isEligibleForTouch()
• buildTouchUrl()

Since they're not returning Promises, it makes sense to remove the await. I was following the way we write our examples for the other JS objects, but most of the methods for those return Promises to be honest.

Let's solve the easy problems first. 😅 If there's no promises, then let's not await. 🤝

For the following comment: function and arrow function here seems wrong, unless clearCache returns a function?, this is what we have in the JS repo and I then followed how that's translated in our docs for other methods:

These get more complicated.

1. I think our JS code is not quite right. Take clearCache, for example:

clearCache(): void {
  return this.sessions.forEach(s => s.clearCache());
}

There shouldn't be a return statement (we're staying void) and forEach actually returns undefined.

2. I think we're unintentionally communicating the wrong thing. What we have indicates we're returning a function, which then needs to be called to get the primitive.