GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — fix(comparisons): make sandbox and session-policy rows binary by waleedlatif1 · Pull Request #6524 · simstudioai/sim

Conversation

@waleedlatif1

@waleedlatif1 waleedlatif1 commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Re-derive codeSandboxRuntime and sessionPolicy as strict binary Yes:/No: across Sim and all 20 competitors. A comparison row answers a binary question; the three-state Partial: / Not publicly documented: framing made every row read as a hedge
  • Constraints are preserved — they move into the value's later sentences and detail, which ship in full to crawlers and screen readers and are reachable via the row's source link
  • Sources untouched; they were verified against live vendor pages in feat(comparisons): add code-sandbox and session-policy rows #6517

The rule

A capability is Yes when any documented, vendor-supported path exists. Self-hosted-only, package-layer-only, tier-gated, env-var-configured, and configured in the vendor's own identity layer (Entra/Power Platform for Microsoft) all count as Yes.

No when the environment/session is vendor-fixed with no documented configuration on any deployment mode, when nothing is documented anywhere, or when the only path is a third-party IdP the vendor doesn't own.

Note this deliberately resolves ambiguity toward the competitor — every former Partial: became a Yes:, not a No:.

Result

Row Yes No
Configurable code sandboxes 17 4 (Dust, Gumloop, Copilot Studio, Workato)
Custom session policy 12 9

Type of Change

  • Bug fix

Testing

Type-check and biome clean (the only tsc errors in my worktree are stale-symlink @sim/emcn icon exports from #6523, unrelated to this diff — zero errors in lib/compare). Diff is +52/-50 across 19 files: a surgical verdict rewrite. An audit pass diffed each file against git to confirm no version number, limit, env-var name, or plan gate was dropped in the reframing.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

greptile-apps[bot] reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@waleedlatif1
fix(comparisons): make sandbox and session-policy rows binary
0783ad9
A comparison row answers a binary question, so the three-state
Partial/Not-publicly-documented framing was wrong. Re-derive both rows
against one rule: a capability counts as Yes when any documented,
vendor-supported path exists, including self-hosted-only, package-layer
only, tier-gated, and configured in the vendor's own identity layer.
Undocumented and vendor-fixed become No. Every constraint moves into the
value's later sentences and detail rather than the verdict.
@vercel

vercel Bot commented Aug 11, 2026

Copy link
Copy Markdown

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

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Skipped Skipped Aug 11, 2026 3:03am

Request Review

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@cursor

cursor Bot commented Aug 11, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

PR Summary

Low Risk
Content-only edits to static comparison marketing data; no runtime, auth, or API behavior changes.

Overview
Comparison competitor data for configurable code sandboxes (codeSandboxRuntime) and custom session policies (sessionPolicy) is reframed from hedged labels (Partial:, Not publicly documented:) to strict Yes: / No: verdicts in value and shortValue, across Sim and 20 competitor profiles under apps/sim/lib/compare/data/.

Yes when any documented vendor-supported path exists (self-hosted-only, package-layer-only, tier-gated, env-var-driven, or Microsoft Entra/Power Platform identity layers still count). No when the runtime or session is fixed with no documented admin control, nothing is documented, or only a third-party IdP sets timeouts. Nuance (plan gates, deployment mode, limits) stays in detail and longer value text; sources and confidence are unchanged.

Sim’s sandbox row wording is tightened (Max/Enterprise gating upfront); session policy shortValue now notes Enterprise. Former partial sandbox rows (e.g. Claude Cowork, Flowise, n8n, Make, Power Automate desktop) move to Yes with scope preserved; undocumented session controls (CrewAI, Dust, Gumloop, OpenAI AgentKit, Pipedream, StackAI, Vellum) move to explicit No; self-hosted JWT/env session controls move to Yes.

Reviewed by Cursor Bugbot for commit 0783ad9. Configure here.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@greptile-apps

greptile-apps Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR converts configurable-sandbox and session-policy comparison entries to strict binary Yes/No verdicts while retaining deployment, tier, and runtime constraints in their explanatory copy.

  • Reclassifies package-layer, self-hosted, tier-gated, and vendor-owned identity controls as Yes.
  • Reclassifies undocumented or vendor-fixed session controls as No.
  • Updates Sim’s summaries to expose its applicable plan constraints.
  • One Gumloop verdict conflicts with both its cited vendor statement and the threshold applied to sibling entries.

Confidence Score: 4/5

The Gumloop session-policy verdict should be corrected before merging because it publishes a false negative under the PR’s own binary classification rule.

Gumloop is assigned a negative verdict even though its cited first-party documentation states that configurable session timeouts are supported and sibling entries accept the same level of evidence.

Files Needing Attention: apps/sim/lib/compare/data/competitors/gumloop.ts

Important Files Changed

Filename Overview
apps/sim/lib/compare/data/competitors/gumloop.ts Reclassifies session policy as No despite quoting Gumloop’s vendor documentation that configurable session timeouts are supported.
apps/sim/lib/compare/data/competitors/power-automate.ts Reframes desktop dependency-loading support as Yes while preserving the fixed-cloud-runtime distinction.
apps/sim/lib/compare/data/competitors/crewai.ts Reframes AMP package declarations as a qualifying Yes and retains the absence of a first-party sandbox.
apps/sim/lib/compare/data/sim.ts Moves Sim’s plan gating into the leading sandbox and session-policy summaries without changing capabilities.

Reviews (1): Last reviewed commit: "fix(comparisons): make sandbox and sessi..." | Re-trigger Greptile

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

greptile-apps[bot]
greptile-apps Bot reviewed Aug 11, 2026
View reviewed changes
Comment thread apps/sim/lib/compare/data/competitors/gumloop.ts
Comment on lines 982 to 984
value:
'Not publicly documented: no admin-configurable session lifetime or idle timeout appears in Gumloop\'s public documentation. The only primary-source statement is a single bullet on the Enterprise SSO page listing "Session Management: Configurable session timeouts and secure token handling." No admin setting name, configuration steps, default session lifetime, idle-timeout value, or absolute-cap value is published anywhere in Gumloop\'s docs, security page, or trust center.',
'No: no admin-configurable session lifetime or idle timeout appears in Gumloop\'s public documentation. The only primary-source statement is a single bullet on the Enterprise SSO page listing "Session Management: Configurable session timeouts and secure token handling." No admin setting name, configuration steps, default session lifetime, idle-timeout value, or absolute-cap value is published anywhere in Gumloop\'s docs, security page, or trust center, so a buyer has no documented control to rely on.',
detail:

@greptile-apps greptile-apps Bot Aug 11, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Gumloop session verdict contradicts source

When the comparison renders Gumloop’s session policy, the changed No: prefix classifies it as unsupported even though Gumloop’s cited Enterprise SSO documentation states that configurable session timeouts are supported, causing a false negative in the table and structured comparison data.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@waleedlatif1 waleedlatif1 closed this Aug 11, 2026
@waleedlatif1
waleedlatif1 deleted the fix/comparison-binary-facts branch August 11, 2026 03:13

This branch was previously deployed

1 inactive deployment
Preview — 0783ad96 Deployed Aug 11, 2026 by vercel[bot]
View deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@greptile-apps greptile-apps[bot] greptile-apps[bot] left review comments

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@waleedlatif1
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.