Saropa Workspace

Pin files as shortcuts, run scripts with a double-click, and automate repository workflows.
Developed by Saropa to make Flutter & Dart development faster.

💬 Have feedback on Saropa Workspace? Please share it by opening an issue on GitHub!

Saropa Workspace maps your recurring shell scripts and critical platform configurations into a master sidebar menu. On initialization, it parses your manifests and .git/config to auto-generate Recipes — zero-config, one-click macros for tasks like formatting, linting, and tracking Git branch PRs. Wire shortcuts into chains and event-driven sequences in the Visual Planner, or fire them off cron schedules while the editor is open. The environment state saves directly to a plain .json file inside .saropa/. Commit it, and your whole team inherits a fully automated project workspace.

Screenshot

Features

📌 Add & Open

• Single-Click Access: Pin any file via the editor title menu or Explorer right-click menu to open it instantly without hunting through directories.
• Website Shortcuts: Add any URL — the project's GitHub page, a staging dashboard, a docs site — with Add Website (URL)...; a single click opens it in your browser, right beside your file and script shortcuts. Or run Add Website Shortcuts from Project... to pick from the addresses your repo already declares (git remote, package.json, pubspec.yaml, mkdocs.yml) in one checklist — no source scanning, just the known files, so the list stays short.
• Scoped Shortcuts: Organize configurations into Project Shortcuts (shared repo-level) or Global Shortcuts (tied to your user profile).
• Unused Marker: Unused or newly added shortcuts carry a leading dot (●) until you open or run them, so new items are easy to spot.
• Launcher Board: Access your tools via a dedicated bottom panel tab with searchable text filters, collapsible sections, and responsive column layouts.

▶️ Script Execution

• Double-Click Runs: Double-click a saved shortcut to trigger scripts inside the integrated terminal or a background channel.
• Custom Environments: Define runtime prefixes (python, node, bash), append CLI arguments, set working directories, and inject environment variables.
• Dynamic Tokens: Parameterize commands with interactive placeholder tokens like ${prompt:Label} or ${pick:a,b,c} that cache your last chosen response.
• Process Handling: Bypasses tree-view event limits with inline play buttons, displays last-run exit status flags, and offers quick force-kill commands.

⏰ Scheduling & Workflows

• Automation Triggers: Run saved scripts at designated times, repeating intervals, open events, or native cron expressions.
• Visual Planner: Wire shortcuts into graph chains or calendar sequences that respond to project hooks like git commits and pushes.
• In-Process Engine: Runs lightweight tasks locally without external system configuration; a status-bar tracker keeps queued scripts visible.

🧩 Discovered Recipes

• Auto-Detection: Scans your codebase manifests and .git/config to stand up dynamic macros without manual entry.
• Ecosystem Shortcuts: Generates instant controls for package installs, formatting, lint diagnostics, and repository PR paths.
• Hygiene Tools: Includes built-in sweeps like a Workspace bloat scan to clear directory conflicts and layout freezes.
• Editable Promotion: Keep scripts hidden, toggle entire recipe domains off, or choose Promote to Shortcut to customize a macro permanently.

🚦 Release Board

