49 of 51 criteria have a sourced finding; 38 were also cross-checked by a second agent. Every comparison that includes Paradev links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Paradev, formerly Superset, has macOS desktop, experimental Linux, CLI and iPhone/iPad clients. Windows and Android remain unavailable. Cloud workspaces are on Team/Ultra; local phone access requires its host online.
Scope
Surfaces: Paradev desktop, Paradev CLI and host server, Paradev iPhone app · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: iPhone and iPad app requires Paradev Pro; desktop and CLI available on all plans · OS: macOS, Linux (experimental) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No installed client or cross-device scenario run.
iPhone/iPad requires iOS/iPadOS 26+ and Pro or higher; Android is waitlisted.
No supported web dashboard; SDK/CLI are separate programmable clients.
Mobile apps [partial] iPhone and iPad app is on the App Store (changelog Sep 28 2026; mobile page; install docs; FAQ) and requires iOS 26 or iPadOS 26 and Paradev Pro. Android is not available (waitlist). Push notifications are coming (FAQ) and are not claimed. Sources: superset:mobile-nov07, superset:d-install-20261107, superset:changelog-nov07, superset:d-faq-nov07.
Browser [unsupported] FAQ states there is no supported web dashboard for workspaces. Shared Pages links are readable in a browser but are not workspace control. Sources: superset:d-faq-nov07.
Mobile browser [unknown] Mobile browser: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Editor extensions [unknown] Editor extensions: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Task actions [partial] The mobile page describes starting agents, following them live and reviewing diffs. Remote Access docs say a phone or tablet can continue terminal sessions, send prompts, review diffs and merge PRs in a workspace. No action-parity test was run. Sources: superset:mobile-nov07, superset:remote-nov07.
Notifications [partial] Desktop notification sounds and macOS dock badges for finished/waiting agents; FAQ says iPhone push notifications are coming, so none are documented today. Sources: superset:d-status-nov07, superset:d-faq-nov07.
Cross device continuity [partial] Other signed-in devices and the iPhone reach workspaces on a host through the relay; the host computer must stay awake, online and running Superset. Sources: superset:remote-nov07, superset:mobile-nov07.
Paradev documents 22 built-in terminal agents, custom CLI agents and mixed-harness orchestration. Status and session integration vary by agent; the newer chat interface supports four harnesses and is still labelled experimental in the November 1 changelog. The pinned built-in terminal registry explicitly includes Antigravity agy.
Scope
Surfaces: Paradev desktop · Version: Targeted first-party source check 2026-11-13. New implementation findings are pinned to 624219c3c6a5428aec38b5f13f040cc0fc087010. Unchanged atomic answers retain the individual source dates and revisions in their cited evidence. · Plan: Not specified · OS: macOS, Linux (experimental) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
Model providers [partial] Provider gateway instructions cover Claude Code with OpenRouter, Vercel AI Gateway, Bedrock, Vertex, Foundry and Anthropic-compatible APIs. Other harnesses use their own provider settings; chat has its own Anthropic key flow. No universal provider matrix was verified. Sources: superset:providers-chk2-nov07, superset:chat-chk2-nov07.
Custom adapters [supported] Settings > Agents > Add agent > Custom agent adds a command with prompt transport and resume/fork args. Custom agents receive a workspace, worktree and terminal; built-in integrations are not implied. Sources: superset:agents-chk2-nov07, superset:agent-support-chk2-nov07.
Mixed harness operation [supported] Documentation permits Claude Code or Codex coordinators with mixed-agent workers and cross-agent handoff. This is documented, not observed mixed-harness execution. Sources: superset:orchestration-chk2-nov07, superset:sessions-chk2-nov07.
Vendor credits [unsupported] FAQ states Superset never proxies model calls and does not bill model usage; the provider bills the user directly, so no Superset-supplied model credits. Sources: superset:d-faq-nov07, superset:pricing-nov07.
Local models [unknown] Local models: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Account switching [partial] The Usage page can hold several Claude Code and Codex logins, each with its own quota card. Make default picks the account new launches use; a running agent keeps its account until relaunched. Sources: superset:d-usage-nov07.
Vendor account requirement [unknown] Vendor account requirement: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Provider restrictions [unknown] Provider restrictions: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Onboarding detects git, gh and installed agents; projects come from a local folder or Git URL and must be git repositories. GitHub is the fully supported host; managed cloud workspaces require Team or Ultra.
Scope
Surfaces: Paradev desktop, User-provided remote host via relay, Paradev managed Cloud workspaces · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Local projects need Git and an installed agent.
Managed cloud requires Team/Ultra, connected GitHub repos and agent sign-in; no onboarding timing test.
7 atomic answers
First task setup [supported] First launch checklist covers gh sign-in, agent detection and adding a project; Cmd+N then starts a workspace with a prompt. Sources: superset:d-install-20261107, superset:d-first-nov07.
No git [unsupported] Projects must be git repositories (FAQ: every project must be a git repository). A folder without git can run as a session workspace instead, which has no project, branch or PR link. Sources: superset:d-faq-nov07, superset:d-workspaces-nov07.
Local git without remote [partial] FAQ says remotes other than GitHub work locally; a repo with no remote at all is not addressed. Sources: superset:d-faq-nov07.
Hosted git [partial] GitHub is fully supported through gh; other hosts work locally and cross-machine project identity is tied to GitHub; GitLab support is only a tracking issue. Sources: superset:d-faq-nov07, superset:repo-issues-nov07.
Prerequisite guidance [supported] Onboarding uses live detection so the checklist updates as git, gh and agents are installed or signed in. Sources: superset:d-install-20261107.
Managed cloud setup [partial] Managed cloud needs a Team or Ultra plan, a connected GitHub repository and agent sign-in. Setup uses environments of one to 20 repositories. Sources: superset:cloud-current-nov07, superset:d-workspaces-nov07.
Byo vps onboarding [supported] Headless install, superset start --daemon and systemd guidance cover a user-provided server without the desktop app. Sources: superset:d-host-nov07, superset:remote-nov07.
Current CLI and OAuth HTTP MCP tools cover tasks, workspaces, agents, terminals, pages, automations and hosts. TypeScript SDK is early alpha, explicitly not for production; no stable REST contract is established.
Scope
Surfaces: Paradev CLI and host server, Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
SDK is early alpha and explicitly not meant for production; current CLI docs do not label CLI Beta.
No installed API/CLI or authenticated MCP scenario ran.
The undated roadmap SDK & public API label is not a stable REST contract.
8 atomic answers
Cli [supported] Installed superset/paradev commands manage tasks, workspaces, terminals, agents, pages, automations and hosts; current CLI docs do not apply a Beta label. Sources: superset:gap07-cli.
Api [partial] HTTP MCP is documented, and the early-alpha SDK exposes configurable API/relay base URLs. A stable independent REST endpoint contract remains unestablished. Sources: superset:gap07-programmatic, superset:gap07-sdk.
Sdk [partial] Early-alpha @superset_sh/sdk supports task/workspace/project/host/agent/terminal/automation operations; docs say not production-ready and may be removed. Sources: superset:gap07-sdk.
Mcp server [supported] HTTP MCP at api.superset.sh/mcp exposes the current named task, workspace, agent, terminal, page, automation, host and project tools. No fixed tool count is claimed; v1 returns410. Sources: superset:gap07-programmatic.
Webhooks [partial] Automations accept inbound POST webhook triggers using a sset_wh_ token, with no filters or de-duplication. The SDK reference does not mention webhooks. Outbound webhook delivery from Paradev is not documented. Sources: superset:d-automations-nov07, superset:d-sdkref-nov07.
Stability [partial] The SDK is explicitly early alpha and not for production. Current CLI docs carry no Beta label; legacy v1 MCP is removed with410, while the documented v2 path remains supported. Sources: superset:gap07-programmatic, superset:gap07-sdk, superset:gap07-cli.
Current Paradev plugins supply MCP tools and skills with agent-specific support and a vendor credential proxy. The chat /mcp command separately lists configured servers; broader MCP manager/community marketplace remain roadmap items.
Scope
Surfaces: Paradev desktop, Slack and Linear integrations · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
No plugin call or credential boundary test.
MCP manager/community marketplace roadmap scope is broader than the released service-plugin catalog.
7 atomic answers
Mcp client [partial] Built-in chat /mcp lists configured MCP servers from .mastracode/mcp.json, .amp/settings.json or .mcp.json with name, transport and state. Installed plugins add their MCP servers to Claude Code (~/.claude.json) and Codex (~/.codex/config.toml) configs. A general MCP manager is In Progress on the roadmap and not claimed as shipped. Sources: superset:mcp-chat-integration-nov07, superset:plugins-current-nov07, superset:roadmap-2026-09-23-nov07.
Plugins [supported] Install service plugins in the sidebar. Claude/Codex get MCP+skills; Kimi/Vibe/Grok get skills only. User config entries win over managed copies. Sources: superset:plugins-current-nov07.
Custom tools [partial] Custom plugins can proxy an existing Streamable HTTP MCP server and ship skills/scripts; the tool server itself must be operated separately. Sources: superset:gap07-custom-plugins.
Instructions import [supported] Plugin skills and built-in skills are installed into standard agent discovery paths; user-authored copies are not overwritten. Sources: superset:gap07-custom-plugins, superset:gap07-skills.
Authentication [supported] Account-requiring plugins connect through Paradev; local configs point at its proxy and do not contain OAuth tokens. Sources: superset:plugins-current-nov07.
Integration owner [supported] Paradev manages plugin installation, config entries and credential proxy; the external MCP server owns its tools. Organization repositories are synced by an owner/admin. Sources: superset:gap07-custom-plugins, superset:gap07-org-plugin-policy.
At the pinned commit the desktop app is Electron 41 and the mobile app is an Expo / React Native project.
Scope
Surfaces: Pinned default-branch source · Version: fc44d327a79cb87f55762f8ec3913d1a366ada26 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
source-only
Delivery
native
Checked
2026-10-08 (45 days old)
Agent cross-check
2026-10-09
Default-branch source (package version 1.36.0) may differ from released desktop-v1.37.0 and the App Store binary.
4 atomic answers
Desktop implementation [supported] Electron 41.10.7 in apps/desktop/package.json. Sources: superset:desktop-code.
Mobile implementation [partial] apps/mobile is an Expo / React Native project with expo-router and @expo/ui; shipped binary not inspected. Sources: superset:src-mobile.
Hybrids [unknown] Hybrids: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Native tasks and connected Linear/GitHub issue lists support workspace intake. A Linear custom script launches local workspaces; separate plugin tools read/update Linear. Sync direction and enforcement are not inferred.
Scope
Surfaces: Paradev desktop · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Linear integration is listed under Pro on the pricing page; the Free plan lists no Linear integration · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No authenticated tracker-write or sync-conflict test.
The Linear custom-tool script is separate from native task records and plugin issue tools.
9 atomic answers
Local creation [supported] New task modal and native create operation with title, description, status, priority and assignee. Sources: superset:tasks-nov07, superset:task-code-nov07.
Prompt intake [partial] The Slack agent and MCP tasks_create can create tasks from natural-language requests; no desktop prompt-to-task flow documented. Sources: superset:d-slack-nov07, superset:d-mcp-nov07.
External import [supported] Linear issues are listed beside native tasks (changelog Oct 4: browse and create Linear issues in Tasks with list and board views, import as a Superset task, each member connects their own Linear account); GitHub issues have their own source tab with Add to workspace. Sources: superset:tasks-nov07, superset:changelog-nov07.
Chat git triggers [partial] Slack mentions spawn a workspace and agent; a Linear local script can create or reuse a workspace per issue. Sources: superset:d-slack-nov07, superset:d-linear-nov07.
Authoritative tracker [partial] An organization owner selects Linear or Superset as the tracker; --tracker can override the selection per CLI command. Full two-way synchronization semantics remain unverified. Sources: superset:cli-tasks-tracker-nov07.
Sync [unknown] The Tasks page describes issues synced from the connected Linear workspace. An organization owner selects Linear or Superset as the tracker, with --tracker overrides per command; full two-way synchronization semantics remain unverified. Sources: superset:d-linear-nov07, superset:tasks-nov07, superset:cli-tasks-tracker-nov07.
Supported edits [partial] With Linear connected, linking an issue or opening its task in a workspace moves the Linear issue to In Progress. Sources: superset:d-linear-nov07.
External roundtrips [partial] The CLI creates, updates and deletes Linear issues through the invoking member's own Linear connection (delete archives them, CLI reference, Tasks). The In Progress write-back and branch-name autolink are documented. Sources: superset:d-linear-nov07, superset:cli-tasks-tracker-nov07.
Task projects group tasks with state, lead and dates in the default-branch source (source-inspected at fc44d327: schema taskProjects and taskProjectTasks, plus TaskRecordScreen project setters). They are not shown in the docs, and the Tasks page project filter applies to Linear issues. Parent/child and dependency features were not found.
Scope
Surfaces: Paradev desktop · Version: Documentation read 2026-10-09; latest release desktop-v1.37.0 (2026-10-08) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
Absence of parent or dependency fields in the default-branch schema is not proof of absence in the product.
Task project fields come from the default-branch schema at fc44d327, not from the released desktop build.
9 atomic answers
Epics [partial] Task projects (planned state, lead, start and target dates) group tasks in the default-branch source at fc44d327; source-inspected only, not in the docs; not labelled epics. Sources: superset:src-tasks-schema.
Hierarchy [unknown] Hierarchy: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Blockers [unknown] Blockers: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Readiness [unknown] Readiness: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Enforcement [unknown] Enforcement: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
State propagation [unknown] State propagation: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Task to epic [unknown] Task to epic: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Identity retention [unknown] Identity retention: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Workflow constraints [unknown] Workflow constraints: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Source schema shows task projects and no parent or dependency columns on tasks at the pinned commit.
Bundled Superset skills are installed into agents, and a session can be handed to another agent with its last 36,000 characters of terminal context.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
Project instruction import, memory and provenance are not documented.
Handoff sends unredacted terminal context.
10 atomic answers
Instructions [partial] Paradev-managed skills teach agents to use orchestration, setup, pages and feedback. This does not establish project-wide maintained memory. Sources: superset:gap07-skills.
Skills [partial] Desktop installs managed Superset skills into Claude Code and shared agent skill folders and keeps them updated. Sources: superset:d-skills.
Project docs [unknown] Project docs: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Memory [unknown] Memory: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Scope [partial] Skills are provisioned per machine into the agent discovery directories; organization plugins are visible only within their organization and role settings. Sources: superset:gap07-skills, superset:gap07-org-plugin-policy.
Provenance [partial] Organization plugin sources show the GitHub admin used for sync and recorded plugin versions; this is plugin provenance, not a verified knowledge-memory citation system. Sources: superset:gap07-org-plugin-policy.
Correction [unknown] Correction: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Deletion [unknown] Deletion: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Takeover continuity [partial] Continue with another agent seeds a fresh agent with the last 36,000 characters of context as read-only history; fork copies the conversation but not files. Sources: superset:d-sessions.
Design mode sends screenshots and DOM context to agents and the Slack agent searches the web with citations; code indexing was not found.
Scope
Surfaces: Paradev desktop, Slack and Linear integrations · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
No code search, indexing or conflict detection documented.
10 atomic answers
Code search [partial] File search and cross-open-workspace search are documented; no code-symbol/architecture retrieval guarantee or indexing method is stated. Sources: superset:gap07-editor-search.
Indexing [unknown] Indexing: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Roadmap lists project-wide search under Exploring.
External knowledge [partial] Slack agent can search the web and read channel history. Sources: superset:d-slack.
Multimodal inputs [partial] Browser Design mode sends a cropped screenshot with DOM, computed styles and React component metadata to an agent. Sources: superset:d-browser.
Freshness [unknown] Freshness: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Roadmap lists project-wide search under Exploring.
Access scope [unknown] Access scope: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Roadmap lists project-wide search under Exploring.
Api retrieval [unknown] Api retrieval: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Roadmap lists project-wide search under Exploring.
Citations [partial] Slack agent web search returns citations. Sources: superset:d-slack.
Conflict detection [partial] If an agent changes an open file with unsaved edits, the editor shows an external-change banner and compare/reload/overwrite choices. It does not merge edits automatically. Sources: superset:gap07-editor-search.
Review enforcement [unknown] Review enforcement: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Roadmap lists project-wide search under Exploring.
Native tasks support create, edit, priority, assignee, labels (with label hierarchy), semantic search, project/state/assignee/label filters, list and board views, and explicit dispatch to a workspace. Task-project records beyond the documented project filter are source-inspected only (fc44d327). Comments are evidenced only by the pinned desktop source (fc44d32), not by docs.
Scope
Surfaces: Paradev desktop, Pinned default-branch source · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
Comments are evidenced by pinned desktop code, not docs or a released-build test.
Archive/reopen and idea parking not documented; epics unverified.
Discuss [partial] Desktop task timeline has a comment composer and threaded replies in the pinned desktop source (fc44d32); docs only mention task activity. Sources: superset:src-task-ui.
Label [supported] Tasks carry labels; a path-style label (acme/website) creates parent labels, and the Label filter shows a tree that matches sub-labels. The desktop task record screen adds and removes labels (source fc44d32). Sources: superset:tasks-filters-chk1, superset:gap07-task-records, superset:src-task-ui.
Filter [supported] The Tasks view filters by project, task state, assignee and label, and filters persist between visits. Sources: superset:tasks-filters-chk1.
Archive [unknown] Archive: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Reopen [unknown] Reopen: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Project epic views [partial] List and kanban board grouped by status, with a project filter (docs). Task-project records (state, lead, dates) are source-inspected only at fc44d327; epics unverified. Sources: superset:tasks-filters-chk1, superset:src-tasks-schema.
Idea parking [partial] Tasks can be created and edited independently of Run in workspace; their initial status may be backlog. No separate idea inbox is documented. Sources: superset:gap07-task-records, superset:gap07-sdk.
Explicit dispatch [supported] Run in workspace picks project and agent, one workspace per task, optional auto-run. Sources: superset:tasks.
Task session separation [supported] Task records exist before a separately invoked Run in workspace creates an agent workspace. Workspaces can link a taskId; a task is not the terminal conversation. Sources: superset:gap07-task-records, superset:gap07-sdk.
Durable states [partial] Configurable task statuses are listed by the tasks_statuses_list tool and status filter. Sources: superset:d-mcp, superset:tasks.
External tracker requirement [supported] Paradev-native tasks can be created directly; Linear is an alternative tracker selected or overridden through the CLI, not a requirement. Sources: superset:gap07-task-records, superset:gap07-cli.
Agents can list, read, create, update and soft-delete tasks over MCP, CLI and SDK. On a Linear-tracked organization the CLI works on Linear issues unless --tracker superset is passed (CLI reference, Tasks); claiming, dependencies and child tasks were not found.
Scope
Surfaces: Paradev CLI and host server, Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Operations not exercised; no per-agent attribution or conflict behavior documented.
API keys grant full organization access.
14 atomic answers
Shared ids [partial] Tasks are fetched by UUID or slug through MCP and the CLI. Sources: superset:d-mcp, superset:d-cli.
Claim [unknown] Claim: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Assign [supported] Tasks create/update accept assigneeId through the SDK shared backend; CLI tasks similarly update assignment. Sources: superset:gap07-sdk, superset:gap07-cli.
State changes [partial] Status changes via tasks_update with tasks_statuses_list. Sources: superset:d-mcp.
Dependencies [unknown] Dependencies: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Children [unknown] Children: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Results [unknown] Results: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Human visibility [supported] The desktop Tasks detail exposes editable task fields/activity alongside the same native tasks addressed by CLI/SDK. Sources: superset:gap07-task-records, superset:gap07-sdk.
Attribution [partial] SDK task list returns creator and assignee names/images; action-by-action concurrent agent attribution is not established. Sources: superset:gap07-sdk.
Permissions [partial] OAuth token scoped to the active organization; API keys give full organization access; no finer permission levels documented. Sources: superset:d-mcp.
Conflicts [unknown] Conflicts: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Paradev documents parallel agents in separate local worktrees, with sidebar activity and workspace list/board views. Pricing lists unlimited workspaces; simultaneous-agent throughput was not measured.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5 (624219c3c6a5428aec38b5f13f040cc0fc087010); live documentation read 2026-11-07 · Plan: Not specified · OS: macOS, Linux (experimental) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unlimited workspaces is a vendor plan allowance, not a measured concurrency limit.
Status depends on harness hooks; local worktrees do not prevent merge conflicts.
No installed-client concurrency test.
5 atomic answers
Concurrent sessions [supported] AI Agents explicitly describes agents running in parallel in multiple workspaces. No observed concurrency count is claimed. Sources: superset:agents-chk2-nov07.
Concurrent tasks [supported] Separate local project tasks use their own Git worktree, branch and terminals. Cloud workspaces use clones and scratch sessions are distinct. Sources: superset:workspaces-chk2-nov07.
Quotas [partial] Pricing lists unlimited workspaces and projects. That does not establish a maximum simultaneous-agent count; provider limits and host capacity were not measured. Sources: superset:pricing-chk2-nov07.
Observed concurrency [unknown] Observed concurrency: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Status visibility [supported] Sidebar activity shows agents and ports; hooks report running/finished/waiting with harness-specific coverage. November 1 changelog describes saved workspace views and status filters; workspace docs also describe list/board state columns. Sources: superset:status-chk2-nov07, superset:workspaces-chk2-nov07, superset:changelog-chk2-nov07.
Tasks have assignees and can be dispatched to a chosen agent; the Linear script reuses an existing workspace per issue. Claims, queues and routing were not found.
Scope
Surfaces: Paradev desktop · Version: Documentation read 2026-10-09; latest release desktop-v1.37.0 (2026-10-08) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
No ownership enforcement or claim mechanism documented.
7 atomic answers
Human assignment [partial] Task assignee field. Sources: superset:tasks.
Agent assignment [partial] Run in workspace chooses the agent per task. Sources: superset:tasks.
Claims [unknown] Claims: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Queues [unknown] Queues: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Routing [unknown] Routing: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Duplicate prevention [partial] Re-running the Linear script on the same issue reuses the existing workspace. Sources: superset:d-linear.
Ownership enforcement [unknown] Ownership enforcement: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Paradev bundles the superset:orchestrate skill: a Claude Code or Codex coordinator launches mixed-agent workers via CLI in separate workspaces, reads/sends terminal messages and verifies structured completion or blocked reports.
Scope
Surfaces: Paradev desktop, User-provided remote host via relay · Version: desktop-v2.0.5 (624219c3c6a5428aec38b5f13f040cc0fc087010); live documentation read 2026-11-07 · Plan: Remote relay access requires Pro or a higher plan · OS: macOS, Linux (experimental) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Installed orchestration skill, distinct from provider-native subagents and future orchestration-chat UI.
No delegated run, child identity check, completed-child reopening or result-retention fixture.
Model/effort overrides are documented; orchestration selection policy is not.
Model harness effort [partial] CLI and MCP launches accept agent, model and reasoning-effort overrides subject to harness support. Orchestration docs do not establish an automatic model-selection policy. Sources: superset:cli-chk2-nov07.
Messages [supported] The coordinator reads worker terminals and sends prompts or dependency results through CLI terminals read/send. Sources: superset:orchestration-chk2-nov07.
Results return [supported] Workers report structured completion or blocked messages for coordinator verification before integration. Sources: superset:orchestration-chk2-nov07.
Cross harness [supported] Claude Code or Codex can coordinate any mix of supported worker agents. Sources: superset:orchestration-chk2-nov07.
Orchestration owner [supported] An agent using the bundled superset:orchestrate skill drives the CLI; this is skill-based orchestration. Sources: superset:orchestration-chk2-nov07.
Activation [supported] Desktop provisions skills at launch; standalone agents install paradevai/skills or the Paradev Claude marketplace. Natural-language skill selection is documented. Sources: superset:skills-chk2-nov07.
Authentication [partial] CLI documents browser OAuth or API-key authentication and active-organization selection. Remote hosts register through authenticated relay access and explicit host grants. No end-to-end delegated auth fixture was run. Sources: superset:cli-chk2-nov07, superset:remote-chk2-nov07.
Retained results [partial] Docs describe a branch and PR per worker. Saved transcripts can be retrieved for Claude/Codex, but complete post-session child findings and their retention period were not tested. Sources: superset:orchestration-chk2-nov07, superset:sessions-chk2-nov07.
Followup [supported] Coordinator sends follow-ups through terminals send. Reopening a completed child and following up after completion was not tested. Sources: superset:orchestration-chk2-nov07.
Invocation [partial] Docs show natural-language fan-out examples and skills selected from context, including running three refactors in parallel. Neither documented invocation nor the shared natural-language fixture was executed. Sources: superset:orchestration-chk2-nov07, superset:skills-chk2-nov07.
Current automations combine schedules and provider-event triggers, up to 25 per automation, on selected hosts or cloud. A created run records workspace creation, not verified task completion. Schedules are evaluated by the cloud API from its database (desktop-v2.0.11 code); a run needs its target device online through the relay, or a Cloud target, and an offline device misses the run.
Scope
Surfaces: Paradev desktop, Paradev CLI and host server · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07; scheduler code desktop-v2.0.11 23c193a and docs reread 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
Docs conflict, 2026-11-21: the Automations page records an offline-device run as missed and not retried; the FAQ calls it failed and retryable with Retry all. Both agree the run does not happen while the target device is offline.
8 atomic answers
Schedules [supported] RFC5545 schedules with presets; multiple triggers per automation. Sources: superset:d-automations-nov07.
Recurring tasks [supported] Saved automations recur from their configured triggers and target a host or Cloud. Sources: superset:d-automations-nov07.
Completion conditions [partial] Created means a workspace was created, not agent task success. Sources: superset:d-automations-nov07.
Scheduler location [supported] Server-side: a per-minute QStash tick in the cloud API selects due schedule triggers from the server database, enqueues dispatch and advances next_run_at, then hands the run to the chosen device or Cloud. Hosted deployment parity with the pinned code is not verified. Sources: superset:b06-evaluate, superset:b06-automations.
Overlaps [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Client independence [partial] The creating client need not stay open, but a local target device must be online through the relay at fire time; an offline device misses the run. A Cloud target avoids keeping a computer connected. The docs disagree on whether such a run is missed and not retried or failed and retryable. Sources: superset:b06-automations, superset:b06-faq.
Agents can pause for questions, tool approval and plan review; workspaces needing input are flagged and notified; unexpected terminal deaths auto-resume. Pause/stop controls were not found.
Scope
Surfaces: Paradev desktop · Version: Documentation read 2026-10-09; latest release desktop-v1.37.0 (2026-10-08) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
Waiting-for-input signal exists only for some agents.
No steering or escalation tests.
10 atomic answers
Pause [unknown] Pause: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Stop [unknown] Stop: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Resume [partial] Unexpected terminal death resumes automatically for agents with id-based resume; failed resumes show Retry. Sources: superset:d-sessions.
Steer [unknown] Steer: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Notifications [supported] Finished and waiting notifications, sounds and macOS dock badges. Sources: superset:d-status.
Pending decisions [supported] Agents pause in the chat pane for questions, tool approval and plan review and the workspace is flagged Needs attention. Sources: superset:d-agents, superset:d-status.
Escalation [unknown] Escalation: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
A quick task takes a prompt and an agent in one step; agents are configurable and skills are discoverable. Growing-epic and live-role views were not found.
Scope
Surfaces: Paradev desktop · Version: Documentation read 2026-10-09; latest release desktop-v1.37.0 (2026-10-08) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
No hands-on workflow test.
10 atomic answers
Quick task [supported] Cmd+N opens a new workspace where you describe the task and pick an agent; the workspace is created with the prompt and agent. Sources: superset:d-first.
Growing epic [unknown] Growing epic: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Presets [partial] Reusable terminal scripts (saved launches that run from any matching workspace, with an older "presets" name) and per-agent task prompt templates in Settings, Agents. Sources: superset:terminal-scripts-doc, superset:d-agents.
Natural language [unknown] Natural-language invocation of the orchestrate skill was not reproduced on the Oct 9 orchestration read. Sources: superset:orchestration.
Agent configuration [partial] Per-agent command, resume args, model override under Settings > Agents. Sources: superset:d-agents.
In run changes [unknown] In run changes: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Live roles [unknown] Live roles: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Retained relationships [unknown] Retained relationships: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Discoverability [partial] Skills install at launch and are invoked by name in chat (/superset/feedback); agents also pick the right skill from context (skills docs, Using Skills); the onboarding checklist updates live. Sources: superset:d-skills, superset:d-install, superset:skills-auto-select.
Auth friction [unknown] Auth friction: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Local and user-hosted remote execution plus managed Team/Ultra Cloud workspaces. Cloud is independently available from desktop/iPhone/iPad and uses metered memory-hours.
Scope
Surfaces: User-provided remote host via relay, Paradev desktop, Paradev managed Cloud workspaces · Version: Paradev 2.0.6 (changelog source retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-12
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
Byo remote [supported] User-provisioned hosts use relay and explicit member grants. Sources: superset:remote-nov07.
Self hosted [partial] A paid Remote Access host can run on Linux in the user own cloud account; data/credentials remain there but discovery and device traffic still depend on Paradev relay/API. Sources: superset:gap07-byoc.
Managed cloud [supported] Cloud workspaces left beta in 2.0.6 (2026-11-08) and are included in Team and Ultra; connected GitHub and agent accounts are required. Sources: superset:nov12-cl-206, superset:cloud-current-nov07.
Hybrid [supported] The desktop/mobile clients open either own-host workspaces or vendor cloud workspaces; those have separate provisioning and billing. Sources: superset:gap07-byoc, superset:gap07-cloud-lifecycle.
Provisioning [supported] Create cloud environment with repositories, region and variables, then choose project, branch, environment and size for each cloud workspace. Own servers are installed/configured separately. Sources: superset:gap07-cloud-lifecycle, superset:gap07-byoc.
Resources [supported] Small/Medium/Large: 2/4/8vCPU with 4/8/16GB RAM; all 64GB disk. Larger sizes by request. Sources: superset:cloud-current-nov07.
Region [partial] Cloud environment chooses a region at creation, default nearest; saved snapshot environments keep their region fixed. The guide does not enumerate all locations. Sources: superset:gap07-cloud-lifecycle.
Expiry [partial] Idle stop about one hour with files retained 30 days; archive unarchive window seven days then sandbox deleted. Sources: superset:cloud-current-nov07.
Other device continuation [supported] Cloud workspaces remain running with the laptop closed and can be opened from desktop,iPhone or iPad; own cloud hosts appear in those clients too. Sources: superset:gap07-cloud-lifecycle, superset:gap07-byoc.
Local workspaces are git worktrees on separate branches; the FAQ states they are not sandboxes and share processes, network and files outside the worktree. Managed Cloud workspaces use Vercel-backed sandbox VMs, as described by the pinned cloud engineering guide and provisioning implementation.
Scope
Surfaces: Paradev desktop, User-provided remote host via relay, Paradev managed Cloud workspaces · Version: Targeted first-party source check 2026-11-13. New implementation findings are pinned to 624219c3c6a5428aec38b5f13f040cc0fc087010. Unchanged atomic answers retain the individual source dates and revisions in their cited evidence. · Plan: Not specified · OS: Not specified · Execution modes: local worktree · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
12 atomic answers
Checkout [supported] Each workspace has its own directory. Sources: superset:d-workspaces.
Container [unknown] Container: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Vm [supported] Managed Cloud provisions sandbox VMs through the Vercel Sandbox backend; local worktrees remain unsandboxed. Sources: superset:gaps41-cloud-vm.
Os sandbox [unknown] Os sandbox: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Process [unsupported] FAQ: agents share processes. Sources: superset:d-faq.
Network [unsupported] FAQ: agents share the network. Sources: superset:d-faq.
Secrets [partial] Cloud sandboxes see placeholder agent/GitHub credentials and Paradev adds real credentials to outgoing requests; environment variables/secrets are copied into workspaces, with named provider-token overrides ignored. Sources: superset:gap07-cloud-lifecycle.
Code separation [supported] Separate branches and directories per task; merge conflicts can still occur. Sources: superset:d-workspaces, superset:d-faq.
Security boundary [unsupported] FAQ: worktrees are not sandboxes. Sources: superset:d-faq.
Terminals run in a background daemon that survives app restarts and updates; unexpected agent-terminal deaths auto-resume for agents with a resume command.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Daemon-crash recovery, log locations and multi-day continuity not documented.
Host toggle restarts interrupt terminals.
Transcript reads cover Claude Code and Codex only (agent-sessions docs).
Worker crash [partial] Unexpected terminal death triggers automatic resume for agents with an id-based resume command. Sources: superset:d-sessions.
Service restart [partial] Sessions survive restarts and updates; toggling remote access restarts the host service and interrupts terminals. Sources: superset:d-faq, superset:remote.
Expiry [partial] Cloud idle stop retains files30days; archive can restore disk within7days before deletion. This does not guarantee multi-day task outcome continuity. Sources: superset:gap07-cloud-lifecycle.
Transcript reload [partial] superset agents read returns the saved transcript for a terminal and fails when none can be read. Superset can read saved transcripts for Claude Code and Codex (agent-sessions docs, Read an Agent's Transcript). Sources: superset:d-cli, superset:agent-sessions-transcript.
Process reconnect [supported] Running processes, output history and scrollback are preserved. Sources: superset:d-terminal, superset:d-model.
Task resume [partial] Resume and fork use each agent's native command. Sources: superset:d-sessions.
State reconstruction [partial] Running and PR state persist across restarts; Clear Status resets stale running state. Sources: superset:d-status.
Context loss [partial] Cross-agent continuation includes at most36000characters of recent context and no credential redaction, while native fork retains conversation. Runtime/process restoration after crash depends on native resume support. Sources: superset:gap07-session-lifecycle.
Duplicate actions [partial] Automation documentation explicitly says at-least-once delivery may dispatch a run more than once and prompts should be safe to rerun; exactly-once actions are not promised. Sources: superset:d-automations-nov07.
Multi day continuity [unknown] Multi day continuity: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Setup and teardown commands run per workspace on create and delete (install dependencies there). Run scripts run on demand from the Run button in a dedicated pane, not on workspace creation. Detected ports are forwarded to the same local port unless busy. Superset does not assign per-workspace port ranges. The overview example config copies the root .env file in setup, which is user-written script content. Duplicate-install warnings were not reproduced in the Oct 9 read.
Scope
Surfaces: Paradev desktop, Paradev managed Cloud workspaces, User-provided remote host via relay · Version: desktop-v2.0.5; local/cloud docs retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No dependency caching or collision handling documented.
Only git-tracked files are copied into new workspaces.
10 atomic answers
Dependencies [partial] Setup commands run per workspace on creation; install commands are user-defined in those scripts. Sources: superset:d-setup.
Caches [unknown] Caches: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Session snapshots & revert are Exploring on the roadmap.
Snapshots [supported] Save as environment snapshots a fully started cloud workspace so later workspaces avoid fresh setup. Repositories/region are fixed in the saved environment. Sources: superset:gap07-cloud-lifecycle.
Services [supported] Run commands start dev servers or long-running services on demand in a dedicated pane and can stop/restart without recreating the workspace. Sources: superset:gap07-lifecycle-scripts.
Ports [partial] Detected ports are forwarded to the same local port number unless it is busy ("Use another port"). "Superset does not assign per-workspace port ranges." Sources: superset:d-ports, superset:d-trouble, superset:setup-ports-quote.
Secrets [partial] Setup-script examples copy the root .env into each workspace with cp "$SUPERSET_ROOT_PATH/.env" .env (overview and Node.js examples); the Docker and full-config examples do not. This is user-written script content, not a built-in secrets feature. Sources: superset:setup-env-example.
Duplicate installs [partial] Fresh cloud environments start clean and rerun setup; a saved ready-workspace snapshot can avoid that repeated setup. No general shared package-cache contract is stated. Sources: superset:gap07-cloud-lifecycle.
Collisions [partial] Local workspace ports are discovered, not allocated. Setup scripts can reserve ranges; remote forward conflicts offer another free local port. Concurrent service isolation was not tested. Sources: superset:gap07-ports.
Remote setup [supported] Headless host server installer and systemd guidance. Sources: superset:d-host.
Automatic repair [unknown] Automatic repair: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. Session snapshots & revert are Exploring on the roadmap.
Cloud GB-hour usage limits are checked at start/wake and during execution; a running workspace stops about ten minutes after reaching its limit. Other time/turn/token budgets remain unestablished.
Scope
Surfaces: Paradev managed Cloud workspaces · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
8 atomic answers
Time limits [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Turn limits [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Token limits [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Spend limits [supported] Cloud usage is metered in GB-hours against the organization limit. Sources: superset:cloud-current-nov07.
Timeouts [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Retries [partial] Automation Run now/Retry all manually redispatch failed runs; missed offline runs are not retried automatically and schedule advances. Unexpected agent terminal death has native resume plus Retry on failure. Sources: superset:d-automations-nov07, superset:gap07-session-lifecycle.
Provider failures [partial] A failed native agent resume shows Failed to resume and a Retry action; exact provider error/backoff handling is not established. Sources: superset:gap07-session-lifecycle.
Enforcement [supported] Limit checked on start/wake and while running; running workspace stops about ten minutes after it reaches the limit. Sources: superset:cloud-current-nov07.
Usage shows local Claude Code and Codex token cost, quotas and per-model/workspace breakdowns; automation run history shows failures; logs and traces beyond that were not found.
Scope
Surfaces: Paradev desktop · Version: Documentation read 2026-10-09; latest release desktop-v1.37.0 (2026-10-08) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
Usage is local host only and covers Claude Code and Codex only.
Traces [unknown] Traces: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Failure reasons [partial] Failed runs have two documented causes: target device offline at fire time, or handoff broke. The error shows inline under the run, selectable for copying (automations docs, Runs). Sources: superset:d-automations, superset:d-status, superset:automations-run-errors.
Usage export [unknown] Usage export: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Task stats [unknown] Task stats: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Agent stats [partial] Token cost split between Claude Code and Codex. Sources: superset:d-usage.
Project stats [partial] Workspace and project drilldown. Sources: superset:d-usage.
Time stats [partial] 7, 30 and 90 day ranges. Sources: superset:d-usage.
Usage estimates token costs from local session logs across supported agents, with workspace/model/session drilldown and five-minute subscription quota meters. Cloud metering is separately shown in Billing; remote hosts are not aggregated.
Scope
Surfaces: Paradev desktop · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Local Usage does not aggregate remote hosts.
Token cost is API-equivalent estimate, not the subscription bill.
No billing reconciliation or workload test.
14 atomic answers
Task cost [partial] API-equivalent estimates can drill down by workspace and session; not subscription invoices. Sources: superset:d-usage-nov07.
Session cost [partial] Workspace drilldown lists top sessions by cost. Sources: superset:d-usage-nov07.
Child cost [unknown] Child cost: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Epic cost [unknown] Epic cost: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Harness aggregation [partial] Token-cost estimates cover Claude Code, Codex, OpenCode, Grok, Cursor Agent, Copilot, Devin, Muse Code, Pi, Oh My Pi, Antigravity, fx and Hermes. Quota meters cover Claude Code, Codex, Grok, Antigravity and OpenCode logins. Sources: superset:d-usage-nov07.
Billed vs estimated [supported] Costs are estimates at API list prices; subscription usage shows $0 cost to the user. Sources: superset:d-usage-nov07.
Granted organization members can open the same remote host workspaces and send input to their shared agent terminals. Shared prompting uses host access grants and requires the host awake/online; live presence and input-conflict handling remain unestablished.
Scope
Surfaces: User-provided remote host via relay · Version: Targeted first-party source check 2026-11-13. New implementation findings are pinned to 624219c3c6a5428aec38b5f13f040cc0fc087010. Unchanged atomic answers retain the individual source dates and revisions in their cited evidence. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
11 atomic answers
Visibility [partial] Terminals, agent runs and diff viewer are proxied to granted members. Sources: superset:remote-nov07.
Discussion [unknown] Discussion: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Comments [partial] Pages let teammates comment on pinned elements and agents reply. Sources: superset:d-pages-nov07.
Presence [unknown] Presence: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Coprompting [supported] Granted users invoke the same host terminal writeInput operation by workspace/terminal ID, without a creator-only restriction. Sources: superset:gaps41-shared-host.
Ordering [unknown] Ordering: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Conflicts [unknown] Conflicts: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Attribution [unknown] Attribution: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Permissions [partial] Host access is granted per organization member. Sources: superset:remote-nov07.
Plan restrictions [supported] Remote access is listed under Pro. Sources: superset:pricing-nov07.
Remote hosts have explicit member grants with owner promotion and removal; Enterprise lists SAML SSO and SCIM.
Scope
Surfaces: User-provided remote host via relay · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No unauthorized-access test; SSO/SCIM only vendor-listed.
Unauthorized access [partial] Only owners/admins add organization plugin repositories; setting a role Unavailable immediately blocks plugin tools. This is plugin access control, not a tested complete project-RBAC boundary. Sources: superset:gap07-org-plugin-policy.
Revocation [supported] Owner can remove members from a host. Sources: superset:remote-nov07.
Plan scope [supported] SSO and SCIM are Enterprise-only; remote access is Pro. Sources: superset:pricing-nov07.
Agents can pause for tool approval in the chat pane. When an agent needs files outside its workspace, Superset prompts in chat so you can approve or deny the request inline (agent-integration docs, Sandbox Access). Policy, network and secret approvals were not found.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
Approver identity, lifetime and enforcement not documented.
14 atomic answers
Command [unknown] Command: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Tool [partial] Agents pause for tool approval in the chat pane. Sources: superset:d-status.
Network [unknown] Network: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Secret [unknown] Secret: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Approver identity [partial] Page plugin calls run as the signed-in viewer through their own connected account; this does not establish attributed command-approval logs. Sources: superset:gap07-page-versions.
Lifetime [partial] Page/plugin consent persists for every tool of that plugin, including writes and future versions of the page; no per-command expiry is specified. Sources: superset:gap07-page-versions.
Allow [partial] Outside-workspace file requests: the prompt lets you approve the request inline (documented; no enforcement test). Sources: superset:sandbox-access-prompt.
Deny [partial] Deny is the other inline choice in the same documented prompt (no enforcement test). Sources: superset:sandbox-access-prompt.
Revoke [partial] The Pages guide explicitly says removing a page tool access from the app is unavailable. Organization plugin Unavailable immediately stops tools for that role. Sources: superset:gap07-page-versions, superset:gap07-org-plugin-policy.
Tunnels [supported] Remote workspace traffic and forwarded TCP ports traverse Paradev relay; turning access off restarts/stops host service and interrupts host-backed work. Sources: superset:remote-chk2-nov07.
Defaults [partial] Remote relay access is off by default; a new organization plugin is available only to owners/admins. These are access defaults, not universal harness command policy. Sources: superset:gap07-org-plugin-policy, superset:faq-chk2-nov07.
Safer modes [unknown] Safer modes: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Enforcement [unknown] Enforcement: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Approvals [unknown] Approvals: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Edits [partial] Republishing a Page creates a version; earlier versions remain readable to authorized users. This is document history, not a full workspace activity audit. Sources: superset:gap07-page-versions.
Discussion [supported] Pinned Page comment threads include agent replies and resolved/open state, with context sent to listening agents. Sources: superset:gap07-page-versions.
Decisions [unknown] Decisions: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Cross user persistence [partial] Organization members share the same Page link/version history and comment threads; public anonymous readers receive only the selected shared version. Sources: superset:gap07-page-versions.
Export [partial] pages pull can retrieve a chosen published version; no bulk audit/activity export is established. Sources: superset:gap07-page-versions.
Mutability [partial] A Page source path republishes into the same page with new version history, while shared links can follow latest or stay pinned. This is not tamper-evident audit retention. Sources: superset:gap07-page-versions.
Retention [unknown] Retention: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Integrity [unknown] Integrity: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Evidence navigation [partial] Check list links to GitHub runs. Sources: superset:d-prs.
Comments [supported] Review tab and PR comment thread with reply composer. Sources: superset:d-diff, superset:d-prs.
Request changes [partial] Select diff lines and send feedback to a running/new agent, optionally posting on GitHub; the agent receives file, range and side. A complete review-decision fixture was not run. Sources: superset:gap07-pr-review.
Shipping guidance [partial] PR header offers Start Workspace and Merge; Changes menu offers applicable commit/push/createPR actions. No exact-revision acceptance gate is documented. Sources: superset:gap07-pr-review, superset:diff-chk2-nov07.
Effort [unknown] Effort: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Missed evidence [unknown] Missed evidence: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Keyboard [unknown] Keyboard: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Granted teammates can open authorized remote workspaces through the relay; separately, a session can be handed to another agent. Co-prompting, human takeover ordering and offline-owner continuity are not documented.
Scope
Surfaces: User-provided remote host via relay · Version: Documentation read 2026-10-09; latest release desktop-v1.37.0 (2026-10-08) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
Co-prompting, full takeover and ordering unverified.
Remote workspace unavailable when the host is offline.
12 atomic answers
Ongoing takeover [unknown] Ongoing takeover: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Same task [unknown] Same task: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Session history [unknown] Session history: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Decisions [unknown] Decisions: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Artifacts [unknown] Artifacts: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Permissions [partial] Per-host member grants. Sources: superset:remote.
Runtime context [partial] Terminals, runs and diff via relay. Sources: superset:remote.
Owner disconnect [partial] Host must be awake and online; offline host is shown Offline. Sources: superset:remote, superset:d-trouble.
Ownership [unknown] Ownership: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Attribution [unknown] Attribution: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Context loss [unknown] Context loss: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Harness transfer [partial] Continue with another agent and fork handoffs. Sources: superset:d-sessions.
Paradev documents split/unified and binary diffs, versioned Pages with workspace lists and retrieval, browser screenshots and local/remote previews. A general retained-evidence gallery, exact code-revision binding and completed-child review retrieval were not verified.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5 (624219c3c6a5428aec38b5f13f040cc0fc087010); live documentation read 2026-11-07 · Plan: Not specified · OS: macOS, Linux (experimental) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Pages is a browsable document collection, not established as a gallery for every artifact type.
Recordings, retained test/reviewer outputs, exact code-revision binding and full completed-child findings remain unverified.
No installed-client retrieval or prompt-leakage fixture was run.
13 atomic answers
Diffs [supported] Split/unified diffs are documented. The September 6 changelog documents image before/after views and video/PDF previews behind a Preview button. Sources: superset:diff-chk2-nov07, superset:changelog-chk2-nov07.
Documents [partial] Pages publish HTML documents/directories, list workspace pages and preserve earlier versions for listing or retrieval. Sources: superset:pages-chk2-nov07.
Screenshots [partial] browser screenshot saves a PNG; Design Mode includes a cropped element screenshot. Persistent task-linked screenshot evidence was not tested. Sources: superset:browser-chk2-nov07.
Recordings [unknown] recordings: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Previews [partial] Browser panes preview detected ports; remote forwarding requires the workspace selected. Workspace PR status can expose a deployment Open Preview link. Sources: superset:browser-chk2-nov07, superset:workspaces-chk2-nov07.
Test outputs [unknown] test outputs: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Reviewer outputs [unknown] reviewer outputs: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Gallery [partial] Pages provides a workspace list, pinned pages and All pages, with version retrieval. A general gallery spanning screenshots, recordings, tests and child-review findings was not established. Sources: superset:pages-chk2-nov07.
Revision links [partial] Page versions can be listed and retrieved, and shared links can select a version. Page-to-code-commit binding was not established. Sources: superset:pages-chk2-nov07.
Persistence [partial] Pages retain earlier publishes under the same page identity; archived workspace history can restore committed work if its branch remains available. No completed-session artifact retrieval test was run. Sources: superset:pages-chk2-nov07, superset:workspaces-chk2-nov07.
Child findings [unknown] child findings: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Prompt leakage [unknown] prompt leakage: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Built-in diff and Pull Requests views stage, commit, push, create PRs and merge (squash, merge commit or rebase and merge) through the user's GitHub connection; merging shipped per the Aug 23 2026 changelog. Local rebase and conflict handling are not documented.
Scope
Surfaces: Paradev desktop · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Conflict handling not documented; rebase only as a PR merge method.
Requires gh/GitHub.
Roadmap read 2026-11-07 lists "In-app PR merge" and "Native PR reviews" under Recently Shipped, both Aug 2026. Answers rely on the cited docs and do not extend to undocumented review features.
9 atomic answers
Branches [supported] One branch per workspace, created from main, existing branch or PR. Sources: superset:d-workspaces-nov07.
PRs can be merged (squash, merge commit, rebase and merge) from Superset on the real PR through the user's GitHub connection; merge shipped per the Aug 23 2026 changelog. Approval action, release and deploy authority were not found.
Scope
Surfaces: Paradev desktop · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Approvals, release and deploy flows undocumented.
Roadmap read 2026-11-07 lists "In-app PR merge" under Recently Shipped, Aug 2026. The PR page shows review status and filters (Approved, Changes requested) but documents no approve action.
6 atomic answers
Approve [unknown] Approve: no approve action is documented; the Pull Requests page only displays review status and filters for Approved and Changes requested. Searched docs, changelog and roadmap.
Release [unknown] Release: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Deploy [unknown] Deploy: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Exact revision [unknown] Exact revision: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Authority enforcement [supported] Merging, closing and commenting act on the real PR through the user's GitHub connection, with the same permissions and effects as doing it on github.com (pull-requests docs, read 2026-11-07). Sources: superset:d-prs-nov07.
PR-based workspaces show pull request state in the sidebar, and an Open Preview button appears when the branch has a deployment preview (workspaces docs, PR Status). PR links and CI check status appear in the PR view, with each check linked to its GitHub run. Rollback and revert were not found.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No retained completion record or rollback documented.
9 atomic answers
Commit links [partial] PR activity includes commits together with review/comment threads. An immutable task-to-delivery receipt is not established. Sources: superset:gap07-pr-review.
Pr links [partial] PR review state and check status appear in the changes sidebar; the PR Checks section lists every CI check with its status and a link to the run on GitHub. Sources: superset:d-diff, superset:d-prs.
Build links [partial] PR Summary lists CI check states with links to their GitHub runs; this does not establish links to deployed production builds. Sources: superset:gap07-pr-review.
Deployment links [partial] An Open Preview button appears when the branch has a deployment preview (workspaces docs, PR Status). The preview target itself was not inspected. Sources: superset:workspaces-open-preview.
Delivery status [unknown] Delivery status: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Retained evidence [unknown] Retained evidence: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Rollback [unknown] Rollback: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Revert [unknown] Revert: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Stale approval invalidation [unknown] Stale approval invalidation: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
The Pull Requests view lists PRs with check counts, and attention-based board columns (Needs attention, Needs review) group workspaces for review; batch review, risk filters and exact-revision approval were not found.
Scope
Surfaces: Paradev desktop · Version: desktop-v2.0.5; current first-party documentation retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Summaries [partial] PR Summary shows authored description,checks and reviews; no automatic batch change summary test was run. Sources: superset:gap07-pr-review.
Grouping [partial] Board columns follow workspace state derived from agent status and PR state (workspaces page); the Filter menu includes Device. Sources: superset:d-workspaces.
Risk size filters [partial] PR list shows added/deleted line counts and filters review status/repository/author; a dedicated risk/size filtering control is not established. Sources: superset:gap07-pr-review.
Findings [unknown] Findings: not established in current Paradev pull-requests, diff-viewer, workspaces and Pages docs reread 2026-11-07; no installed-client scenario was run.
Artifacts [partial] PR pane displays up to three workspace Pages and links to all. This does not establish all reviewer outputs as structured artifacts. Sources: superset:gap07-pr-review, superset:gap07-page-versions.
Request changes [partial] Per-line feedback can be routed to an agent in the linked/new PR workspace. Multi-task batching and exact-revision approval were not tested. Sources: superset:gap07-pr-review.
Exact revision approval [unknown] Exact revision approval: not established in current Paradev pull-requests, diff-viewer, workspaces and Pages docs reread 2026-11-07; no installed-client scenario was run.
Dependency queues [unknown] Dependency queues: not established in current Paradev pull-requests, diff-viewer, workspaces and Pages docs reread 2026-11-07; no installed-client scenario was run.
Next actions [partial] Start Workspace, Merge and close/reopen PR actions are shown in PR detail; review filters retain their state between visits. Sources: superset:gap07-pr-review.
Stale approval invalidation [unknown] Stale approval invalidation: not established in current Paradev pull-requests, diff-viewer, workspaces and Pages docs reread 2026-11-07; no installed-client scenario was run.
Check deduplication [unknown] Check deduplication: not established in current Paradev pull-requests, diff-viewer, workspaces and Pages docs reread 2026-11-07; no installed-client scenario was run.
Current desktop-v2.0.5 root repository code is MIT-licensed. This does not establish hosted-service parity or licenses for every component. At desktop-v2.0.11 the server apps (apps/api, apps/relay, apps/realtime) sit in the same MIT repository with no separate license.
Scope
Surfaces: Pinned default-branch source · Version: desktop-v2.0.5 at 624219c3c6a5428aec38b5f13f040cc0fc087010; server_license at desktop-v2.0.11 23c193a326a9be449f35bf3a97372cd1c2175e50 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
source-only
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
6 atomic answers
Client license [supported] Root LICENSE.md is MIT at pinned desktop-v2.0.5 commit. Sources: superset:mit-license-nov07.
Server license [supported] MIT: apps/api, apps/relay and apps/realtime are in the root-MIT repository at desktop-v2.0.11 with no separate license file. Whether the hosted service runs this code unchanged is a separate, unestablished question. Sources: superset:b06-license-tree.
Hosted extensions [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Source visibility [supported] Public repository at ParadevAI/Paradev; former superset-sh/superset redirects there. Sources: superset:releases-nov07.
Source revision [supported] 624219c3c6a5428aec38b5f13f040cc0fc087010 for desktop-v2.0.5. Sources: superset:mit-license-nov07.
Hosted parity [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
The MIT local core can import a repository, run agents and review diffs signed out and offline on the user machine, as explicitly documented in the shipped roadmap. Self-hosting every account/sync/relay/Pages/Cloud service remains unestablished.
Scope
Surfaces: Pinned default-branch source, Paradev desktop, User-provided remote host via relay · Version: Targeted first-party source check 2026-11-13. New implementation findings are pinned to 624219c3c6a5428aec38b5f13f040cc0fc087010. Unchanged atomic answers retain the individual source dates and revisions in their cited evidence. · Plan: Not specified · OS: macOS, Linux (experimental) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
8 atomic answers
Self hosting [partial] The complete local-core loop runs signed out/offline on user hardware. Hosted-service deployment parity is not established. Sources: superset:gaps41-local-core, superset:readme-chk2-nov07.
Vendor dependencies [partial] Local CLI works without relay connectivity. Remote/mobile access to user hosts uses Paradev relay and authenticated host grants; Pages publishing uploads content and managed Cloud is vendor hosted. Sources: superset:faq-chk2-nov07, superset:remote-chk2-nov07, superset:pages-chk2-nov07.
Export [partial] Published Page versions can be retrieved with pages pull, and local code remains ordinary git files. A full task/session-history export/import contract is not established. Sources: superset:gap07-page-versions.
Import [partial] Existing Git worktrees can be imported while keeping paths, branches and uncommitted changes. This does not establish import of tasks, complete context or full history. Sources: superset:workspaces-chk2-nov07, superset:migrate-conductor-chk1.
Formats [partial] Code remains in ordinary Git worktrees. Pages can be pulled as earlier HTML versions; a standard task/context/history interchange format was not established. Sources: superset:workspaces-chk2-nov07, superset:pages-chk2-nov07.
Cancellation [supported] Downgrades and cancellations take effect at the end of the current billing period; upgrades apply immediately. Account deletion is a separate support request. Sources: superset:pricing-chk2-nov07, superset:faq-chk2-nov07.
Account independence [partial] The roadmap shipped list says the local core loop can import a repo, run an agent and review diffs signed out and offline. Remote relay uses an authenticated organization and Pages/Cloud remain vendor services. No account-free client fixture was run. Sources: superset:roadmap-local-chk2-nov07, superset:remote-chk2-nov07.
History portability [unknown] history portability: Not established in the November 7 pass over current Paradev documentation, pricing, roadmap, changelog, public issues and stable-release source. No installed-client scenario was run.
Paradev discloses desktop analytics. In desktop-v2.0.5 the telemetry settings procedures are no-ops and desktop analytics uses a true compile-time default, so there is no effective desktop-user opt-out. SUPERSET_TELEMETRY=0 controls SDK method-call events only.
Scope
Surfaces: Paradev desktop, Pinned default-branch source · Version: Targeted first-party source check 2026-11-13. New implementation findings are pinned to 624219c3c6a5428aec38b5f13f040cc0fc087010. Unchanged atomic answers retain the individual source dates and revisions in their cited evidence. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
This source pass establishes only the named atomic answers. Other parts retain their documented source gaps; no hands-on test was performed.
15 atomic answers
Code data [partial] Local workspaces keep repos, worktrees and agent sessions on the user's machine by default. The privacy policy says messages, tasks and attachments sent to AI agents through Paradev apps are stored by Paradev and synced across devices. Remote Access routes terminals, agent runs, diffs and forwarded ports through the Paradev relay, and cloud workspaces run code in the cloud. Sources: superset:home-security-chk1, superset:privacy, superset:d-faq, superset:remote.
Prompts [partial] Prompts to terminal agents go to the configured model provider; messages, tasks and attachments sent to AI agents through Paradev apps are stored by Paradev for delivery and cross-device sync. Sources: superset:d-faq, superset:privacy.
Logs [unknown] Logs: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Artifacts [partial] Pages are shared with the organization by default or by public link (pages docs). Upload handling for published content is not stated in the privacy policy. Sources: superset:d-pages, superset:privacy.
Retention [partial] Data kept as long as needed; no period stated. Sources: superset:privacy.
Training [partial] Google user data is not used for generalized model training; policy silent on other content. Sources: superset:privacy.
Residency [partial] Cloud environment region is chosen at creation and fixed for saved snapshots; BYOC repo and sign-in state live in the user server. This does not establish all metadata/subprocessor residency. Sources: superset:gap07-cloud-lifecycle, superset:gap07-byoc.
Subprocessors [partial] Policy refers to a subprocessors page and names PostHog and Apple. Sources: superset:privacy.
Telemetry disclosure [supported] Usage data processed by PostHog and linked to account identifiers. Sources: superset:privacy.
Telemetry defaults [partial] Desktop analytics events are sent only for a signed-in user (track() returns when no user ID is set) and only when a PostHog key is configured. DEFAULT_TELEMETRY_ENABLED is true at the pinned commit (constants line 67). Sources: superset:src-telemetry, superset:src-constants, superset:src-analytics-track.
Telemetry controls [partial] The SDK has an environment switch, but the desktop getTelemetryEnabled always returns true and setTelemetryEnabled changes no state. Desktop analytics uses the true default. Sources: superset:gaps41-telemetry, superset:gap07-sdk.
Consent prompt [unknown] Consent prompt: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Provider separation [supported] Superset never proxies model calls; the provider bills directly. Sources: superset:d-faq, superset:home.
Per-seat Pro $20 monthly/$192 yearly; Team $60/$648 yearly; Ultra $200 monthly. Team/Ultra include pooled Cloud GB-hours with $0.06/GB-hour extra usage. Model accounts are separate. Workspaces and projects are unlimited on every plan; cloud compute is metered per GB-hour instead.
Scope
Surfaces: Paradev desktop, User-provided remote host via relay, Paradev managed Cloud workspaces · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
12 atomic answers
Currency [partial] Dollar-denominated public offer; no exchange/tax assumptions. Sources: superset:pricing-nov07.
Seat minimum [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Workspace fees [supported] No per-workspace or per-project fee: the comparison lists Workspaces and Projects as Unlimited on Free, Pro, Team, Ultra and Enterprise. Cloud workspace use is metered by GB-hour. Sources: superset:b06-pricing.
Included usage [supported] Team 1,200 GB-hours/seat/month; Ultra 4,000. Standard 8GB workspace equivalents 150/500 hours. Sources: superset:pricing-nov07.
Credits [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Trial [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Overages [supported] $0.06/GB-hour for extra/over-pool use; purchased GB-hours do not expire. Sources: superset:pricing-nov07.
Taxes [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Model cost [supported] Bring own agent subscription/API keys; no model resale. Sources: superset:pricing-nov07.
Fixed local/Pro examples: one Free user $0; two Pro users $40/month or $384/year; five $100/month or $960/year. Managed Cloud requires Team/Ultra and separate usage accounting.
Scope
Surfaces: Paradev desktop, User-provided remote host via relay, Paradev managed Cloud workspaces · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
Superset became Paradev on October 26, 2026; the latest stable GitHub release is desktop-v2.0.8 (Nov 10, 2026). Desktop macOS and experimental Linux; mobile Pro+ and managed Cloud Team/Ultra have separate requirements. The legacy v1 MCP server is removed (410 Gone); agent transcripts read out as JSON from the CLI.
Scope
Surfaces: Paradev desktop, Paradev CLI and host server, Paradev iPhone app · Version: Paradev desktop-v2.0.8 (GitHub releases and changelog source retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
SLA numbers unpublished; status history not read. Export is per-terminal transcript and theme JSON; no account-wide export or product end-of-life policy was found.
8 atomic answers
Release stage [partial] desktop-v2.0.5, published November 5, is marked Latest and is not a prerelease; cli-v2.0.5 is listed separately as a prerelease. The current CLI reference has no beta label; Linux is experimental. Sources: superset:releases-nov07, superset:d-cli-nov07, superset:d-install-20261107.
Status history [unknown] Status history: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Export options [partial] superset agents read returns an agent's saved transcript as JSON per terminal, theme definitions export as JSON, and local workspace files stay in the user's git worktrees. No account-wide or cloud-workspace data export was found in the inspected docs and source. Sources: superset:b134-doc-cli-agents-read, superset:d-faq-nov07.
Paradev states it completed a SOC 2 Type II audit (Aug 27, 2026 changelog entry) and lists the SOC 2 Type II report under Enterprise; the report is requested through its trust center. Scope, period and the report itself were not inspected.
Scope
Surfaces: Paradev desktop · Version: Paradev desktop-v2.0.5; changelog and pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
Not separately cross-checked
Report scope, auditor and period unknown; trust center unreadable.
Vendor-stated organization-level control; not tied to one product surface.
9 atomic answers
Iso scope [unknown] Iso scope: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. trust.superset.sh returned only a page title.
Iso issuer [unknown] Iso issuer: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. trust.superset.sh returned only a page title.
Iso validity [unknown] Iso validity: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. trust.superset.sh returned only a page title.
Soc2 scope [unknown] Soc2 scope: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. trust.superset.sh returned only a page title.
Soc2 period [unknown] Soc2 period: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. trust.superset.sh returned only a page title.
Report access [partial] Report listed as an Enterprise feature; the changelog says it is requested through the trust center at trust.paradev.com. Sources: superset:pricing, superset:changelog-soc2-chk1.
Verification date [unknown] Verification date: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question. trust.superset.sh returned only a page title.
Evidence status [partial] Report not inspected. Sources: superset:pricing.
Trial [unknown] Trial: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Credits trial [unknown] Credits trial: not established. Searched docs.superset.sh pages (overview, install, workspaces, tasks, remote access, automations, usage, MCP, CLI, SDK, FAQ, troubleshooting, skills), superset.sh home, pricing, roadmap, changelog and GitHub source at fc44d32 for this question.
Self host cost [partial] The MIT License permits self-hosting; no hosting fee is stated. This covers the repository code, not managed Cloud. Sources: superset:src-readme-v205.
Paid only [supported] Pro includes remote/mobile/automations/integrations; Cloud starts at Team/Ultra. Sources: superset:pricing-nov07.
Seat prices, pooled Cloud GB-hours and $0.06/GB-hour extras are public. Enterprise is custom annual; cancellation applies at period end. Enterprise is annual billing only; Pro and Team bill monthly or yearly and Ultra monthly, with no published seat minimum.
Scope
Surfaces: Paradev desktop, Paradev managed Cloud workspaces · Version: Paradev desktop-v2.0.5; current docs/pricing reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
No workload, billing or authenticated client test was performed; unestablished details remain unknown.
Compute markup [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Model markup [supported] User-supplied provider subscriptions/keys, no model resale. Sources: superset:pricing-nov07.
Minimum commitment [partial] Enterprise is annual billing only; Pro and Team can bill monthly and Ultra bills monthly. The pricing page states no seat or spend minimum; Enterprise contract minimums are sales-only. Sources: superset:b06-pricing.
Cancellation [supported] Upgrades immediate/prorated difference; downgrade/cancel at billing period end. Sources: superset:pricing-nov07.
Sales only unknowns [partial] Enterprise custom annual pricing and allowance. Sources: superset:pricing-nov07.
Transparency classification [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
Current Paradev homepage is the former Superset site. Desktop macOS and experimental Linux; iPhone/iPad, CLI/SDK/MCP; Windows/Android not available. Local and cloud workspaces are separate. Root license now links MIT; hosted parity not inferred.
Kind
vendor-claimed
Locator
Hero; FAQ; Supported agents; Download; Source available
Re-read 2026-10-09. superset start --daemon registers the machine with the relay. Desktop toggle "Allow remote access to this device via relay"; default state not stated. Only the starting user has access until members are added in Settings, Hosts (Add member); owners can promote or remove members. Terminals, agent runs and the diff viewer are proxied through the relay. iPhone or iPad needs the computer awake, online and running Superset. Turning access off restarts the host service and interrupts in-flight terminals. Port forwarding needs a host on host-service 1.26 or newer; TCP only. Owner-offline behaviour, co-prompting and concurrency not described.
Kind
documented
Locator
Hosts and the relay; Security; Who can access; Ports; Turning access off
Re-read 2026-10-09. Lifecycle hooks in each agent config report started, finished and waiting for input; hooks exist only for agents launched through Superset (Settings, Agents toggle removes them). Notifications: sounds and a macOS dock badge for workspaces that need attention. Inline prompts: agents can pause to ask questions, request tool approval or ask for plan review in the chat pane, and the workspace is flagged as needing attention. Running and PR state persist across restarts; Clear Status resets a stale running indicator. Each sidebar workspace shows an activity strip. Waiting-for-input signal varies by agent; some agents trigger completion notifications only. No mobile or push notification described.
Kind
documented
Locator
Status states; How status is detected; Notifications
Re-read 2026-10-09. CLI is in Beta; commands and flags still evolving. Top-level groups: scripts, auth, start, stop, status, update, organization, projects, hosts, workspaces (archive is current; delete is an alias), agents, terminals, browser, pages, tasks, automations, settings, completion, schema, config. Cloud workspace archive stops the sandbox within a minute and deletes it after 7 days; sleep stops the sandbox and ends its terminals and agents. hosts list, set-wake and wake. Global --api-key and SUPERSET_API_KEY. agents read returns the saved agent transcript. No platform list and no dates.
Re-read 2026-10-09. iPhone and iPad app on the App Store, requiring iOS 26 or iPadOS 26 or later and Superset Pro. Push notifications are coming. Android not available yet. No supported web dashboard. Windows is planned with no date; Linux x64 AppImage experimental and untested; CLI supports Linux x64 and arm64. Local workspace files live on the host; agents send prompts and context to configured providers; remote access via relay is off by default; Superset never proxies model calls. Worktrees are not sandboxes: agents share processes, network and files outside the worktree. Terminals survive restarts through a background daemon. Every project must be a git repository; GitHub is fully supported through gh; repos with other remotes work locally; cross-machine project identity is tied to GitHub. Account deletion is not self-serve; email support. Pro features live in the v2 interface. Telemetry and licence not covered; no pricing or free-tier wording. Change from the Oct 8 record: iPad now described as on the App Store, not coming.
Kind
documented
Locator
Data Handling; Platforms; Isolation; Offline Behavior
October 25 explicitly announces Superset is now Paradev with existing accounts/workspaces/settings/superset CLI carried over. Plugins on for everyone; November 1 improves panes/workspaces. Released automation event triggers and ticket workflows now appear in current docs/roadmap.
Re-read 2026-10-09. Standalone installer auto-detects macOS (Apple Silicon or Intel) and Linux (x64 or arm64) and installs under the home directory. The intro labels the CLI Beta. The Homebrew command is listed separately.
macOS Apple Silicon or Intel; Linux x64 AppImage experimental; Windows not yet available. iPhone and iPad need iOS or iPadOS 26 or later and Paradev Pro. Android is not available; waitlist. The page carries no early-access label for cloud workspaces.
Lists 22 built-in terminal agents, including Claude Code, Codex, OpenCode and Gemini CLI. Settings > Agents > Add agent > Custom agent adds a CLI command, prompt transport and resume/fork args. Multiple workspaces can run agents in parallel. Launch model and effort controls depend on the agent.
Agent CLIs run with user subscriptions or API keys; Paradev does not proxy model calls. Status, resume, usage and quota integration vary by harness. Custom agents receive a workspace, worktree and terminal without built-in integrations. Claude/Codex native subagents appear under the parent; cross-agent handoff can carry their structured transcript.
Kind
documented
Locator
Feature Support; Subagents and Handoff; Other Agents
Provider environment-variable instructions apply to Claude Code in a terminal; other agents such as Codex read their own settings. Named routes are Vercel AI Gateway, OpenRouter, Bedrock, Vertex, Foundry and Anthropic-compatible gateways. The documented chat API-key flow uses Anthropic; this is not a universal provider matrix for every harness.
Chat runs the installed CLI through Agent Client Protocol with the same login, settings and MCP servers. CLI/Chat switching resumes the same session. Chat is documented for Claude Code >=2.1.226, Codex >=0.160.0, OpenCode >=1.15.5 and Pi; other agents use terminals.
Resume uses native session IDs and configured resume args after unexpected terminal death. Fork copies the conversation, not files, within the same workspace. Cross-agent handoff seeds a fresh session with up to 36,000 context characters; Claude/Codex saved conversations are preferred, otherwise terminal output. Output is not redacted. agents read retrieves Claude/Codex saved transcripts only.
Kind
documented
Locator
Resume Interrupted Sessions; Fork; Continue with another agent; Read an Agent transcript
Sidebar activity strips show running agents and ports; running/PR state persists across restarts. Hooks and command wrappers report started, finished and waiting states only for agents launched through Paradev. Waiting-state support varies; inline prompts mark workspaces needing attention.
Kind
documented
Locator
The Activity Strip; How Status Is Detected; Notifications
The bundled superset:orchestrate skill makes Claude Code or Codex coordinate mixed-agent workers. The coordinator creates one branch/workspace per worker, launches bounded prompts, reads/sends terminal messages and verifies structured done/blocked reports before integration. Each worker produces a branch and PR. Natural-language examples are documentation, not observed runs.
November 1 describes saved workspace views, status/host/project filters and list/board grouping. It still labels chat experimental under Settings > Experimental > Chat. September 6 documents image before/after diffs and video/PDF previews behind a Preview button. Read through the current November 1 entry; older dated entries are historical.
Kind
documented
Locator
November 1, 2026 > A New Workspaces List; Experimental chat; September 6 > Image, Video, and PDF Diffs
Latest stable resolves to desktop-v2.0.5, November 5, 2026, at 624219c3c6a5428aec38b5f13f040cc0fc087010. Changes include MIT relicensing and importing worktrees from other tools. Live docs can change independently of this release.
The shipped built-in agent registry explicitly names Antigravity and launches its agy CLI. Its setup package installs corresponding lifecycle hooks. Other unlisted agents can be configured through the generic custom-agent facility.
Kind
source-inspected
Locator
builtin-terminal-agents.ts Antigravity entry; packages/agent-setup/src/agent-wrappers-agy.ts; official agent-integration Supported Agents
Free $0 one local user, no card. Pro $20/month or $16 annual-equivalent ($192/year); Team $60 or $54 annual ($648/year); Ultra $200 monthly. Per active seat. Cloud Team 1,200 GB-hours/seat/month, Ultra 4,000; $0.06/GB-hour overage/top-up. Enterprise custom annual; cancellation period-end. User model accounts required.
Re-read 2026-10-09. macOS Apple Silicon and Intel; Linux x64 AppImage experimental; Windows not yet available. Git required; gh CLI optional but needed for PR workflows and offered during onboarding. Onboarding checks prerequisites live: the checklist updates when git, gh or agents are installed or signed in. At least one coding agent needed. iPhone and iPad app: iOS 26 or iPadOS 26 or later and Superset Pro; enable Remote Access to reach agents on your computer; cloud workspaces in early access. Android not available yet; join the waitlist. No dates.
Kind
documented
Locator
Platform and versions; Requirements; First launch; iPhone
Usage estimates API-equivalent cost from local session logs across named agents, with model/workspace/session drilldown. Provider quota meters refresh every five minutes. Remote hosts not aggregated. Machine resources every two seconds; not subscription invoices.
Kind
documented
Locator
Subscription allowance; Per-agent breakdown; Estimates vs billed; Machine resources
Re-read 2026-10-09. Any CLI agent said to work. Named gateways: Vercel AI Gateway, OpenRouter, AWS Bedrock, Google Vertex AI, Microsoft Foundry; Anthropic-compatible endpoints such as LiteLLM. Variables include ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN and ANTHROPIC_BASE_URL. No local-model or Ollama mention. The only stated requirement is an Anthropic-compatible API for custom endpoints; the page recommends pinning model versions. No dates.
Local projects use git worktrees; Cloud uses separate clones and is available on Team/Ultra. Sessions use scratch git folders under ~/.paradev/sessions without a project. Board statuses and archived history documented.
Kind
documented
Locator
Creation and Branches; Status Indicators; Archiving; Deleting
Re-read 2026-10-09. superset start --daemon spawns a background daemon, writes a manifest and binds only to loopback; automatic updates off by default. The systemd example runs superset start without --daemon, requires KillMode=process and a CLI newer than 1.30.2. A headless machine uses the standalone installer; the desktop app starts the host itself. The first machine runs projects create and others run projects setup; projects are host-owned. Wake behaviour not described on this page.
Kind
documented
Locator
Daemon basics; Headless and VPS setup; Systemd; Upgrades
Re-read 2026-10-09. Cmd+N creates an isolated git worktree on its own branch. Prompt-first flow: describe the task, pick an agent and create; the agent starts immediately. A project can be added from a local folder or a cloned remote. No dates or versions.
Kind
documented
Locator
Creating a workspace; Racing agents; Shipping the winner
Team/Ultra managed cloud uses GitHub and agent sign-in, 1-20 repos/environment. Small/Medium/Large 2/4/8 vCPU and 4/8/16GB; 64GB disk. GB-hour metering; running workspace stops about ten minutes after quota limit. Idle stop around one hour, files kept 30 days; archive deletion after seven days. Credentials proxied, not copied to sandbox.
Kind
documented
Locator
Requirements; Machine Sizes; Usage and Billing; Lifecycle; Credentials
Current roadmap marks automations/event triggers, ticket intake and iOS as shipped in October. MCP manager, shared team features and broader plugin marketplace remain undated future items. Some roadmap Cloud/SDK labels lag live docs; current scoped docs take precedence.
Current docs describe mixed schedules and provider-event triggers, up to 25 triggers. Pro/Enterprise-labelled automation entitlement in docs; paid higher plans inherit Pro. Delivery at least once; created means workspace creation, not task success. Offline host failures and retries documented.
Kind
documented
Locator
Schedules; Device selection; Retries; Offline machines; Plan requirement
Re-read 2026-10-09. HTTP endpoint api.superset.sh/mcp with 40 tools across nine groups: tasks 6 (tasks_list, tasks_get, tasks_create, tasks_update, tasks_delete, tasks_statuses_list), workspaces 4, agents 2, terminals 5, pages 9, automations 11 (including automations_logs), projects 1, hosts 1, organization members 1. OAuth 2.1 default, scoped to the active organization; sk_live API keys for headless use grant full organization access. No stability label; versioned URL kept; v1 path returns 410 Gone. No dates. Re-read 2026-10-09 (final review): Chat Integration documents the /mcp slash command in the built-in chat, listing configured MCP servers with names, transport (local or remote) and state (enabled, disabled or invalid), read from .mastracode/mcp.json, .amp/settings.json or .mcp.json.
Kind
documented
Locator
Endpoint and transport; Authentication; Tools (40 total)
Re-read 2026-10-09. SDK is in early alpha, "not meant for production use and may be removed in the future." Package @superset_sh/sdk for Node, Bun and Deno; browser bundles should not ship API keys. Resource groups: tasks, workspaces, projects, automations, hosts. Options: apiKey, organizationId, timeout (60 seconds default), maxRetries (2 default), logLevel. Client example shows baseURL and relayURL as optional.
Current changelog/roadmap and automation docs describe shipped schedule and provider-event triggers; previous exploring/experimental-only claim is superseded. No hands-on event test.
Kind
vendor-claimed
Locator
August 23, 2026 section: "Experimental: event triggers for automations"; October 4, 2026 section: event-trigger account choice in the automation editor
Current HTTP MCP server documents tasks/workspaces/agents/terminals/pages/automations/hosts/projects tools and OAuth. Avoiding an exact tool count prevents a stale inventory from being treated as a contract. Legacy v1 returns410.
Current CLI reference does not label CLI Beta. Uses same backend as desktop, OAuth or API key; task tracker can be native or Linear. Commands target local/remote/cloud; tasks support create/update/assignee,status,JSON and tracker override.
Slack @superset creates/updates/searches tasks and starts Cloud workspaces; OAuth setup and connected Linear/GitHub plugins have restricted tools, without delete/merge/bulk writes.
Kind
documented
Locator
Triggering agents; Permissions and limits; Where agents run
Re-read 2026-10-09. Desktop app provisions skills at launch and keeps them updated. Direct install: npx skills add superset-sh/skills. Claude Code route: /plugin marketplace add superset-sh/superset. Managed copies written to ~/.claude/skills/superset/, ~/.agents/skills/ and ~/.agents/commands/. Listed agents: Claude Code; Codex, Kimi, Vibe and Grok as other agents that read skills; in-app chat, invoked as /superset/feedback. Only the Superset marketplace is named; no community plugins or third-party marketplaces. No dates.
Re-read 2026-10-09: "use the /mcp slash command to see your workspace's configured MCP servers"; the list gives "their names, transport type (local/remote), and current state (enabled/disabled/invalid)"; it reads from .mastracode/mcp.json, .amp/settings.json or .mcp.json.
Plugins supply MCP tools and skills. Claude Code/Codex support both; Kimi/Vibe/Grok skills only; other agents unsupported in this matrix. Credentials stay at Paradev proxy; OAuth tokens not written into local configs. User-owned entries win; managed entries cleaned on uninstall.
Users create plugin manifests pointing to existing Streamable HTTP MCP servers, with optional skills/scripts and connector binding. Paradev proxies credentials, no OAuth settings in manifest; it does not bundle the tool server.
Owners/admins add GitHub plugin repositories. Owner/admin/member plugin access states unavailable/available/installed; unavailable immediately blocks tool use and removes installations on next sync. Sync is manual, changed same-version content refused, last good version survives failure.
At app launch managed skills are provisioned in standard Claude/agents discovery paths, refreshed and removed when no longer shipped; user-authored files at the same path are preserved. Orchestrate and setup skills are available.
Desktop app uses Electron 41.10.7 at the pinned default-branch commit (package version 1.36.0; latest GitHub release is desktop-v1.37.0, so source is not guaranteed to equal the released binary).
Mobile app in apps/mobile is an Expo / React Native project (expo-router entry, @expo/ui dependency, ios and android run scripts) at the pinned commit; the shipped App Store binary was not inspected.
Re-read 2026-10-09. New task modal: title, description, status, priority, assignee. Views: sortable table or kanban board grouped by status. Semantic search ("find tasks by meaning"). Run in workspace: pick a project and agent, one workspace per task, with an Auto-run command toggle. Linear source lists issues from the whole connected workspace ("synced from your connected workspace"; no direction stated); filters for project, status and assignee. GitHub issues source with repository filter and Add to workspace. Task projects not covered. Creating tasks from Slack or MCP not stated on this page.
Kind
documented
Locator
Sources; Views; Creating and editing; Task to workspace
Re-read 2026-10-09 at pinned commit fc44d32, packages/trpc/src/router/task/task.ts (blob unchanged on main). createTask builds a task in a database transaction and anchors description attachments; the router exposes byId, bySlug and byIdOrSlug lookups, update, and soft delete. importLinearIssue sits outside lines 253 to 348 and reads a Linear issue into a local task; the file contains no Linear write-back and no PR merge logic.
Linear custom tool launches a local workspace with two CLI calls. Separate Linear plugin grants tools to read/update issues. This page does not prove bidirectional native tracker sync.
Re-read 2026-10-09 at pinned commit fc44d32, packages/db/src/schema/schema.ts (blob unchanged on main). Task slugs are "<key>-<number>" with one counter per team; organization-unique slug constraint. Tasks table includes branch and prUrl fields. Task projects table includes state (default planned), leadUserId, startDate and targetDate.
Re-read 2026-10-09: "When the organization tracks tasks in Linear (an owner's setting), these commands work on its Linear issues through your own Linear connection; otherwise on Superset tasks." "A command works on one tracker only." "Pass --tracker superset|linear to reach the other one for a single command." tasks delete: "Linear issues are archived."
Kind
documented
Locator
Tasks section (tracker selection and --tracker flag)
Re-read 2026-10-09. New task modal: title, description, status, priority, assignee. Views: sortable table or kanban board grouped by status. Semantic search ("find tasks by meaning"). Run in workspace: pick a project and agent, one workspace per task, with an Auto-run command toggle. Linear source lists issues from the whole connected workspace ("synced from your connected workspace"; no direction stated); filters for project, status and assignee. GitHub issues source with repository filter and Add to workspace. Task projects not covered. Creating tasks from Slack or MCP not stated on this page.
Kind
documented
Locator
Sources; Views; Creating and editing; Task to workspace
Re-read 2026-10-09 at pinned commit fc44d32, packages/db/src/schema/schema.ts (blob unchanged on main). Task slugs are "<key>-<number>" with one counter per team; organization-unique slug constraint. Tasks table includes branch and prUrl fields. Task projects table includes state (default planned), leadUserId, startDate and targetDate.
Re-read 2026-10-09. Resume uses an id-based resume command set in Resume Args; failed resumes show "Failed to resume" with Retry. Sessions whose terminal died unexpectedly auto-resume; sessions closed on purpose or agents that exited cleanly stay stopped. Handoff to another agent seeds it with the last 36,000 characters of terminal context as read-only history and warns that output is not redacted. Fork starts a native copy in the same agent with the same conversation; forks copy conversation, not files. Pausing for questions, tool approval or plan review not covered on this page.
Re-read 2026-10-09. Desktop app provisions skills at launch and keeps them updated. Direct install: npx skills add superset-sh/skills. Claude Code route: /plugin marketplace add superset-sh/superset. Managed copies written to ~/.claude/skills/superset/, ~/.agents/skills/ and ~/.agents/commands/. Listed agents: Claude Code; Codex, Kimi, Vibe and Grok as other agents that read skills; in-app chat, invoked as /superset/feedback. Only the Superset marketplace is named; no community plugins or third-party marketplaces. No dates.
Re-read 2026-10-09. The @superset agent can create, update, search and triage tasks; search the web with citations; read thread or channel history; and spin up a cloud workspace to launch a coding agent. Code-change requests default to a workspace and agent. Rich previews unfurl Superset tasks, workspaces and Pages. Limited tool set: plugin tools cannot delete resources, merge pull requests or perform bulk writes. Uses a linked user's connected Linear and GitHub plugins; a Connect button appears when one is missing. Pro requirement not stated on this page. No dates.
Kind
documented
Locator
Triggering agents; Permissions and limits; Where agents run
Re-read 2026-10-09. Design mode arms an element picker; the agent receives the element DOM, computed styles, React component metadata and a cropped screenshot, plus a note, and can go to an existing terminal or a new session. In-app browser pane for previewing running services, with back, forward, reload, address bar, DevTools pane and detected-port links. Agents can open, read, screenshot and interact with browser panes through superset browser CLI commands. For remote workspaces, detected ports are forwarded while that workspace is selected. No Open Preview button described. No dates.
Kind
documented
Locator
Previews; Design Mode; Screenshots and agent control
File search and a search bar across open workspaces are documented; editor detects concurrent disk edits and offers compare/reload/overwrite while retaining buffer. No automatic merge. Exact semantic code indexing remains unestablished.
Re-read 2026-10-09 at pinned commit fc44d32, packages/trpc/src/router/task/task.ts (blob unchanged on main). createTask builds a task in a database transaction and anchors description attachments; the router exposes byId, bySlug and byIdOrSlug lookups, update, and soft delete. importLinearIssue sits outside lines 253 to 348 and reads a Linear issue into a local task; the file contains no Linear write-back and no PR merge logic.
Re-read 2026-10-09. HTTP endpoint api.superset.sh/mcp with 40 tools across nine groups: tasks 6 (tasks_list, tasks_get, tasks_create, tasks_update, tasks_delete, tasks_statuses_list), workspaces 4, agents 2, terminals 5, pages 9, automations 11 (including automations_logs), projects 1, hosts 1, organization members 1. OAuth 2.1 default, scoped to the active organization; sk_live API keys for headless use grant full organization access. No stability label; versioned URL kept; v1 path returns 410 Gone. No dates. Re-read 2026-10-09 (final review): Chat Integration documents the /mcp slash command in the built-in chat, listing configured MCP servers with names, transport (local or remote) and state (enabled, disabled or invalid), read from .mastracode/mcp.json, .amp/settings.json or .mcp.json.
Kind
documented
Locator
Endpoint and transport; Authentication; Tools (40 total)
Re-read 2026-10-09 at pinned commit fc44d32, apps/desktop task record screen TaskRecordScreen.tsx (read through the GitHub API; main not compared). Uses label add and remove mutations and an addComment mutation that carries parentCommentId for threaded replies.
Kind
source-inspected
Locator
useTaskLabelMutations; TaskCommentComposer in TaskTimeline
Native task has editable title/description,status,priority,assignee and labels, alongside connected Linear issues. Run in workspace separately selects a project/agent and one workspace per task, with optional staged auto-run.
Tasks view offers list and status-grouped board views, filters for project, task state, assignee and label that persist, a label hierarchy from path-style names, semantic search and multi-select.
Kind
documented
Locator
What You Can Do: Filters; Label hierarchy; List and board views
Re-read 2026-10-09. CLI is in Beta; commands and flags still evolving. Top-level groups: scripts, auth, start, stop, status, update, organization, projects, hosts, workspaces (archive is current; delete is an alias), agents, terminals, browser, pages, tasks, automations, settings, completion, schema, config. Cloud workspace archive stops the sandbox within a minute and deletes it after 7 days; sleep stops the sandbox and ends its terminals and agents. hosts list, set-wake and wake. Global --api-key and SUPERSET_API_KEY. agents read returns the saved agent transcript. No platform list and no dates.
Re-read 2026-10-09: "When the organization tracks tasks in Linear (an owner's setting), these commands work on its Linear issues through your own Linear connection; otherwise on Superset tasks." "A command works on one tracker only." "Pass --tracker superset|linear to reach the other one for a single command." tasks delete: "Linear issues are archived."
Kind
documented
Locator
Tasks section (tracker selection and --tracker flag)
Local project tasks use separate Git worktrees and branches; cloud workspaces use separate clones and scratch sessions use managed folders. Board docs name Idle, Working, Needs attention, Needs review, Merged and Deleted. Workspace PR badges link pull requests and deployment previews; archived cards can restore committed work if the branch still exists. Existing worktrees can be imported without moving their paths.
Kind
documented
Locator
Core Concept; Create Workspaces; Import Worktrees; List and Board Views; PR Status; Restore a Workspace
The comparison table labels Workspaces and Projects unlimited. This is a plan allowance, not observed simultaneous-agent throughput. Free lists one user; paid tiers differ. Upgrades apply immediately; downgrades and cancellation apply at the current billing period end.
Re-read 2026-10-09. The page describes an existing Linear connection and gives no connection steps or per-member wording. Linking an issue in the New Workspace flow or opening a task in a workspace uses Linear's branch name and moves the issue to In Progress. --skip-branch-prefix keeps Linear's branch format so Linear autolinks the branch. A wrapper script runs superset workspaces create then open; re-running on the same issue reuses the existing workspace. Sync direction and the authoritative tracker not stated. Pro requirement not mentioned.
Desktop provisions and updates skills at launch; standalone installation uses paradevai/skills or paradevai/paradev marketplace. superset:orchestrate is an installed orchestration skill, selected from context or invoked explicitly. Managed locations include ~/.claude/skills/superset/, ~/.agents/skills/ and ~/.agents/commands/.
Kind
documented
Locator
Installation; What You Get; Using Skills; How They Are Delivered
CLI authenticates with browser OAuth or an API key and active organization. Workspace and agent creation accept --agent, --model and --effort overrides, subject to harness support. --from-terminal can seed a cross-agent session; terminal read/send monitor and communicate with workers.
Remote hosts authenticate and register with Paradev relay; headless API keys are documented. Organization members need explicit host grants. Relay proxies remote terminals/agents/diffs. Mobile access to a user host requires that host awake and online; managed cloud is separate.
Kind
documented
Locator
Overview; Option 2 CLI; Headless; Grant teammates access
Re-read 2026-10-09. Host must be awake, online and connected to the relay; enable the relay under Settings, Remote Access, or run superset start --daemon. Mobile app shows "One step left" for a host that never connected, "Offline" with a last-seen time for an unreachable host, and "Can't check" when status fails to load. A scheduled run on an offline device is recorded as failed; retry from the Automations list. Updater race fixed in recent releases; terminals are held by a background daemon, so quit fully and relaunch. No owner or teammate access statement.
Kind
documented
Locator
Failure modes; Terminal reconnect and daemon behavior
Each automation targets a device or Cloud. Run statuses: created, creating, missed (no device online to take the run; not retried) and failed. Limits: offline hosts miss the run; keep the device online. Legacy docs.superset.sh/automations redirects here.
Online means connected to the Paradev relay. Runs fail when the target device is not relay-connected at fire time; use Retry all once it is back. Cloud workspaces work without keeping your own computer connected.
A QStash-verified per-minute tick in the cloud API selects enabled schedule triggers whose next_run_at is due from the server database, skips plans without schedules, enqueues dispatch and advances next_run_at. The schedule is evaluated server-side, not on a desktop client.
Re-read 2026-10-09. Local project workspaces use isolated git worktrees at <worktrees path>/<project>/<branch>. Fresh-branch workspaces start from main; existing branch and review-PR options also exist. A session is a workspace without a project, stored under ~/.superset/sessions, with no branch or PR link. Organization owners and device owners can delete a project. Board columns follow workspace state derived from agent status and PR state: Idle, Working, Needs attention, Needs review, Merged, Deleted; Merged and Deleted are history cards. Cloud workspaces are in early access and not generally available; when available, a new working branch is created from the selected base. Filter menu includes Device.
Kind
documented
Locator
Creation and Branches; Status Indicators; Archiving; Deleting
Re-read 2026-10-09. Lists 22 supported agents: Claude Code, Amp, Codex, Gemini CLI, Mastracode, OpenCode, Pi, Oh My Pi, Copilot, Mistral Vibe, Kimi Code, Grok, Cursor Agent, Droid, Polygraph, Hermes, Muse Code, Devin, fx, Antigravity, Kiro and UFO. Settings, Agents customises built-in agents: command with and without prompt, prompt command suffix, task prompt template, resume args, fork args, model override. Adding entirely new adapters not documented. The page does not claim that any CLI agent works; the homepage says any CLI-based coding agent. Codex picker shows GPT-5.5 under "Retiring 2026-10-14."
Re-read 2026-10-09. Lifecycle hooks in each agent config report started, finished and waiting for input; hooks exist only for agents launched through Superset (Settings, Agents toggle removes them). Notifications: sounds and a macOS dock badge for workspaces that need attention. Inline prompts: agents can pause to ask questions, request tool approval or ask for plan review in the chat pane, and the workspace is flagged as needing attention. Running and PR state persist across restarts; Clear Status resets a stale running indicator. Each sidebar workspace shows an activity strip. Waiting-for-input signal varies by agent; some agents trigger completion notifications only. No mobile or push notification described.
Kind
documented
Locator
Status states; How status is detected; Notifications
Re-read 2026-10-09. Schedules stored as RFC 5545 RRules, with Hourly, Daily, Weekdays and Weekly presets and a Custom option; several cadences per automation through Add Trigger. Schedule triggers are the only trigger type described on this page. Run statuses: created (success), creating (handoff in flight), failed (device offline at fire time or handoff broke). Retry all appears when a latest run failed; Run now dispatches immediately. Delivery is at-least-once. A run records only workspace creation, not agent task success. Creating, running or resuming needs Pro or Enterprise. Overlapping-run handling not described.
Kind
documented
Locator
Schedules; Device selection; Retries; Offline machines; Plan requirement
Re-read 2026-10-09. Sessions survive app restarts: running processes continue, output history and scrollback preserved. If a terminal ends, New shell starts a fresh session in the same pane; recent output stays visible. Agent recovery is covered on a separate page. Host-run terminals, detached-agent behaviour and cloud or remote terminal persistence not described.
Re-read 2026-10-09. The superset:orchestrate skill lets one agent coordinate workers in separate workspaces through the Superset CLI. The coordinator creates workspaces, launches workers and monitors them with terminals read and send. The coordinator can be Claude Code or Codex; workers can be any mix of agents Superset runs. Workers finish with a structured completion or blocked message that the coordinator verifies. Each worker yields one branch and PR. Model or effort selection not covered. Natural-language invocation wording not reproduced in this read. No dates.
Kind
documented
Locator
Roles; Who orchestrates; Live progress; Activation
Re-read 2026-10-09. macOS Apple Silicon and Intel; Linux x64 AppImage experimental; Windows not yet available. Git required; gh CLI optional but needed for PR workflows and offered during onboarding. Onboarding checks prerequisites live: the checklist updates when git, gh or agents are installed or signed in. At least one coding agent needed. iPhone and iPad app: iOS 26 or iPadOS 26 or later and Superset Pro; enable Remote Access to reach agents on your computer; cloud workspaces in early access. Android not available yet; join the waitlist. No dates.
Kind
documented
Locator
Platform and versions; Requirements; First launch; iPhone
Re-read 2026-10-09. Cmd+N creates an isolated git worktree on its own branch. Prompt-first flow: describe the task, pick an agent and create; the agent starts immediately. A project can be added from a local folder or a cloned remote. No dates or versions.
Kind
documented
Locator
Creating a workspace; Racing agents; Shipping the winner
Re-read 2026-10-09. Terminal scripts are reusable terminal launches, each with a label, shell commands, optional working directory and launch mode. They appear in the Scripts bar above terminal tabs. Each script applies to every project or selected projects and runs from any matching workspace. Older versions called them presets; the superset presets add command remains as an alias. Per-agent task prompt templates are not on this page; the Import agent action links an agent configuration.
Current model docs separate workspaces, persistent terminals, agent status and git review. Local worktrees share host processes/network; event/schedule automations target hosts.
Version 2.0.6 (2026-11-08): cloud workspaces are out of beta and included in the Team and Ultra plans; Chrome extensions run in the browser pane; the chat interface is no longer experimental; Paradev moved from the Elastic License to MIT. Read from the repository source because paradev.com refuses automated fetches.
Kind
vendor-claimed
Locator
Changelog source for paradev.com/changelog, 2026-11-08, version 2.0.6
Re-read 2026-10-09. A workspace is an isolated git worktree on its own branch. A workspace lives on the machine that hosts its files, terminals and ports, which need not be the machine you are using. Remote access reaches workspaces hosted on another device. Automations dispatch scheduled agent runs to whichever device you pick. Sessions survive restarts. Cloud workspaces, early access and relay are not described on this page; the "Device filter" wording recorded on Oct 8 was not reproduced here.
Re-read 2026-10-09. iPhone and iPad app on the App Store, requiring iOS 26 or iPadOS 26 or later and Superset Pro. Push notifications are coming. Android not available yet. No supported web dashboard. Windows is planned with no date; Linux x64 AppImage experimental and untested; CLI supports Linux x64 and arm64. Local workspace files live on the host; agents send prompts and context to configured providers; remote access via relay is off by default; Superset never proxies model calls. Worktrees are not sandboxes: agents share processes, network and files outside the worktree. Terminals survive restarts through a background daemon. Every project must be a git repository; GitHub is fully supported through gh; repos with other remotes work locally; cross-machine project identity is tied to GitHub. Account deletion is not self-serve; email support. Pro features live in the v2 interface. Telemetry and licence not covered; no pricing or free-tier wording. Change from the Oct 8 record: iPad now described as on the App Store, not coming.
Kind
documented
Locator
Data Handling; Platforms; Isolation; Offline Behavior
The application's cloud engineering guide explicitly describes the sandbox VM, memory limits and swap configuration. The shipped backend provisions and resumes those environments through @vercel/sandbox. This concerns managed Cloud workspaces, not local worktree security.
Re-read 2026-10-09. superset start --daemon registers the machine with the relay. Desktop toggle "Allow remote access to this device via relay"; default state not stated. Only the starting user has access until members are added in Settings, Hosts (Add member); owners can promote or remove members. Terminals, agent runs and the diff viewer are proxied through the relay. iPhone or iPad needs the computer awake, online and running Superset. Turning access off restarts the host service and interrupts in-flight terminals. Port forwarding needs a host on host-service 1.26 or newer; TCP only. Owner-offline behaviour, co-prompting and concurrency not described.
Kind
documented
Locator
Hosts and the relay; Security; Who can access; Ports; Turning access off
Re-read 2026-10-09. superset start --daemon spawns a background daemon, writes a manifest and binds only to loopback; automatic updates off by default. The systemd example runs superset start without --daemon, requires KillMode=process and a CLI newer than 1.30.2. A headless machine uses the standalone installer; the desktop app starts the host itself. The first machine runs projects create and others run projects setup; projects are host-owned. Wake behaviour not described on this page.
Kind
documented
Locator
Daemon basics; Headless and VPS setup; Systemd; Upgrades
Re-read 2026-10-09. Host must be awake, online and connected to the relay; enable the relay under Settings, Remote Access, or run superset start --daemon. Mobile app shows "One step left" for a host that never connected, "Offline" with a last-seen time for an unreachable host, and "Can't check" when status fails to load. A scheduled run on an offline device is recorded as failed; retry from the Automations list. Updater race fixed in recent releases; terminals are held by a background daemon, so quit fully and relaunch. No owner or teammate access statement.
Kind
documented
Locator
Failure modes; Terminal reconnect and daemon behavior
Re-read 2026-10-09. Setup and teardown commands run automatically when a workspace is created or deleted, sequentially in the workspace directory, for each workspace; teardown also runs when deleting through the CLI, SDK or MCP. Terminal scripts are a separate type. Ports, port allocation, a .env copy step and run scripts are not described on this page.
Re-read 2026-10-09. The desktop app forwards detected ports from the selected remote workspace to the local machine. If a local port is busy, choose Use another port, which implies the default keeps the same port number. Relay routing, minimum host-service version and UDP are not stated on this page; it refers readers to remote access for requirements.
Re-read 2026-10-09: the overview example sets "setup" to ["bun install", "cp \"$SUPERSET_ROOT_PATH/.env\" .env"]; the Node.js example copies the same root .env. The Docker and full-config examples copy no .env files. The SUPERSET_ROOT_PATH table entry describes the variable only.
Re-read 2026-10-09: "Superset does not assign per-workspace port ranges." "If a local port is busy, choose Use another port from its row." Deterministic per-workspace ranges must be implemented in lifecycle scripts.
Re-read 2026-10-09: "On-demand: triggered by the Run button, not automatically on workspace creation"; "Dedicated pane: runs in its own terminal pane separate from your shell". The overview example config (not the prose) runs cp "$SUPERSET_ROOT_PATH/.env" .env in setup.
Setup/teardown run sequentially; Run starts restartable dedicated service terminals. Agents start parallel to setup by default; experimental wait-for-setup starts them only on success. No automatic dependency repair implied.
Paradev discovers listening workspace processes rather than assigning port ranges; user scripts may reserve/release them. Remote forwarding offers Use another port if local binding is busy.
Re-read 2026-10-09. Add account creates a second login profile for a provider; Make default picks the account new launches use; a running agent keeps its account until relaunched. Quota cards show account email, plan and one meter per window (Session 5h and Weekly for Claude), refreshed every 5 minutes. Token costs are estimates at API list rates; subscription usage shows "Cost to you: $0." Per-model and per-workspace drilldowns; 7, 30 and 90 day ranges; Cost and Tokens toggle; workspace drilldowns list top sessions by cost. Resources view refreshes CPU and memory every 2 seconds and groups processes by project and pane. No spend or token caps described.
Kind
documented
Locator
Subscription allowance; Per-agent breakdown; Estimates vs billed; Machine resources
Re-read 2026-10-09. Visibility: only you (private draft); anyone in the organization (default); anyone with the link, who can read without signing in and cannot comment or edit. Teammates pin comments to page elements; the agent republishes and replies; automatic comment delivery needs the host and agent session running. Edit permissions for organization members not stated. Public viewers can report a page.
Host members granted access can open the same remote workspaces and terminal sessions. The authenticated writeInput operation accepts workspace/terminal IDs and writes into that session without a creator-only check. Multiple granted humans can therefore send instructions to the same running agent terminal. The host must remain awake and online.
Kind
source-inspected
Locator
terminal.ts writeInput protectedProcedure; official remote-access Grant teammates access and continue workspace sections
Re-read 2026-10-09: "When an agent needs access to files outside its workspace," and "it will prompt for permission in chat so you can approve or deny the request inline." Inline Prompts: "Agents can pause and ask questions, request tool approval, and ask for plan review directly in the chat pane."
Local CLI works regardless of relay connectivity; remote access is opt-in. Git worktrees are not security sandboxes. Settings > Billing supports cancellation; account deletion, email changes and moving projects between organizations require support.
Kind
documented
Locator
Accounts and Billing; Workspaces and Git; Remote and Automations
Pages retain versions under one link, support pinned comment threads routed to listening agents and explicit shared versions. Publicreaders cannot edit/comment/history. Tool consent is perpage/plugin includingfutureversions/writes; UI revocation unavailable.
Re-read 2026-10-09. Review changes, stage files, commit, push and pull; split and unified layouts; focus mode; open a pull request on GitHub from the viewer. Review tab shows PR review comments, with resolved comments separated from open ones; PR check status appears in the changes sidebar. Selecting lines in a PR Code tab sends feedback to an agent; posting to GitHub is optional. Remote workspace support, image diffs and multiple reviewers are not mentioned on this page.
Kind
documented
Locator
Diff modes; Staging and committing; Push, pull, and PR creation; Review comments
Re-read 2026-10-09. Pull Requests view: resizable split view; connect GitHub under project settings to sync PRs. Merge options: Squash and merge, Merge commit, Rebase and merge. Close and reopen are header actions. The Merge action acts on the real PR through the user's GitHub connection, "with the same permissions and effects as merging on github.com." Checks show each CI run with a GitHub link; cancelled checks count as failures. Comment thread with reply composer. PR creation is described in the diff viewer. No dates.
Re-read 2026-10-09. Requires iOS 26 or iPadOS 26 or later, and Superset Pro. iPhone: available now through the App Store. iPad: available now; runs natively in portrait and landscape. Android: not yet released; waitlist ("Be first to know when it ships"). Features: start agents, follow them live, review the diff from iPhone or iPad. Reply to a waiting agent appears in a testimonial only; notifications not mentioned; "Your code stays on your machines." No launch date. Change from the Oct 8 record: the page now states iPad availability.
Split/unified diffs, staging, commit/push/PR actions and GitHub-synced review comments are documented. Selected PR lines can be sent to an agent with file, line range and diff side. A PR without a linked workspace gets a checkout workspace.
Kind
documented
Locator
Diff Layouts; Review Tab; Send PR Feedback to an Agent
PR list filters state/repository/author/review status and shows CI and diffsize. Summary contains checks/runlinks,reviews,comments/threads/commits and up to3 workspacePages. Line comments can send precise context to existing/new agent; narrowpanes stack; mergeusesGitHubpermissions.
Kind
documented
Locator
List filters; Summary; Code; Comment straight to an agent
Detected ports open in browser panes; remote workspace ports forward while selected. CLI browser screenshot writes a PNG. Design Mode sends an element DOM, computed styles, React metadata and cropped screenshot to an agent. This documents capture and preview, not retained recording or a general evidence gallery.
Kind
documented
Locator
Design Mode; Ports Integration; Drive it from the CLI and agents
Pages publish an HTML file or directory and link back to the workspace. The workspace menu lists its pages, pinned pages and All pages. Republishing the same source/workspace preserves a URL and earlier versions; versions can be listed and pulled. Public readers access only the shared version. Agent comment delivery requires a running host/session.
Kind
documented
Locator
Find Workspace Pages; Share a Page; Keep Iterating on the Same Page
Pinned schema retains task branch and prUrl fields. Current Tasks docs expose Run in workspace and GitHub issue Add to workspace. Schema fields alone do not establish a task-linked artifact gallery or exact-revision binding.
Kind
source-inspected
Locator
tasks table: branch and prUrl fields, lines 241-243
Run in workspace picks a project and agent and creates a workspace per selected task; GitHub issue rows have Add to workspace. This links work to tasks but does not prove retained child-review findings.
Re-read 2026-10-09. Review changes, stage files, commit, push and pull; split and unified layouts; focus mode; open a pull request on GitHub from the viewer. Review tab shows PR review comments, with resolved comments separated from open ones; PR check status appears in the changes sidebar. Selecting lines in a PR Code tab sends feedback to an agent; posting to GitHub is optional. Remote workspace support, image diffs and multiple reviewers are not mentioned on this page.
Kind
documented
Locator
Diff modes; Staging and committing; Push, pull, and PR creation; Review comments
Re-read 2026-10-09. Pull Requests view: resizable split view; connect GitHub under project settings to sync PRs. Merge options: Squash and merge, Merge commit, Rebase and merge. Close and reopen are header actions. The Merge action acts on the real PR through the user's GitHub connection, "with the same permissions and effects as merging on github.com." Checks show each CI run with a GitHub link; cancelled checks count as failures. Comment thread with reply composer. PR creation is described in the diff viewer. No dates.
Re-read 2026-10-09. Steps: Cmd+N, choose Pull request, search or paste the PR URL; prompt an agent to address each comment; check the Changes tab; push from the diff viewer if the agent did not; re-request review on GitHub; delete the workspace once the PR merges. The page does not say whether feedback sent from the Code tab or diff posts replies to GitHub. No dates.
Re-read 2026-10-09: "PR-based workspaces show pull request state in the sidebar." "If the branch has a deployment preview, you'll also see an Open Preview button."
Re-read 2026-10-09 from the first 100,000 characters of a 222,396-character page, newest first. Oct 4: "Coming Next: Native iPad Support" (next mobile build uses the full iPad screen; watch for the update on the App Store); browse and create Linear issues in Tasks, each member connects their own Linear account; Linear and GitHub integrations require Pro; failed automation runs retried from Automations, All runs; cloud automations in early access with no release date ("A Peek at What's Next"); phone voice mode is an internal prototype not in the App Store; merging from the PR pane shows a pending state. Sep 28: Superset Mobile live on the App Store; Google Calendar triggers removed; Slack page links unfurl. Sep 20: iOS terminal switching; Linux file-watching fix; standalone CLI HTML publishing; Pro setup checklist. Sep 13: PR pane; automations are a Pro feature; iOS feedback reading; notifications name project and workspace; Linux window controls. Sep 6: PR creation and inline review replies; image diffs; per-launch model choice from CLI, SDK and MCP. Aug 30: organization menu, command palette and dock or launcher reachable on Linux and Windows. Aug 27: "Superset has completed its SOC 2 Type II audit"; report available through the trust center. Aug 23: PR merge, close and reopen from the detail header; experimental event triggers (see changelog-events). Entries older than the Aug 2 truncation marker were not read.
Root LICENSE.md is MIT, copyright 2025-2026 Superset Inc. Pin is desktop-v2.0.5 tag commit. License covers code under this grant; it does not establish hosted-service parity or every third-party component license.
Root LICENSE.md is MIT (Superset Inc.). The server apps apps/api, apps/relay and apps/realtime are in the same repository with private package manifests and no separate license file; the only other LICENSE files are packages/sdk (MIT) and vendored utilities. README says the whole app is in the repo under MIT.
The current stable root licence is MIT, copyright 2025-2026 Superset Inc. It permits use, modification and redistribution subject to its notice requirement. Historical ELv2 text at fc44d32 does not describe this release.
README says the app is in the repository under MIT and can be forked, modified, self-hosted and redistributed; local parallel agents remain free and paid features are optional services. This is vendor documentation, not an observed self-host deployment.
The Recently Shipped list says the core loop of importing a repository, running an agent and reviewing the diff works signed out and offline, labelled August 2026. This is a documented local-core scope, not a test of vendor-account-free operation for remote access, Pages or Cloud. Orchestration chat remains Exploring.
The shipped roadmap explicitly says the complete core loop of importing a repository, running an agent and reviewing its diff works signed out and offline. This is usable local core functionality on the user machine, beyond MIT permission alone. Relay, Pages and managed Cloud remain separate vendor services.
Kind
documented
Locator
Recently Shipped: Offline / local-first mode, Aug 2026
Re-read 2026-10-09. Platform text: macOS desktop (Apple Silicon and Intel) with a Download for macOS button; experimental Linux AppImage; Windows not yet available; iPhone and iPad app on the App Store; no Android or web dashboard listed. Supported-agents list unchanged (Claude Code, Codex, OpenCode, Gemini, Cursor Agent, Mistral Vibe, Kimi Code, Grok CLI, Hermes, Muse Code, Devin, fx, Antigravity, Kiro, and any CLI-based coding agent). Local-first wording: cloud sync covers account and organization metadata only; no API proxying. SOC 2 Type II badge and Source Available, Elastic License 2.0 wording. "100+ agents" remains a vendor claim. Change from the Oct 8 record: iPad is now listed with the iPhone app.
Kind
vendor-claimed
Locator
Hero; FAQ; Supported agents; Download; Source available
Re-read 2026-10-09. Free: $0, one user, local workspaces, desktop app and CLI, no credit card. Pro: $20 per user per month billed monthly, or $15 per user per month billed yearly ($180 per user billed yearly); billed per active seat; unlimited users, remote access, automations, Linear and Slack integrations, mobile app. Enterprise: custom pricing, annual billing only; SAML SSO, SCIM, audit logs, SOC 2 Type II report, uptime SLA with dedicated support. Workspaces and projects unlimited on all plans. Plan changes take effect at the end of the billing period. No free-for-now, trial or deadline wording. Copyright line 2026 only. The "from $15" header noted on Oct 8 was not reproduced.
Re-read 2026-10-09. Visibility: only you (private draft); anyone in the organization (default); anyone with the link, who can read without signing in and cannot comment or edit. Teammates pin comments to page elements; the agent republishes and replies; automatic comment delivery needs the host and agent session running. Edit permissions for organization members not stated. Public viewers can report a page.
Re-read 2026-10-09. Policy last updated 2026-09-29. Analytics providers such as PostHog process usage data linked to the account identifier; device identifiers and OS version collected; diagnostics shared only when the user chooses. Cookies used for tracking. Messages sent to AI agents "are transmitted to and stored by our services so they can be delivered to your workspaces." Accounts permanently deleted after a 30-day recovery period. Data retained as long as necessary. Google user data not used to train generalized AI models; AI providers do not train on it. Names PostHog and Apple (speech recognition for dictation); refers to a Subprocessors page not read. No statement about Pages uploads. Desktop app described as running locally; no statement about where cloud workspaces run.
Kind
documented
Locator
Data collected; Code and prompt handling; Deletion; Analytics
Re-read 2026-10-09 at pinned commit fc44d32, apps/desktop/src/main/lib/analytics/index.ts (blob unchanged on main). Imports PostHog and DEFAULT_TELEMETRY_ENABLED from shared/constants; the PostHog client is created only when a PostHog key is configured; the telemetry-enabled function returns DEFAULT_TELEMETRY_ENABLED (line 33).
track() returns without sending when no user ID is set (setUserId) and when isTelemetryEnabled() is false. isTelemetryEnabled() returns DEFAULT_TELEMETRY_ENABLED. A PostHog client is created only when NEXT_PUBLIC_POSTHOG_KEY is set.
Kind
source-inspected
Locator
setUserId lines 36 to 38; track() lines 40 to 45; isTelemetryEnabled lines 32 to 34
Home page says code and agent sessions in local workspaces stay on the user's machine, cloud workspaces run in a sandbox, model calls go straight to the user's provider and Paradev does not proxy API calls; it no longer states metadata-only cloud sync.
Kind
vendor-claimed
Locator
Security section: Local First; Your Agents, Your Accounts; FAQ: Can I use my own API keys?
getTelemetryEnabled always returns true and setTelemetryEnabled returns success without changing state. Main-process analytics checks the compile-time true default, not an end-user setting. The SDK SUPERSET_TELEMETRY=0 control affects SDK method events only, not desktop analytics.
Kind
source-inspected
Locator
settings router lines 1328-1340; main/lib/analytics/index.ts isTelemetryEnabled and track; shared/constants.ts DEFAULT_TELEMETRY_ENABLED
Workspaces and Projects are Unlimited on Free, Pro, Team, Ultra and Enterprise; cloud usage is metered per GB-hour. Ultra is billed monthly; Enterprise is custom pricing with annual billing only.
The body explicitly gives October 26, 2026 as the effective date when Superset became Paradev. The page has an original October 12 date and an October 27 update date; neither is the effective rename date. Only the name, logo, website and email domain changed; the product, accounts and workspaces continue.
Kind
documented
Locator
Opening product description and What changes; page dated October 12 and updated October 27, 2026
Non-prerelease desktop-v2.0.6 published 2026-11-08, desktop-v2.0.7 on 2026-11-09 and desktop-v2.0.8 on 2026-11-10; desktop-canary and cli-v2.0.8 are prereleases.
superset agents read --workspace <id> --terminal <id> [--local|--host] returns the agent's saved transcript as a JSON object in JSON mode or as text; superset settings theme export <id> [--out] writes a theme's full JSON definition. The legacy presets command name remains an alias for terminal scripts.
The MCP server lives at https://api.superset.sh/mcp; the versioned /api/v2/agent/mcp URL keeps working for existing configurations; the legacy v1 server /api/agent/mcp has been removed and returns 410 Gone.
Kind
documented
Locator
L5-L7 callout on current, versioned and legacy v1 MCP URLs
At desktop-v2.0.8 the legacy /api/agent/[transport] route answers GET, POST and DELETE with HTTP 410 and error code GONE, "The v1 MCP server has been removed.", with a hint to connect to <API URL>/mcp.
The CLI works against the v2 local-first model only; projects in the legacy v1 interface are not visible to it until v2 is enabled under Settings > Experimental.
Paradev says it completed its SOC 2 Type II audit with an independent auditor and that the report can be requested via trust.paradev.com; scope and period are not given.
The desktop app is described as free forever. The whole app is in the repository under the MIT License: use it, fork it, modify it, self-host it and redistribute it.