Alexander Balashov in #general: "Hey all, I’ve been poking at upgrading the repo from TypeScript 5.9 to 6.0, and it looks like a pretty smooth change. I only ran into two things: •..." | Archestra Community

Messages in #general

Alexander Balashov — April 23, 2026

Hey all, I’ve been poking at upgrading the repo from TypeScript 5.9 to 6.0, and it looks like a pretty smooth change. I only ran into two things: • a `tsconfig` deprecation warning, already addressed in this PR • a small TS bug that the stricter compiler checks caught, already fixed in my TS 6 PR So it feels like we're in a good spot to move to 6.0 without much churn. It also seems like a good prep step for eventually switching to the faster TypeScript 7 toolchain. TypeScript 6 PR is here github.com/archestra-ai/archestra/pull/4035

10 replies

joey (archestra team) — April 23, 2026

TIL typescript 7 beta was announced yesterday 😅

joey (archestra team) — April 23, 2026

pr LGTM - one comment about `pnpm` lockfile from CI, other than that will merge once that's addressed! 🙏

Alexander Balashov — April 23, 2026

> TIL typescript 7 beta was announced yesterday yeah, BTW I've already tested the beta version locally and it gives x8 🚀 performance improvement. Almost the advertised x10

Alexander Balashov — April 23, 2026

@user > pr LGTM - one comment about `pnpm` lockfile from CI, other than that will merge once that's addressed! 🙏 ✅ fixed

joey (archestra team) — April 23, 2026

> and it gives x8 🚀 performance improvement. Almost the advertised x10 oh wow! merging the ts6 pr now, if you are motivated to open one to upgrade to ts7, I'd certainly review 👀

joey (archestra team) — April 23, 2026

curious why the `pnpm.overrides` portion is needed in the PR?

Alexander Balashov — April 23, 2026

without the `override` install works, but removing the override causes duplicate TypeScript versions in the tree. • pnpm install completes successfully (only unrelated peer warnings for @better-auth/passkey and next-runtime-env). • However, the lockfile now resolves both typescript@5.9.3 and typescript@6.0.2. The override was deduping them. • Packages pulling in 5.9.3 via peer deps: @tanstack/router-plugin@5.86.0, tsconfck@0.21.3, @hey-api/openapi-ts@0.94.1, and a vite plugin at 6.1.1. They all declare typescript as a peer and prefer 5.x. • The - typescript 5.9.3 / + typescript 6.0.2 diff pnpm printed confirms the override was actively forcing those consumers onto 6.0.2. Recommendation: keep the override. It's doing real work — preventing a second TS copy from being hoisted for tooling that hasn't caught up to TS 6 yet.

joey (archestra team) — April 23, 2026

makes sense! :pr-merged:

Alexander Balashov — April 23, 2026

after that realized the approach is actually suboptimal. Here is a proper fix using the `pnpm` 's `Catalogs`feature github.com/archestra-ai/archestra/pull/4043

Alexander Balashov — April 23, 2026

> if you are motivated to open one to upgrade to ts7, I'd certainly review ✅ done github.com/archestra-ai/archestra/pull/4051

development

general

social

#general

Apr 22April 23, 2026

Yesterday

Palak Bakshi4:53 AMOpen in Slack

Hi Team, I am Palak

I am interested in contributing to Archestra, but I found that commenting on issues is currently blocked. Could anyone please guide on how can we claim an issue? Should I work on reproducing and provide a video of working fix first?

Ps: I’m about to graduate and have prior experience through internship at MNC as well as open source contributions. I’d also like to know if I’m eligible to participate in the interviews.

🙌1:archestra-love:1🚀2

1 reply

Phil Filippak7:03 AMOpen in Slack

Hi everyone! I'm Phil, have been working in software engineering for 15 years, will try and contribute to Archestra in the next few days, then we'll see how it works out

❤️1🙌1🔥1👋1

Ilya Korovin10:09 AMOpen in Slack

Hi, is the A2A API supposed to work right now, specifically with API keys managed on the Settings page? API keys in Settings are handled via ApiKeyModel, and it looks like that model is not used anywhere. For the A2A API, I only see UserTokenModel and TeamTokenModel.

14 replies

Alexander Balashov11:42 AMOpen in Slack

Hey all,

I’ve been poking at upgrading the repo from TypeScript 5.9 to 6.0, and it looks like a pretty smooth change.

I only ran into two things:

• a tsconfig deprecation warning, already addressed in this PR

• a small TS bug that the stricter compiler checks caught, already fixed in my TS 6 PR

So it feels like we're in a good spot to move to 6.0 without much churn. It also seems like a good prep step for eventually switching to the faster TypeScript 7 toolchain.

TypeScript 6 PR is here https://github.com/archestra-ai/archestra/pull/4035

😮1

10 replies

Archestra App5:02 PMOpen in Slack

New release! 🚀🚀🚀

