v2.7.7: Connector Panels Open Again, Chat Survives a Refresh, and Context Window Changes Actually Reach Your Employees

Some releases add features. This one takes three things that looked broken and makes them work the way you always assumed they did. If you have tried to assign a bot to an employee lately, refreshed a busy chat and watched it come back wrong, or raised your context window and seen nothing happen, v2.7.7 is the release that quietly fixes all three.

The connector side panels are back

Since the settings redesign, the side panels in Settings, Connectors never appeared. Clicking How to Create a Bot or Assign did nothing at all, on Telegram, Discord, Slack, Teams, every connector. Assigning a bot to an employee was simply impossible from the interface, which is a rough thing to discover when that is the entire reason you opened the page.

Here is the part worth knowing: the panels were opening the whole time. They were being positioned underneath the connector list and drawn below it, so they sat completely hidden behind it. Nothing was failing loudly, which is exactly why it was easy to miss and maddening to hit.

• Every connector is usable again. The help panel and the assignment panel open to the right of the connector list, as intended.
• The fix covers every stacked panel in the new settings interface, not just connectors.
• Panels now measure the open panels beside them instead of leaning on a shared value that several of them were overwriting at once. That overwrite was why the position silently drifted after the redesign.

The chat holds the whole conversation again

Refreshing a busy conversation could leave it stuck on an old message, show a pile of tool rows with no reply, or come back looking like a brand-new session. At the same time, tools an employee was running never showed up until you reloaded the page, and once they did, the chat flickered on every single one. None of it lost your work, but it made a working session feel unreliable, and that feeling matters as much as the facts.

We rebuilt how a conversation restores itself and how live activity streams in:

• Refresh keeps your conversation. The reload window is now counted in messages you can actually read, so a reply full of tool calls no longer shoves the conversation off screen. Before, a long working session could come back showing three bubbles.
• The exchange in progress is never cut in half. However many tools an answer needed, a reload always goes back at least to the message you sent.
• No more orphan tool rows. The conversation always resumes on one of your messages, so tool calls arrive alongside the reply that produced them. The first refresh is correct, with no second one needed.
• Tools appear as they run. They were being dropped on the way to the browser and only surfaced after a reload. Now you watch the work happen.
• The chat no longer flickers. Tool calls are grouped before being sent, and the conversation keeps its existing messages in place instead of redrawing the entire list on each one. On a 40-tool answer, that used to mean redrawing everything 80 times.

That last number is the one to sit with. An employee doing real, multi-step work is exactly when the interface was working hardest against itself. Now the heavier the task, the more you see, not the less.

Changing the context window now reaches your employees

If you run custom LLMs, this one has been quietly costing you. The instance-wide context window in Admin, Settings was copied into each employee when its provider was first chosen, and then never read again. Raising it changed nothing for anyone. Every existing employee stayed on the size it was created with, and the only workaround was to reopen each employee and pick its model again, one by one.

• Set it once, it applies everywhere. Each employee picks up the current size the next time its session starts. Clear the session and carry on.
• Nobody is interrupted. Employees already mid-task keep their current size until they restart, so changing the setting never cuts a live conversation short.

It is a small setting with a large blast radius. A context window is how much your employee can hold in mind at once, and being silently pinned to an old value is the kind of thing that makes an otherwise capable employee feel forgetful for no reason. Now the number you set is the number they use.

The theme underneath

None of these are marquee features, and that is sort of the point. A connector panel that opens, a chat that survives a refresh, a setting that actually propagates: this is the unglamorous layer that decides whether the product feels solid or slippery on an ordinary Tuesday. We would rather ship the boring fix that removes a daily papercut than let it linger behind something flashier.

v2.7.7 is live now. If you were blocked on assigning a bot, that path works again. If you run custom models, take a moment to confirm your context window is where you want it, then clear a session to pick it up.