Attach toast as a one-line summary, with a /workspace Status view for the detail

Open
#1,311 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, data-engineering

Research direction

Start with the existing /workspace menu from #1278 and the engine's unfulfilled report from #1307, then trace the attach toast and sidebar Workspace tile. Verify the Status row presents every declared integration, prioritizes attention items, includes served keys and the stated failure reason, and links to the web fix; the toast and tile should show the same counts.

Written by the indexing model from the issue text.

Description

Problem

When a session attaches to a workspace, the toast tries to carry the whole report: which declared tools the engine could not serve, grouped by reason, with the engine's detail. On a workspace with a few gaps it reads as noise, and there is nowhere else in the TUI to see the same information afterwards.

Proposal

  • The attach toast carries numbers only — 2 of 9 integration tools available · 7 need attention. Details: /workspace — and points at the menu.
  • /workspace gains a Status row: one line per integration the workspace declares, with what this session got from it and why not (no usable connection, server failed to start, not offered, no longer in the catalog, needs a VS Code window), the served keys, and "Open on the web" for the fix. Rows needing attention first.
  • The sidebar's Workspace tile shows the same counts under the workspace name once a session has attached.

Builds on the /workspace menu from #1278 and the engine's unfulfilled report from #1307.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.