November 2026 status archive, page 13 of 15
Shutdown notices, recent changes and all monthly archives
These events link to today's eligible findings, not historical before-and-after claims.
Cited events
20 ADEs
Intent by Augmentfreshness recheckresearch correction46 findings · 9 sources
Findings today
- Desktop, self-hosted browser and iOS access are documented; Windows/Linux desktop are Alpha.
- Intent runs multiple named coding harnesses with provider and model selection per specialist.
- Intent uses native provider account logins and supports separate Codex/Claude profiles.
- Onboarding supports local Git repos, cloned repos, new Git repos and remote service setup.
- Product CLI manages the daemon and access; agents call the workspace API.
- Intent connects MCP servers and imports repository instruction/skill context.
- Users create workspaces from prompts, local projects, GitHub PRs and Linear issues.
- Spec and Task Notes retain goals, scope and acceptance criteria.
- Task blocks express dependency and conflict metadata.
- Specs, notes, MCP and discovered instructions are shared workspace context.
- Notes link code and external tools; browser evidence supports visual inspection.
- Persistent Task Notes provide native work records beyond agent chats.
- Agents create and update the native task notes visible to users.
- The workspace Spec is a living shared requirements document.
- Multiple agents and workspaces can run concurrently.
- Humans and Coordinator agents assign task notes to specialists.
- Coordinator delegates to inspectable specialists and receives results.
- Daemon hooks and PR monitors start follow-up work from events.
- Stop, steer, queued follow-ups and structured questions are available.
- Home and Fleet HUD expose agents across workspaces.
- Single Developer tasks and Coordinator teams share configurable workflows.
- Run locally or place the background service and agents on a user-controlled remote machine.
- Workspaces use dedicated Git worktrees and branches; Work directly can disable isolation.
- Transfer retains notes/conversations/assets but stops processes and excludes terminal/event history.
- Saved setup scripts and remote preview forwarding help prepare workspaces.
- Provider quota failures can retry on another profile; idle reaping and agent caps bound activity.
- Streaming output, token views and workspace status are documented.
- Token usage is visible by agent/model; cost appears only when reported by provider.
- The daemon reduces repeat wakes and stops idle agents.
- An owner and invited collaborators can send messages to the same workspace agents under separate human principals.
- Workspace owner and collaborator roles enforce different permissions; host role enums also distinguish owner, member…
- Remote device access uses explicit pairing and token rotation.
- Persistent notes and comments retain decisions; transfers exclude event history.
- Review diffs, spec evidence and inline comments inside Intent.
- Workspaces retain documents, diffs and browser verification captures.
- Verifier specialist checks batches against spec; browser checks can record visual evidence.
- Intent owns Git diff, commit, PR and merge UI.
- Users can merge a PR or workspace branch inside Intent.
- Workspace timelines link commits and PR state and support local undo.
- Home lists workspaces and reviewable PRs; merge queue state comes from GitHub.
- Intent application repository is Apache-2.0 licensed.
- User hosts Intent background/web services; workspace transfer preserves selected data.
- Remote docs disclose plaintext web machine-token storage; iOS uses Keychain.
- Intent describes its desktop app as free and Apache-2.0 open source, with no paid plan or price published; model…
- Desktop is free; Windows/Linux are Alpha and current updates are documented.
- Intent describes a free desktop application; provider usage remains separately authenticated.
Sources
Open the Intent by Augment page
Jeanresearch correctionfreshness recheck37 findings · 14 sources
Findings today
- Jean has desktop builds for macOS, Windows and Linux, plus full host-served browser access.
- Linked projects, saved context summaries and reusable prompts provide session context.
- Jean exposes backend-specific steering and archived/unread session attention.
- Jean exposes editable workflow presets and session-specific model, effort and execution modes.
- Jean records run logs and exposes issue-sweep error status; operational accuracy is untested.
- Jean exposes diffs, saved context and review findings alongside retained session history.
- Jean reads backend MCP config and exposes global, project and session enablement.
- Jean accepts images, files, tracker context and linked repositories.
- Local and self-operated Linux server execution share browser/native access; remote agents continue when the…
- Jean stores chat/session state and archive metadata on the host.
- Jean supports inline diff comments and revisitable AI review findings.
- Jean supports worktrees, commits/push, PR actions and conflict resolution.
- Jean has confirmation before reverting the last local commit.
- Jean states there are no paid tiers or feature gates; agent and server costs are supplied by the user.
- Jean is downloadable with macOS tested and Windows/Linux builds needing further testing.
- Jean explicitly offers a free application without paid tiers, feature gates or usage caps.
- Jean runs installed coding CLIs with model and effort controls.
- Jean uses the user existing CLI subscriptions and authentication.
- The Linux server has documented binary/systemd onboarding.
- Jean exposes authenticated HTTP/WebSocket and product-owned MCP project, session and shipping operations.
- Desktop uses Tauri 2 with React; headless server uses Tokio/Axum.
- Intake starts from external repository and tracker context.
- Jean documents Plan, Build and Yolo sessions with saved context.
- Jean tracks project worktrees, labels and chat sessions and imports external GitHub/Linear context.
- Jean advertises parallel agents in worktrees and multiple sessions per worktree.
- v1.0.14 describes linked child sessions and automatic delegated-result return.
- GitHub issue sweeps remain a beta workflow; new Agents access is restricted.
- Canvas groups worktrees by state; the fleet fixture is untested.
- Jean separates task files with Git worktrees; agents share the operating-system user.
- Jean persists chats, archive metadata and native backend session IDs; crash fixtures were not run.
- Issue-sweep automation documents bounded failed-start retries and GitHub rate-limit deferral.
- The application has one instance-token access boundary, with no named human organization roles.
- Remote access defaults to token authentication; current release changes browser sign-in storage.
- The documented PR flow includes merge.
- Jean source distribution is Apache-2.0.
- Jean has user-operated desktop and headless-server routes.
- Jean keeps working state on its host and documents archive deletion and saved-secret handling separately from…
Sources
Open the Jean page
JetBrains Airfreshness recheckresearch correction17 findings · 78 sources
Findings today
- Air is reachable through the Air app on macOS, Linux and Windows, Air Teams in the browser, and Air in JetBrains…
- Air in IDEs runs local coding agents through ACP and terminal surfaces, explicitly including Claude Code, Codex and…
- Air in IDEs runs agent sessions on the user's machine by default, with Local and Temporary Worktree modes, and Air…
- In the documented current release, Air Teams usage tracking covers JetBrains AI only, and the Air app credit counter…
- Console Business is $20 per seat per month (monthly or annual billing); 1 AI credit equals 1 USD of provider-side…
- Fixed Air Governance Business seats are $20, $40 and $100 per month for one, two and five users.
- Air is in early access: the Air app is under an EAP user agreement, Air in IDEs is EAP, Air Teams is available to…
- Air app EAP terms allow free app use; AI usage is separate.
- Units are AI credits (1 credit per 1 USD of provider-side LLM cost) and Business plan AI seats at $20 per seat per…
- Plan mode lets the agent write a plan as a Markdown file in .air/plans before implementation and the user approves…
- Air app Plan mode stores Markdown plans and asks for implementation approval.
- Air Teams automations run in the cloud on a schedule, at an interval, or from GitHub, Jira or webhook events without…
- Run environment is selectable: Local Workspace (no isolation), Git Worktree, Docker (local) and Cloud; worktree and…
- Air Teams documents only per-task capacity and stopping: a cloud task runs on a selected predefined VM size, and a…
- The Air app offers Plan, Ask, Edit and Full Access permission modes; Ask requires approval before changes or…
- Central Console keeps an immutable audit log of organization administration changes (not AI activity) with CSV…
- Cloud tasks commit to a task branch and push after every agent turn; a person then opens the pull request from that…
Sources
Open the JetBrains Air page
Julesresearch correctionfreshness recheck34 findings · 23 sources
Findings today
Sources
Open the Jules page
Kirofreshness recheckresearch correction38 findings · 20 sources
Findings today
- The IDE supports macOS, Windows and listed modern Linux distributions; Crew has separate desktop support.
- Crew 0.12 exposes a fixed registry of Kiro/KAS, Claude Code, Codex, OpenCode, Pi, Goose, DeepSeek, Strands and…
- Crew runs Claude Code and Codex using each harness native sign-in and own credential store, reusing the external…
- IDE installation requires sign-in and opening a project; measured setup time was not tested.
- The Kiro license page states that Chromium is the IDE’s underlying engine.
- Crew Projects accepts a prompt or uploaded Markdown specification for a task run.
- A spec produces requirements.md or bugfix.md, design.md and tasks.md.
- Steps can declare dependencies; independent tasks run in batches.
- Workspace .kiro/steering and AGENTS.md guide sessions; global local files do not automatically appear in cloud…
- Steering files can carry product, technology and project-structure context; runtime architectural compliance was not…
- Crew Projects creates task runs from a prompt or uploaded spec.
- Task Runner injects the spec, working memory and prior Git state into each step.
- Feature specs persist requirements.md, design.md and tasks.md.
- Spec task execution can run independent tasks in parallel on IDE, CLI and Web; the matrix excludes mobile.
- Crew can spawn isolated subagents and synthesize their results; this does not establish IDE-native delegation parity.
- Crew Schedule creates recurring jobs in separate sessions; continued execution depends on its Gateway host.
- Approvals requested with no client attached wait for the next attaching client.
- Crew runs on the user's machine, container or controlled remote host; the desktop app can connect through an SSH tunnel.
- Each task uses its own kirocrew/task/ branch.
- Task Runner reconciles interrupted steps after a Gateway restart.
- kirocrew run --timeout sets a run timeout.
- The account dashboard updates credit usage at least every five minutes; pooled admin usage has separate dashboards.
- Crew allows three concurrent task runs and parallel batches of three independent steps.
- Crew 0.12 ships opt-in Shared Crew collaboration: owners can admit distinct people over Tailscale, and the source…
- Organization sign-in supports IAM Identity Center or external IdP such as Okta and Microsoft Entra.
- Spec force_approval gates can protect deployment/publish steps.
- IDE supervised mode shows agent-generated file changes for review.
- Task steps run tests before committing unless --no-test is selected.
- The Web spec flow implements tasks and opens a PR or merge request, with later feedback updates.
- Kiro Web explicitly says it never merges changes automatically; the user reviews before the default branch is changed.
- Per-step commits and Git log/diff state feed later step prompts.
- Kiro IDE and CLI use the AWS Content and AWS IP License terms.
- The Crew Gateway and dashboard run locally, in Docker or on a user-controlled remote host; Kiro/model-service…
- Improvement content can include generated code, questions, other inputs and responses.
- Monthly individual prices are Pro $20, Pro+ $40, Pro Max $100 and Power $200, checked 7 November 2026.
- Mobile is TestFlight early access, separate from IDE/CLI/Web availability.
- Kiro Free provides fifty credits monthly for limited listed models; cloud/Web access is not implied.
- Credit pricing is public but model choice and work complexity prevent deriving a fixed per-task cost.
Sources
Open the Kiro page
Lanes Desktopfreshness recheckresearch correction40 findings · 20 sources
Linzumifreshness recheckresearch correction37 findings · 4 sources
Findings today
Sources
Open the Linzumi page
Maestroresearch correctionfreshness recheck35 findings · 22 sources
Findings today
- Maestro exposes Claude Code project memory for reading, editing and deletion, and passes provider-configured skills…
- Released desktop Cue sends prompts on file changes, timers, scheduled times, agent completions and GitHub events.
- Auto Run supports presets, model options and queued steering notes between tasks.
- Agent Resilience pending retries do not survive quitting the app; Cue engine restarts mark in-flight runs failed,…
- Multiple people can prompt the same Maestro through browser clients.
- History persists summaries with session links, supports deletion and has a configured buffer.
- Auto Run has human-gate and halt markers; History Validated is explicitly only a bookmark.
- Maestro runs locally and can export Cue bundles for user-owned headless servers.
- Anonymous check-in and optional folder sync have explicit data and conflict limits.
- Maestro has public issue support and released/RC scopes that differ.
- Maestro has bundled CLI control plus a separate read-only documentation-search MCP server.
- Maestro inherits MCP tools, skills and authentication from configured coding providers.
- Group Chat queues busy agents by default, with an explicit unsafe concurrent-edit alternative.
- Group Chat has a moderator, follow-up rounds and named local/remote participants.
- Nested worktree agents expose parent relationships; the fleet fixture remains untested.
- Worktree setup scripts prepare missing files before agents start.
- Group Chat queues busy agents and exposes explicit queue pause/resume.
- Git menus and keyboard shortcuts expose diff and commit context.
- Maestro documents cross-platform desktop and phone-browser control.
- Maestro integrates several coding CLIs with provider-specific capabilities.
- Provider credentials decide subscription versus API billing.
- The desktop package uses Electron.
- Auto Run uses editable Markdown plans with on-disk checkboxes and resettable run copies.
- Markdown tasks can be saved and selected before explicit Auto Run.
- Maestro documents multiple agent processes and worktree agents.
- Desktop/SSH execution and headless Cue server pipelines are user-operated.
- Worktree agents use separate directories and branches.
- Maestro documents provider retries, per-run auto-resume caps and stalled-goal/document stops.
- The scoped Web Login uses local username/password accounts.
- Phone access uses a bearer URL token with full host control.
- History links completed Auto Run summaries to sessions and Git tools expose diffs.
- Git menu integrates worktrees, branch changes, push/pull and PR creation.
- Maestro root distribution uses AGPL-3.0.
- Maestro is AGPL-3.0 open source and downloaded from GitHub Releases, with no price or paid plan published; model…
- Maestro is a free AGPL-3.0 desktop download from GitHub Releases for macOS, Windows and Linux, and the website,…
Sources
Open the Maestro page
Multicafreshness recheckresearch correction22 findings · 78 sources
Findings today
- Web app, Desktop app (macOS, Windows, Linux) and a CLI exist; the iOS client is self-built from source, with no App…
- Multica does not provide model access in the sources read: each coding tool uses the account, subscription or API…
- Connected computers execute local-tool runs while Cloud or self-hosted Multica coordinates them.
- Estimated per-run and per-issue cost appears in the execution log with a cumulative curve, and the CLI reports issue…
- No public price list was found: /pricing renders a not-found page and the site offers Get started, Book a demo and…
- Internal self-hosted software license cost is $0 for one, two or five users.
- Current release is v0.8.1 dated November 6.
- Self-hosting is free for internal use (infrastructure and tool accounts are the user's), the website offers a Start…
- A commercial license for external hosted/embedded use is quote-only.
- The vendor website, the providers table and the install table each list 29 supported coding tools, including…
- Squads provide product-owned delegation: an agent leader receives the issue, @-mentions member agents, records an…
- Execution log exposes run state, timing and streaming transcript with classified failure reasons; a workspace…
- Review is issue- and PR-centric: in_review status, a pull request card with state, size, CI and mergeability,…
- Issues retain comments, attachments with versions, a deliverables sidebar and in-place previews (HTML, Markdown,…
- Multica shows CI status and mergeability on the PR card and can move an issue when linked PRs merge, but no…
- Agents run Git and the GitHub CLI themselves; Multica adds per-task worktrees, a task Git identity, optional…
- Merging is done by humans or by agents on request through the user's own Git tooling; the GitHub App is read-only.
- Workspace owners/admins keep an MCP server library that is assigned per agent and passed to most supported tools;…
- Agent instructions, workspace context, project descriptions and reusable skills provide shared context; sessions…
- Issues have parent-child relationships.
- Issue descriptions can hold persistent requirements editable by people and agents.
- Runs are unsandboxed and tool approval prompts are answered automatically by default; agent Access controls who can…
Sources
Open the Multica page
Omnarafreshness recheckresearch correction38 findings · 19 sources
Findings today
- Current Omnara exposes web, CLI and API; current native mobile clients are not established.
- Omnara uses its own model/tool agent loop with configurable model providers.
- Bring API credentials or use managed model credits; native agent subscription reuse is not documented.
- Create agent config and grants, then use dashboard/API/CLI; own machine and full self-host recipes exist.
- Product CLI, REST API, TypeScript SDK and event webhooks operate durable agents.
- Agents can call MCP/custom tools and load versioned skills.
- Agent conversations accept dashboard/API prompts and integration subscriptions.
- Agent configs, versioned skills and shared project memory retain context.
- External tools and versioned knowledge packages supply agent context.
- The scoped native database and API manage durable agent conversations and trigger configurations.
- Product subagents run concurrently within configured caps.
- Product dispatches subagents and leases execution steps to workers.
- Product-owned agents delegate, message/read children and receive their results.
- Omnara control-plane cron schedules (cron plus timezone) and provider events (Slack, Discord, GitHub) start agents…
- Queued/steering inputs, stop and permission interactions control work.
- Instances dashboard filters agent activity and exposes child relationships.
- Reusable profiles and mid-conversation configs customize agent behavior.
- Control plane persists independently of user/BYO or managed execution machines.
- Machine pools can use container sandbox providers (Daytona, Agent37, Modal) or microVM and full-VM providers.
- Durable event state survives workers and machine loss with explicit unknown external outcomes.
- Managed pools include development tools; custom images/snapshots and startup scripts are configurable.
- Model retries/timeouts/context limits and subagent depth caps are explicit.
- Agent activity distinguishes waiting, background processes, idle and archived; history records errors.
- Capacity caps and worker leases bound allocation and recovery.
- Authorized project operators can send input to the same durable agent.
- Organization/project roles are documented; SSO is documented for self-hosted deployments and the Enterprise offering.
- Per-tool allow/ask/deny policy creates durable permission interactions.
- Durable event timeline records attributed inputs, config changes and tool outcomes.
- Durable artifacts attach immutable downloadable content to agent events.
- Through the GitHub App integration, an agent assigned to a pull request can read its diff, comments and reviews,…
- Omnara describes the full platform as Apache-2.0 open source.
- Full control plane can run on own database/storage/compute.
- Self-hosting controls data stores; machine deletion does not delete agent history/artifacts.
- Platform has $0 fee; managed model/machine usage is separate.
- Current open-source daemon release and cloud/self-host access are documented.
- SOC 2 Type II is in observation, not a completed audit claim.
- Full platform is free with own models/machines and no card.
- Managed usage units/rates are public; Enterprise is contact-priced.
Sources
Open the Omnara page
Omnigentfreshness recheckresearch correction45 findings · 15 sources
Findings today
- Native desktop on three OSs, native phone apps, browser and CLI connect to product server.
- Named coding harnesses support direct/native modes with distinct support levels.
- Use native Claude/ChatGPT subscriptions, API credentials or compatible gateways.
- Local setup or user-hosted server/runner deployment are documented.
- Product CLI and REST API manage sessions, hosts and scheduled tasks.
- YAML agents use MCP/local functions/skills; owner controls live agent configuration.
- Native shells connect to server-served UI; desktop includes Electron browser.
- New-chat prompt creates a persistent session; external links may prefill drafts.
- Polly decomposes tasks; native Plan mode and persistent sessions retain planning context.
- Polly parent-child orchestration decomposes one task into parallel subtasks.
- Server stores skills/bundles/history and YAML defines shared tools/context.
- Custom MCP tools and browser inspection supply external knowledge.
- The scoped native UI and database have agent sessions, project grouping and scheduled automation definitions.
- Polly runs several coding agents in parallel.
- Polly routes implementation and review work to child agents.
- Shipped Polly orchestrator delegates inspectable mixed-harness children.
- Persistent recurring automations launch agent sessions from server.
- Shared prompt/approval control and notifications are available across clients.
- Agents panel, project session grouping and attention badges expose running work.
- Single agents, Polly presets and custom YAML define workflows.
- Separate server and hosts enable local or user-controlled remote execution.
- Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms.
- Server persists sessions through restarts; forks copy history with independent compute binding.
- Cloud sandbox configuration and remote SSH host setup are documented.
- Configurable policies cap tool calls and spend with approvals.
- Session state, output and incomplete Git data are visible.
- Spend policies use USD caps; broader billing reconciliation remains unestablished.
- Edit collaborators co-prompt the same live session.
- Admin/user management, OIDC SSO and Read/Edit/Owner boundaries are documented.
- Policy/harness gates ask or deny tools; owner controls permission mode.
- Committed session events and authorship persist and export.
- Changes and PR UI support diff review and inline GitHub conversations.
- Teammates co-drive a shared session or fork full history independently.
- Files, diffs, conversation and browser screenshots are accessible.
- Polly routes worker changes to a different-vendor reviewer; policy gates are separately configured.
- GitHub PR association, review and merge controls are documented.
- Product PR panel has merge controls; deployment authority remains unknown.
- Server retains session PR associations even with execution host offline.
- Compact PR list exposes checks/merge state and inline review discussion.
- Omnigent application repository is Apache-2.0.
- Full server/host is self-hostable and sessions export/import JSONL.
- Anonymous telemetry defaults on and has explicit opt-outs; session storage belongs to own server.
- Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or…
- v0.21.0 is released; public docs and issue support exist.
- Apache application is freely installable/self-hostable; providers and infrastructure cost separately.
Sources
Open the Omnigent page
Onafreshness recheckresearch correction40 findings · 23 sources
Findings today
Sources
Open the Ona page
OpenCoderesearch correctionfreshness recheck38 findings · 22 sources
OpenHandsresearch correctionfreshness recheck38 findings · 14 sources
Findings today
- Canvas provides desktop installation paths, browser UI and documented phone/tablet browser access.
- Canvas manages backend-scoped MCP, skills and plugins, with health and credential checks.
- Canvas documents skills and a persistent workspace/user memory setting that can be enabled or disabled.
- Canvas has reusable profiles, goals and backend-specific configuration.
- Optional containers and worktrees separate execution/files, with documented shared-HOME and shared-workspace limits.
- Goals and experimental critic refinement have explicit iteration limits.
- Canvas displays automation phase/status and exports reported costs with null for unavailable cost.
- Canvas automation history exposes reported per-run LLM cost with explicit missing values.
- Canvas exposes combined commit/uncommitted diffs and experimental critic feedback.
- Canvas self-hosts and provides portable conversation and automation exports.
- Backend settings/secrets and browser-generated exports have explicit boundaries.
- Canvas integrates OpenHands and ACP agents with custom stdio ACP commands.
- Local ACP providers can reuse native logins, while clean containers/cloud require credentials and have provider limits.
- Canvas launches linked child conversations and returns their results to the parent.
- Automation Server owns schedules/events and Canvas exposes lifecycle/run history.
- Canvas supports goal interruption and preserves failed-message retry controls.
- Canvas shows linked children and grouped conversation metadata.
- Canvas reloads backend conversation history and keeps archived conversations without deleting them.
- Backend concurrency caps can skip automation dispatch; resource-aware fairness remains unknown.
- Cloud organization automation conversations support read-only team visibility.
- Canvas exports timestamped conversation/tool history and retains archived messages.
- Canvas renders file artifacts, images and unified code-change views.
- Experimental critic evaluates OpenHands-agent results and can request bounded refinement.
- Canvas Git controls prompt the agent to commit, pull, push and work with PRs.
- Local stack requires Node 24 and uv; Docker and hardened VM routes are separate.
- Canvas uses the Agent Server REST API; SDK ownership is separate.
- Canvas is a React/TypeScript web frontend.
- The Canvas Task List renders the latest TaskTrackerObservation from the current conversation, with position-derived…
- Parallel conversations can use separate Docker runtimes.
- Canvas switches between local, self-hosted remote and optional cloud backends.
- The user chooses workspace mounts and runtime configuration.
- Organizations document Member/Admin/Owner permissions; paid Teams/Enterprise separately advertise SSO/SAML.
- Self-hosted public mode requires the backend API key.
- The Canvas source distribution is MIT.
- The current public self-hosted offer is free Canvas, Teams at $500/month for ten users plus $50/month additional…
- Teams and Enterprise plans carry paid identity governance; support ranges from community support for Agent Canvas to…
- The vendor advertises free local and self-managed Canvas use.
- Pricing page publishes monthly Teams rate and session caps, with Enterprise by quote.
Sources
Open the OpenHands page
OpenSpecfreshness recheck36 findings · 10 sources
Findings today
- OpenSpec ships a terminal CLI on macOS, Windows and Linux plus assistant workflow files, without a standalone…
- OpenSpec integrates workflow skills into Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok Build and…
- OpenSpec adds skills and commands to the user's existing coding assistant and runs inside it, so the assistant's own…
- Initialize in a project directory or create a separate planning store.
- Product-owned CLI exposes machine-readable change, spec, readiness and instruction operations.
- OpenSpec delivers configurable workflow skills into supported coding assistants.
- Ideas become named change folders through an agent workflow or CLI.
- A change retains its proposal, requirements, design and implementation checklist as files.
- Schema dependencies order planning artifacts before implementation.
- Project config and shared stores provide persistent instructions and upstream specifications.
- Planning can reference upstream specifications; freshness depends on the user Git checkout.
- Named change records and task checklists can be created and archived independently of a chat session.
- Assistant workflows operate the same named change artifacts users inspect.
- OpenSpec maintains canonical requirements through change deltas and archive/sync workflows.
- OpenSpec tracks plans and task checklists but does not own or run concurrent coding-agent sessions.
- OpenSpec supplies workflow instructions for an existing assistant without a product-owned coordinator or…
- OpenSpec workflows are invoked by a user or an external assistant; the product has no schedule or event runner.
- Apply pauses when tasks are unclear or errors block implementation.
- Profiles, schemas and natural-language workflows customize planning and implementation.
- OpenSpec runs its CLI and planning workflow on the user-controlled machine with an installed assistant.
- OpenSpec edits artifacts in existing project directories; it provisions no Git worktree, container or VM isolation.
- CLI reports planning and checklist status, not verified agent runtime statistics.
- OpenSpec shares planning artifacts through ordinary Git repositories; it has no shared agent prompting session.
- OpenSpec has no workspace identity service, named team roles or enterprise SSO.
- Specification and archived change files remain available through the user repository.
- OpenSpec prints task and artifact progress and supplies verification instructions; it has no code-diff review interface.
- Change folders retain documents and implementation checklists.
- Structural validation and report-only verification are documented; archive offers bypasses.
- OpenSpec leaves code commits and pull requests to the user and coding assistant; its native workflow does not create…
- Bulk archive reviews several changes and syncs deltas before archiving.
- The OpenSpec application repository is MIT licensed.
- The CLI and durable Markdown planning files run on user-controlled machines.
- OpenSpec documents telemetry identifiers and opt-out controls.
- OpenSpec is an MIT open-source npm package with no paid plan or price published; it runs inside your existing AI…
- OpenSpec 1.16.1 is released; store workflows retain beta status.
- OpenSpec is freely installable MIT software; coding assistant costs are separate.
Sources
Open the OpenSpec page
Orcafreshness recheckresearch correction29 findings · 66 sources
Findings today
- Desktop on macOS, Windows and Linux, plus beta iOS/Android companion.
- Orca launches and tracks existing CLI agents in terminals rather than embedding a harness: many CLI launchers are…
- Orca reuses the installed coding-agent native subscription logins, including Claude Code and Codex.
- Orca exposes a broad orca CLI (worktrees, terminals, files, browser, orchestration, automations, Linear, accounts,…
- Orca keeps lightweight task state: orchestration tasks carry a spec and status, worktrees carry a free-text comment…
- Workspaces can be nested under a parent workspace and orchestration tasks have dependencies and statuses including…
- Agents can read, create and update Linear issues through orca linear and set worktree comments and status, report…
- Orchestration dispatches a task to a specific worker terminal and treats the active dispatch as completion…
- Orca documents its own orchestration skill/CLI and supervised worker delegation, but the required Experimental panel…
- orca automations run a prompt on hourly, daily, weekday, weekly, cron or RRULE schedules against a repo or worktree,…
- Fleet views documented: sidebar worktree cards with N-children chips, an experimental kanban dashboard (Needs You,…
- Creating a worktree and launching an agent is a create-and-launch sequence with no mandatory workflow selection (the…
- Local desktop, user-owned SSH hosts and persistent Remote Orca Servers; experimental Cloud VM recipes use the user…
- No enforced time, turn, token or spend limit was found.
- Orca shows provider usage windows, resets and credit balances, and Stats with estimated cost from a local price…
- Orca is built around one developer machine or server; several paired clients can see the same server-owned workspaces.
- The self-managed Orca runtime uses revocable paired-device grants without named organization/project user roles or…
- A second client paired to a Remote Orca Server reaches the same server-owned workspaces, tabs and agent sessions.
- A done queue exists in the experimental dashboard and Agents feed with response previews, PR status filters and…
- Vendor policy describes local code/provider credentials and anonymous opt-out telemetry.
- The Orca application is advertised as free and open source with no price list; the Enterprise page offers rollout…
- No priced scenario was built.
- Latest GitHub release is v1.4.253, published November 7, 2026, following v1.4.252 the same day and v1.4.251 on…
- The desktop app is advertised as free and open source, so BYO-subscription and self-hosted scenarios carry no Orca…
- The site advertises the desktop app as free; no desktop seat, usage-unit or overage rate is established by the cited…
- A background daemon keeps local agent processes running across app quit, update relaunch and Orca app crashes.
- Orca documents native Run/Task/Dispatch records independent of external trackers, but the required Experimental…
- Native orchestration tasks retain a spec and link to execution attempts and decision gates.
- Approval handling is largely delegated to the agent CLIs: by default Orca pre-fills each supported CLI's…
Sources
Open the Orca page
Paseofreshness recheckresearch correction16 findings · 75 sources
Findings today
- Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact…
- Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a…
- Paseo reuses each provider CLI's own login for Claude plan, ChatGPT plan and API-key use, and adds no charge for…
- Paseo provides agent timelines (paseo logs), daemon and desktop logs, a Usage view of subscription quota windows and…
- In self-hosted Paseo Hub, distinct permitted Slack users can send instructions to one daemon agent by enabling Same…
- The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per…
- Fixed hosted Hub examples: one Free seat $0 for 50 runs/month; two Pro seats $30/month; five $75/month.
- Current stable is v0.15.3 on November 6, with separate Beta channel and gradual desktop rollout.
- The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a…
- Hub pricing lists the unit (seat), included runs and the seat definition; Paseo documents no model or compute charge…
- Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares…
- Paseo documents a plugin system and passes through the provider CLI's own MCP servers and skills; it does not…
- Paseo models parentage between agents (subagents, detach) and workspaces; epics, blockers and readiness states are…
- Paseo isolates file changes with optional git worktrees per workspace; same-workspace agents share files.
- Paseo persists agent records and timelines and resumes closed agents under the same ID.
- Stable v0.15.3 states no telemetry, tracking or required Paseo account for the local app.
Sources
- Paseo homepage
- Paseo: CHANGELOG.md
- Paseo: public-docs/orchestration-workflows.md
- Paseo: Why Paseo?
- Paseo: Supported providers
- Paseo: Workspaces
- Paseo: Git worktrees
- Paseo: Security
- Paseo: MCP reference
- Paseo: Hub security
- Paseo: Daemons in Hub
- Paseo: GitHub access
- Paseo: Docker
- Paseo: Run parallel tasks
- Paseo: Agent lifecycle
- Paseo: Troubleshooting
- Paseo: Plugins
- Paseo: Orchestration skills
- public-docs/why.md, line 23
- public-docs/why.md, lines 35 and 43
- env examples lines 56, 129 and 134; Multiple profiles line 118
- providers.openai.stt and tts apiKey examples, lines 94 and 98
- GitHub repository metadata
- Paseo homepage
- Paseo Hub plans and pricing
- Paseo GitHub releases
- Paseo: CHANGELOG.md
- Paseo: public-docs/orchestration.md
- Paseo: public-docs/orchestration-workflows.md
- Paseo: Getting started
- Paseo: Why Paseo?
- Paseo: Supported providers
- Paseo: Security
- Paseo: MCP reference
- Paseo: CLI reference
- Paseo: TypeScript SDK
- Paseo: Hub overview
- Paseo: Hosted Hub
- Paseo: Hub security
- Paseo: GitHub access
- Paseo: Hub activity
- Paseo: Hub public API
- Paseo: Self-hosting Hub
- Paseo: Claude Code provider
- Paseo: Codex provider
- Paseo: Agent lifecycle
- Paseo: Related projects
- Paseo: Updates
- Paseo: Troubleshooting
- Paseo: Self-hosting the web UI
- Paseo: Plugins
- Paseo: Custom providers
- public-docs/why.md, line 23
- public-docs/why.md, lines 35 and 43
- Native support (6 entries); ACP catalog (36 entries)
- GitHub API repos/getpaseo/paseo open_issues_count
- env examples lines 56, 129 and 134; Multiple profiles line 118
- providers.openai.stt and tts apiKey examples, lines 94 and 98
- Paseo homepage FAQ and integrations list
- Paseo Hub live page FAQ
- Paseo v0.11.1 Claude Code terminal access
- Paseo v0.15.3
- Paseo licence at v0.15.3
- Paseo desktop manifest at v0.15.3
- Paseo security docs at v0.15.3
- Paseo self-hosting Hub at v0.15.3
- Paseo v0.15.3 release
- Paseo v0.15.3: public-docs/supported-providers.md
- Paseo v0.15.3: public-docs/plugins/reference.md
- Paseo v0.15.3: public-docs/hub/workflows.md
- Paseo v0.15.3: public-docs/hub/security.md
- Paseo v0.15.3: public-docs/docker.md
- Paseo v0.15.3: docs/agent-lifecycle.md
- Paseo v0.15.3: docs/permissions.md
- Paseo Hub - GitHub, Slack, and Discord triggers
Open the Paseo page
Podiumfreshness recheckresearch correction11 findings · 72 sources
Findings today
- Docs state repositories and native harness credentials stay on machines you control and server state lives in a…
- Docs describe a first-run flow (install, podium, register a Git repository, confirm a detected logged-in harness)…
- Podium gives agents its own issue tools over CLI and MCP, and agent profiles import and export Claude Code agent files.
- v0.3.0 routes Podium issue instructions and relay environment through terminal and engine session launch.
- Not established.
- The spec CLI and service (living specs under pspec with stable SP IDs) are in v0.3.0.
- The server owns a scheduler for cron and one-time automations that spawn agent sessions, skipping overlaps and not…
- Issue actions, approval steps, comments and mail are recorded server-side.
- Artifact commands store immutable server-side copies of issue-linked files, including images, video, HTML and…
- The shipping service records revision-specific approval, configured validation and delivery receipts.
- Agent-session management requests go through an operator approval broker with approve and deny; the privacy docs say…
Sources
Open the Podium page
Proliferatefreshness recheckresearch correction38 findings · 15 sources
Findings today
- Repository documents Mac desktop and self-hosted browser app; native mobile release not established.
- The inspected Proliferate runtime supports the fixed native harness set Claude Code, Codex, Cursor, OpenCode and Grok.
- Detected native login, own API/provider config and managed gateway are distinct authentication routes.
- Source build and full self-host deployment recipes remain public despite missing website docs.
- Scoped runtime HTTP/MCP APIs exist; target general public agent API is excluded.
- Shared MCP, skills and custom tools extend native agent sessions.
- Desktop uses Tauri/Rust with compiled Vite web app on server.
- Prompted tasks execute in durable workspaces; source records do not establish tracker sync.
- Saved workflow definition carries prompts, inputs and materialized context docs.
- Workflow is a linear chain; child-agent hierarchy is bounded.
- Agents share configured skills/tools and retain durable conversation state.
- Proliferate persists agent sessions, local/worktree workspace lifecycle and workflow runs, without an accessible…
- Multiple task/child agents run concurrently.
- Parent agents dispatch and configure bounded child agents.
- Product-owned delegation keeps child identity, transcripts, messaging and parent result delivery.
- The current workflow implementation starts through a human click and a client courier; unattended schedule and…
- Close/open/interrupt and queued messaging control children; workflows can wait on a human.
- Current Agents pane exposes durable hierarchy and live state.
- Saved linear workflows and per-node agent picks customize work.
- Proliferate offers a local runtime and a self-hosted control plane.
- The current local workspace implementation provisions local clones and Git worktrees; subagents share their workspace.
- Durable runtime state supports archive/restore and history; restart interrupts workflow.
- Workspace setup scripts prepare execution; E2B cloud template status conflicts across repository docs.
- Child roster and workflow shape are bounded.
- Runtime statuses distinguish running, attention, human wait and completion.
- Organization owner/admin/member roles are documented in the current source contract.
- Workspace MCP enforces per-call role/relationship authority; workflow human-in-loop nodes park a run until approved.
- Frozen invocation and durable child results retain workflow history.
- Workspace diff surfaces and child transcript navigation support review.
- Workspace files, diffs, Cowork artifacts and workflow context docs are durable; artifacts are not session-linked.
- Workspace Git operations and a hosting PR read model are documented.
- Workspace Git API can revert changes; turn-start checkpoints are default-off and their revert consumers never landed.
- Main application repository is AGPL-3.0.
- Full control plane/browser application and local desktop runtime self-host from source.
- Desktop telemetry has a documented complete disable flag; self-host mode differs from hosted.
- User provider API configuration and native coding-agent accounts are supported.
- Public website is a holding page; source repository remains available.
- Application source can be built/self-hosted without a software license payment; hosted free offer unverified.
Sources
Open the Proliferate page
QM from YCresearch correctionfreshness recheck40 findings · 15 sources
Findings today
- QM offers web/PWA, Slack and a published Apple Silicon Mac desktop client.
- QM provides administrator-registered HTTP MCP connectors and own-deployment customization.
- Swarms dispatch durable reserved workers and deduplicate retried spawn/send requests by requestId.
- Web swarm strip groups workers under parents and exposes control/status.
- Scoped computers retain installed tools and support provider-specific snapshots.
- Operator error records and optional Sentry reporting expose logs and failure causes.
- QM has posture-based command rules and exact-argument single-use MCP approvals.
- Published Files retain artifacts after sandbox retirement.
- QM supports own-cloud deployment and durable Files/share outputs separate from sandbox lifetime.
- QM telemetry is deployment-configured with separate analytics and backend/browser error controls.
- QM is distributed as an MIT-licensed npm package and source for operator-run deployment; README links a separate…
- QM memory uses scoped revisioned records and grant-based skills.
- QM can search notes, documents, email, databases and web; scoped memory retrieval does not prove architecture…
- Headless QM crons, watches and webhooks run while users are away.
- Swarm workers can pause, resume or stop with retained session results.
- Feature-flagged swarm workers expose configuration and retained session identities.
- QM runs its headless core and agent resources on operator infrastructure.
- QM has per-scope sandbox computers.
- Durable core state, provider snapshots and file publication have separate recovery boundaries.
- Swarm goals/time budgets and resource reconciliation have bounded failure behavior.
- Swarm resource pools, durable cleanup and notification pools bound provisioning.
- QM supports people collaborating with an agent in shared Slack/web rooms.
- Organization security posture and project membership controls are documented.
- Durable shared session snapshots preserve selected visible history, separate from raw tool/audit history.
- QM advertises running tests and monitoring repository CI through the agent.
- QM advertises agent work in repositories including PR creation and CI monitoring.
- The current QM core runs the Pi coding-agent loop.
- QM supports both operator-provided model keys and personal Claude or ChatGPT/Codex subscription sign-in for human turns.
- QM supplies an agent-guided deployment directory and requires Postgres.
- Core HTTP APIs and scoped swarm routes provide programmatic operations.
- The web package uses Lit with Vite.
- QM accepts human prompts in personal and shared channels.
- The current QM API and web UI expose conversations/runs, schedules and approvals without a native independent issue…
- Swarms document independently provisioned worker sessions.
- QM swarm APIs retain linked worker sessions and addressable follow-ups.
- QM displays conversation artifacts, files and approvals without an integrated proposed-code diff review interface in…
- Slack and web share identity and configuration; full colleague takeover is unverified.
- QM repository is MIT.
- QM is MIT open source and self-hosted in your own cloud with your own model keys; YC publishes no paid plan, and the…
- QM is MIT-licensed software an organization deploys in its own cloud with its own model keys.
Sources
Open the QM from YC page
Archived event links
Something wrong or missing?