• One Screen For "Can We Ship?": Click Release Board in the status bar (or the checklist button in the Shortcuts view title bar, or run Release Board: Open). It reads your bugs, docs and plans folders across projects and shows what blocks a release in red, amber and purple. The tab is named Saropa Release Board.
• Honest Light: NO-GO, UNVERIFIED or GO per project. GO needs an accepted baseline, nothing blocking, every open document read, and fresh, clean lint and test results.
• Always In View: A Release Board section at the top of the sidebar shows one row per project with its light and first blockers. The status bar button is tinted with the worst light. The board can open once as a background tab when a window starts.
• Correct The Severity Yourself: A document's severity (Extreme to Low) comes from keywords and phrases, which can guess wrong. The line under the board's intro offers Edit keywords (also in the options menu, the kebab button in the top bar). The editor lists the phrases of each level as chips you add or remove, the threshold, the weights and the negation words, each with a one-line explanation, and shows live which open documents would change level before you save. Save asks first, then writes only what differs from the shipped keywords into the severity key of .saropa/release-board.json; Restore defaults (per list, or all) goes back. Lowering a severity can turn a light greener, so the editor and the confirmation say so, and the board shows Keywords customized by you whenever the file changes the keywords.
• Several Projects: The Projects button adds folders, or every project inside a parent folder, next to the folders open in the window. With more than one project, a header counts the projects by light, and a folder that cannot be read gets its own gray row with the reason. The Settings button opens the board settings.
• Three Tabs: Gantt (the default) lists items grouped by project in the order the work must be done, with a bar per item (a Split / Unified switch shows all projects in one section), arrows for what waits on what and a dimmed trail of done items. Board shows the cards and lists. Future holds ideas and plans that are not started. The Scope switch shows This project or All projects (the open folders plus the ones you chose). The View options kebab holds the release mode, Group by, the time you have, the devices in hand and Tags and rules. The Project actions kebab holds Hand off board, Organize with AI, Bring back AI result, scan again, the rules file, projects, keywords, settings and the start-up choice. Active filters show as pills under the top bar; click a pill to remove it or Clear all.
• Edit In Place: Click a row's status pill for a menu of statuses and severities. The change is saved at once with an Undo bar. Waits on... and Blocks... pick the documents a row depends on or holds up; a Needs: line is added to or taken out of the document. Move to group... puts a document in a group, a new group, or none.
• Drag And Drop: Drag a row onto a status band to set its status, onto a group to move it there, out of its group to ungroup it, or onto another row's Waits on slot to make that row wait on it. Each drop is saved at once with Undo. Inside a group, Alt+Up and Alt+Down move the focused row one place.
• Group By: Project, Group, Status, Severity or None (View options, or the releaseBoard.groupBy setting). Groups are found automatically from folders, file names, tags and shared source files, or listed by hand in the rules file. An auto group has a name, an emoji and a colored stripe, and a tooltip says why it exists ("tag X matched 4 documents"). A group you renamed or changed shows by you.
• Tags And Rules Editor: View options > Tags and rules... (or Edit tags... in a row menu) opens one editor with four tabs: Tags (words that match documents to groups, each with a label, emoji and color), Link words (phrases such as "depends on"), Naming (prefixes, dates and acronyms dropped or kept in group names) and Severity (the keyword editor). It previews the effect on your open documents, and has Import, Export and Reset. Save writes only what differs from the shipped defaults, to the organize key of the project's rules file (.saropa/release-board.json).
• Link Proposals: Documents that name each other are listed as proposed links. Accept treats one as waiting on the other; Reject stops suggesting it.
• Hand Off To An AI Agent: A row menu, a group, a project or the whole board can build a document for an AI agent. Choose the scope (this item, chosen items, group, project, whole board), a task (Fix, Plan, Review, Triage or Organize) and a format (Markdown or JSON). Save to file writes it to .saropa/handoff/ in the project; Copy copies one line that points at the file (or the full text, see releaseBoard.handoff.copyMode); Run in terminal saves and runs the releaseBoard.handoff.terminalCommand in a new terminal. The board never sends anything to an AI by itself. Bring back takes the agent's reply, lists the changes it proposes and applies only the ones you tick; an item that changed since the agent saw it is skipped. Organize with AI asks for status, severity, group and Needs: link proposals as a patch you review.
• Active Now: A project with a chat working in it shows an Active now pill, read from Saropa Chat Explorer when it is installed. The board looks every 30 seconds; the pause button stops that, and releaseBoard.chatActivity turns it off.
• Since You Left: When something changed since you last looked, a strip says so, with a Changes button that lists it and a Dismiss button. Rows that changed have a dotted outline until you dismiss.
• Documents Are Links: An openable document is an underlined link, and its tooltip is its path inside the project. Anything else stays plain text. Every element, colored dot, triangle, square and mark has a tooltip that says what it is and what it means. Every count is a small rounded pill.
• Row Menu And Options Menu: Every document row has a small kebab button (three dots) that opens a menu: Open document, Change status, Change severity, Back to automatic, Assign rule, Hand off and Open the rules file. Change severity stores your choice for that one document under severityOverrides in .saropa/release-board.json; it wins over the severity guessed from phrases, a small Set mark shows it, and a line under the intro counts the severities set by hand and the ones lowered below a level that stops the release. Back to automatic takes away your severity and your status for the document. Click a row's status pill (or its kebab) to choose its status or severity; the choice is saved at once, with an Undo bar for ten seconds, and a line in the menu says what the choice would do to the project's light before you click. Assign rule still asks you to confirm before it adds a rule to .saropa/release-board.json. A status chosen for one document wins over the rule that placed it and can turn a blocking document green and move the project's light, for example to GO. Such a rule is tried before all others and the document's Status line cannot undo it. Every rule written from the board names its project, so it never changes another project's documents, and it applies to chosen projects too. Nothing is written for a project whose id had a number added because two folders share a name (the check only catches ids that already collide when the rule is written; an id can still shift if folders are added later), or when the rules file has unsaved edits, is a symbolic link, is not plain UTF-8, repeats a key or holds a number too large to keep exactly. The kebab buttons in the top bar are View options and Project actions (see Three Tabs). The rules file opens only from these menus. Everything works with the keyboard (Enter or Down arrow opens, arrows move, Escape closes).
• One Project Or A Narrow Panel: With one project in focus the project name is left out of each row. In a narrow panel the name, the Hand off button and all icons but the most severe one move out of the row (hover the icon to see them all) and the row menu holds what no longer fits.
• Folds And Narrow Panels: Every section can be folded, with the keyboard too, and the board remembers which ones you folded. Long lists start folded. The layout reflows down to a panel about 280 pixels wide: no sideways scrolling, buttons under the text, touch targets at least 32 pixels high.
• Linked Work: Needs: lines in documents draw chains between documents and projects; related documents cluster into groups; the board suggests links you can accept or reject.
• Path to GO: Click a project row to see the few steps between it and GO, fastest first, with links to open a document or the rules file, buttons to run lint or tests in the background, and to accept the scan. Steps tick off as they are done.
• Steps I Can Do Now (Sittings): An always-visible filter, Time I have: Any, 15 min, 30 min, 1 hour or Half a day, plus a chip for each thing you have in hand (iPhone, Mac, SQL editor and so on). By default everything is allowed for any time. Your choice is remembered on this machine.
• In Progress: Lists the open documents you are editing right now (unsaved edits or changed in git) that belong to the board, then the documents marked in progress. The list is capped; the rest is counted as "N more".
• Documents With No Rule: A section for documents no rule placed, with the number and the folders they sit in. Add a rule asks which category the folder gets, shows the rule, and writes it to .saropa/release-board.json only after you confirm (a file that does not parse is never touched). Preview shows what the rule would match. The board scans again after a rule is added.
• Since You Last Looked: A strip at the top lists new blockers, cleared blockers and lights that moved, plus standup and since-yesterday report lines.
• Live Evidence: A small flame on a row when the source files a document names have errors or warnings right now. Crash signals in files no document names are listed with a Start a bug document button.
• Tidy: A Ready to tidy box lists finished documents that have not changed for a while, and the tech-debt, branch and bloat reports. A document moves to the archive only after you click and confirm.
• Hand Off: A Hand off entry in the row menu, the group and project menus and the options menu, plus row checkboxes to choose several documents. It opens a side drawer that previews the document as Markdown or JSON for Fix, Plan, Review or Triage. Copy copies one line that points at the saved file (the full text on request). Save to file writes it to .saropa/handoff in the project: never committed, and the last 20 are kept. Run in terminal starts the command in releaseBoard.handoff.terminalCommand in a new terminal. Nothing is sent by the board.
• Prove Overnight: Optional. Runs each project's own lint and test shortcuts once a night while VS Code is open and records fresh evidence.
• Release Train: When more than one project ships together, one row shows the worst light of them and what holds the release.
• Daily Report Evidence: The newest Build status, Dawn lint sweep, Test trend tracker and Dependency freshness reports feed the Build, Lint, Tests and Dependencies marks. Other daily reports add row notes and lines in Tidy and in Since you last looked.
• Release Profiles: Rush, Deliberate or Zero defects decide which severities stop a release.
• Optional Links: Saropa Lints results, Claude sessions per document (Chat Explorer) and the pull requests waiting for your review.
• Future Tab And Research: Deferred and blocked documents are listed under an importance flag, never as problems. Each can carry a research state in its header block (Research: none | needed | in-progress | ready | reviewed) and a one-line Research question:. Hand off all saves one research hand-off for the flagged documents to .saropa/handoff and copies it: pass it to your AI, confirm, and the documents become in-progress. A document with ready research shows Research ready, not reviewed until you press Mark reviewed.