1.2.23 (2026-04-23)

Features

*a2a:* accept arbitrary JSON payloads in addition to JSON-RPC envelope (#4037) (6d15f0c)
add onboarding wizard (#4013) (12f8a5a)
add Outline knowledge connector (#3938) (0bd17f3)
interweave persisted chat errors (#4002) (e5e3fec)

Bug Fixes

include scheduled- prefixed session IDs in sessionId search (#4040) (a1822eb)
scroll to bottom when user sends a message (#4005) (2ac31a6)
Slack setup slash command slugs (#4014) (0570258)
treat UUID search input as sessionId filter on sessions list (#4029) (e580151)

Documentation

fix stale mcpServer:admin reference in access-control docs (#3994) (a1fc7bf)
update agent docs (#4038) (315ffeb)

Miscellaneous Chores

clear agent identity provider config (#4020) (0bb5954)
knowledge base - make advanced-access control an enterprise feature (#3783) (10b4ff0)
remove deprecated downlevelIteration from tsconfig (#4027) (77bae6a)
upgrade TypeScript 5.9 -> 6.x (#4035) (2b7737e)

Tigran Kostandyan5:06 PMOpen in Slack

While working on error processing in web chat I noticed we started showing duplicate error cards – it wasn't like this a few days ago. Traced it to the AI SDK invoking onError twice after we added persistence inside that callback. Proposed fix here: https://github.com/archestra-ai/archestra/pull/4047

Join Slack to see the image

👀1

3 replies

Kyle Skutt6:45 PMOpen in Slack

Hi Kyle looking to be more involved with open source. Experience in building LLM, environments and various programs. I noticed most of the new bounties appear to be for in house members. If there is anything i can jump on let me know!

2 replies

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!

Thread

Alexander Balashov11:42 AMOpen in Slack

Hey all,

I’ve been poking at upgrading the repo from TypeScript 5.9 to 6.0, and it looks like a pretty smooth change.

I only ran into two things:

• a tsconfig deprecation warning, already addressed in this PR

• a small TS bug that the stricter compiler checks caught, already fixed in my TS 6 PR

So it feels like we're in a good spot to move to 6.0 without much churn. It also seems like a good prep step for eventually switching to the faster TypeScript 7 toolchain.

TypeScript 6 PR is here https://github.com/archestra-ai/archestra/pull/4035

😮1

10 replies

joey (archestra team)12:19 PMOpen in Slack

TIL typescript 7 beta was announced yesterday 😅

joey (archestra team)12:20 PMOpen in Slack

pr LGTM - one comment about pnpm lockfile from CI, other than that will merge once that's addressed! 🙏

Alexander Balashov12:31 PMOpen in Slack

TIL typescript 7 beta was announced yesterday

yeah, BTW I've already tested the beta version locally and it gives x8 🚀 performance improvement. Almost the advertised x10

Join Slack to see the image

Alexander Balashov12:39 PMOpen in Slack

@user

pr LGTM - one comment about pnpm lockfile from CI, other than that will merge once that's addressed! 🙏

✅ fixed

👀1

joey (archestra team)12:59 PMOpen in Slack

and it gives x8 🚀 performance improvement. Almost the advertised x10

oh wow! merging the ts6 pr now, if you are motivated to open one to upgrade to ts7, I'd certainly review 👀

👍1

joey (archestra team)1:03 PMOpen in Slack

curious why the pnpm.overrides portion is needed in the PR?

Alexander Balashov1:11 PMOpen in Slack

without the override install works, but removing the override causes duplicate TypeScript versions in the tree.

• pnpm install completes successfully (only unrelated peer warnings for @better-auth/passkey and next-runtime-env).

• However, the lockfile now resolves both typescript@5.9.3 and typescript@6.0.2. The override was deduping them.

• Packages pulling in 5.9.3 via peer deps: @tanstack/router-plugin@5.86.0, tsconfck@0.21.3, @hey-api/openapi-ts@0.94.1, and a vite plugin at 6.1.1. They all declare typescript as a peer and prefer 5.x.

• The - typescript 5.9.3 / + typescript 6.0.2 diff pnpm printed confirms the override was actively forcing those consumers onto 6.0.2.

Recommendation: keep the override. It's doing real work — preventing a second TS copy from being hoisted for tooling that hasn't caught up to TS 6 yet.

👍1

joey (archestra team)3:59 PMOpen in Slack

makes sense! :pr-merged:

Alexander Balashov4:20 PMOpen in Slack

after that realized the approach is actually suboptimal.

Here is a proper fix using the pnpm 's Catalogsfeature

https://github.com/archestra-ai/archestra/pull/4043

👀1

Alexander Balashov6:28 PMOpen in Slack

if you are motivated to open one to upgrade to ts7, I'd certainly review

✅ done https://github.com/archestra-ai/archestra/pull/4051

👀1