🎨 Customize

• Name, Icon, Color, Tags — One Screen: Rename any shortcut, pick from a searchable codicon grid, tint it with a theme-aware color, and tag it, all from a single panel with a live preview.
• Theme-Tuned Palette: Each color swatch is pre-tuned for light, dark, and high-contrast themes, so a chosen tint always stays legible.
• Tag-Driven Filtering: Tags feed the mode filter in the Shortcuts view, so customization doubles as organization.

Technical Capabilities

• Workspace Management: Group configurations with drag-and-drop support, customize codicons/colors, or swap between isolated tool sets.
• Project Files Pane: Surfaces notable files scanned from the open project, with file-type icons/colors and modification-time tracking.
• Dashboard: A process-monitor webview with analytics and trend tabs for background-run activity, alongside the script output it tracks.

Project vs Global Scopes

Execution Fallbacks

VS Code trees lack native double-click handling, so the extension monitors click gaps via saropaWorkspace.doubleClickMs (default 400 ms). If click intervals feel erratic on your hardware, use the explicit inline play button or the right-click Run menu for deterministic execution.

Settings Reference (saropaWorkspace.*)

A representative sample below — open Settings → Extensions → Saropa Workspace (or search saropaWorkspace. in the Settings UI) for the complete, current list.

{
  "saropaWorkspace.interpreterDefaults": {
    ".py": "python",
    ".js": "node",
    ".ts": "ts-node",
    ".sh": "bash"
  }
}

Command Reference

A representative sample below — open the Command Palette and type Saropa Workspace: for the complete, current list.

Part of the Saropa Suite

Contact & License

• Support: dev@saropa.com
• License: MIT — open usage.

GitHub | Issues | Saropa Suite