November 2026 status archive, page 22 of 26
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
claude_codex_bridgeinitial researchresearch correction28 findings · 5 sources
Findings today
- CCB provides a native terminal application for Linux/macOS and a publicly downloadable native Windows x64 beta.
- Named CLI families include Claude Code, Codex, Gemini, OpenCode, Pi, Grok, Cursor and additional providers.
- Release history describes preserving local conversation history across credential/key/gateway changes for Claude/Codex.
- Install @seemseam/ccb, run ccb in a project, then configure installed providers using local Settings or ccb config ui.
- ccb config validate/update and ask manage topology and inter-agent collaboration.
- Optional Agent Roles packs bundle skills, memory and tools and are installed separately.
- CCB Mobile is a Flutter Android app distributed as an APK.
- A new project opens one demo agent using the first available CLI; a full team is not mounted by default.
- Project-wide .ccb/ccb_memory.md stores shared collaboration rules and durable context.
- Configured windows can run multiple CLI providers concurrently.
- ask requests and returned results share a per-target chronological FIFO.
- The Config UI edits per-agent provider, model, thinking level, pane topology and worktree scope.
- Humans can type in native panes or send phone input; queued messages wait for an eligible idle input surface.
- A project starts with one agent and can grow through visual pane/topology configuration and guarded reload.
- CCB runs installed provider CLIs and a project daemon on the current host.
- CCB separates configured workers with Git worktrees and terminal processes.
- v8.7.21 uses private legacy OpenCode database snapshots and opt-in v2 native ingress; uncertain historical jobs are…
- Managed draft protection waits up to 180 seconds before clearing a nonempty draft once; busy/modal states keep waiting.
- ccb-diagnose combines authoritative job state, queue/inbox/trace/provider logs and live-pane evidence for a named agent.
- One target agent processes ordered requests/results serially while different agents can work in parallel.
- Pairing profiles authorize view/content/terminal/file-transfer scopes; exact runtime authorization limits require…
- Project daemon state and shared memory survive closing the foreground UI; no immutable audit-retention claim is made.
- Optional Rich mode browses files, edits documents and previews media inside WezTerm/Yazi.
- Explicit worker(worktree) topology separates worker checkouts.
- CCB declares AGPL-3.0; its own license summary also discusses separately licensed closed-source commercial use.
- Core TUI/daemon and mobile gateway run on user-controlled machines from the distributed source/package.
- Native Windows x64 remains an unsigned beta and some provider ingress and queue behavior is opt-in; the 8.7.21…
- The license summary explicitly states CCB can be used for free, subject to its licensing terms and separate model costs.
Sources
Open the claude_codex_bridge page
CodeNomadinitial researchfreshness recheck34 findings · 8 sources
Findings today
- CodeNomad supplies native desktop packages for macOS, Windows and Linux and a standalone browser/PWA workspace.
- CodeNomad's built-in coding runtime is OpenCode V2.
- OpenCode-native OAuth subscriptions and API credentials are supported, with account selection scoped service-wide.
- Desktop includes Node/npm; select or install OpenCode, open a folder and connect a provider.
- Product-owned CLI launches and configures the standalone server.
- Workspace manages MCP connections, Global/Project plugins and SideCar web tools.
- Desktop variants use Electron or Tauri, with a SolidJS frontend and Node server.
- Native missions save an objective and task tree separately from conversations, and create remains paused until…
- Missions retain durable plans, task briefs and reports with explicit amendment controls.
- Mission tasks record dependencies, execution identities and nested conversations.
- Project files, saved briefs, playbooks and followed conversation context feed missions.
- File references, tool images and agent-driven web previews are documented.
- Missions have durable tasks with states, briefs and reports, separate from session lists.
- Mission coordinator plans and delegates into native conversations and records task results.
- Mission objective and notes are durable, editable and linked to tasks; formal requirements approval remains…
- Multiple projects, sessions and specialist conversations can run concurrently.
- Mission coordinator owns task assignment and preserves original control identities.
- Product mission coordinator plans, delegates and exposes specialists, reports and progress in an inspectable tree.
- Native schedules and event launch criteria can arm future mission passages.
- Pause, Interrupt now, Stop and uncertainty-aware refresh are distinct controls; native permission questions appear…
- Mission task tree exposes dependency links, progress and retained reports.
- Five playbooks provide flexible mission, debugging, exploration, product delivery and two-model comparison.
- Standalone server executes on user-controlled host and can continue while the phone PWA is closed; host must remain…
- CodeNomad supplies worktree file separation.
- Shared OpenCode service survives closing CodeNomad clients; reconnect refetches state.
- Mission status distinguishes admitted input from observed work.
- Per-message tokens and cost estimates are separate from provider quota and wallet readings.
- Native OpenCode permission controls remain in force; the browser UI does not authorize all later tool effects.
- Conversation diffs, project files, tool images, previews and mission reports stay linked to work.
- CodeNomad manages Git/worktrees and can list forge issues and pull requests read-only.
- CodeNomad application source is MIT licensed.
- Core server and clients run on user-controlled hardware without CodeNomad accounts.
- CodeNomad says it has no telemetry or analytics.
- Desktop/browser source pass covers current 1.0 and OpenCode V2, including dev releases; install and upgrade…
Sources
Open the CodeNomad page
codex-actioninitial researchfreshness recheck26 findings · 4 sources
collaboratorinitial researchfreshness recheck13 findings · 3 sources
Zeroninitial researchresearch correction28 findings · 18 sources
Findings today
Sources
Open the Zeron page
dmuxinitial researchfreshness recheck19 findings · 3 sources
Findings today
- dmux supplies a terminal CLI/TUI inside tmux on macOS and Linux, not a separate desktop GUI.
- The fixed launch registry supports Claude Code, Codex, OpenCode, Grok Build, Cline, Gemini CLI, Qwen, Amp, Pi,…
- Optional internal inference supports API keys, OpenAI-compatible endpoints, Codex ChatGPT subscription login or Grok…
- Install npm package, enter repository and run dmux; dependencies include tmux, Node, Git and chosen coding CLI.
- dmux owns the CLI and terminal commands for pane/workspace management.
- Lifecycle hooks can run scripts around worktree creation and merge.
- Several coding agents run in parallel with individual worktrees/panes.
- Users jump between panes to interact, receive macOS attention alerts, and can hide panes without stopping work.
- Prompt intake can select multiple agents, optional goal mode and custom branch/base names.
- Agents run in tmux on the machine where dmux is invoked.
- dmux creates a branch and Git worktree per agent pane.
- Regular terminals restore last observed directory; tracked coding agents resume conversations when panes are recreated.
- Lifecycle hooks can prepare worktrees and handle merge steps; automatic dependency provisioning unestablished.
- Built-in file browser searches worktree files and previews code/diffs.
- Pane menu can merge completed work or push branch and create GitHub PR; custom base/branch names are supported.
- Merge menu brings task branch back to main and cleans it up.
- dmux application source uses MIT license.
- Core dmux CLI runs on user-controlled hardware with local tmux/Git/Node and installed agents.
- Latest listed release v5.11.1 was published August 16, with terminal naming/activity improvements.
Sources
Open the dmux page
Fusioninitial researchfreshness recheck40 findings · 8 sources
Findings today
- Web dashboard (installable PWA), CLI, a released Windows x64 Electron desktop app and an Android APK.
- Fusion has explicit installable Cursor Agent and Grok CLI runtime plugins, plus an experimental generic ACP runtime…
- Subscription OAuth, API-key and local-model paths are separately documented.
- One-command daemon and dismissible onboarding support local setup; remote use requires a running host.
- Product CLI and HTTP APIs create/manage tasks, agents and routines.
- Fusion owns MCP configuration and plugin setup; actual tool calls depend on runtime support.
- Desktop is Electron and mobile is Capacitor, with a separate browser dashboard.
- Native tasks are created in dashboard/CLI or imported from GitHub; external sync scope is not assumed.
- Planner writes PROMPT.md with steps, file scope and acceptance criteria.
- Mission hierarchy and dependency-aware dispatch are documented.
- Agents retain project and identity instructions/memory; no product-spec drift fixture was run.
- Research and knowledge tools retrieve web/GitHub/local documents; architectural enforcement remains untested.
- Product-owned tasks have durable state, metadata and board/list/graph views.
- Agent tools create, assign and delegate native task records.
- Independent tasks execute concurrently with configurable project/system limits.
- Durable agent roles, assignment tools and opt-in backlog claims route work.
- Fusion owns orchestration, task delegation and agent mail.
- Daemon schedules and webhook routines start work unattended.
- Active task details expose nudge/pause/re-prompt and question response cards.
- Boards, graphs, mission planner and Command Center expose multiple work items.
- Quick fix, coding, review-heavy and custom graph workflows are selectable per task.
- Fusion runs its engine/dashboard on user-controlled local or remote hosts.
- Tasks use Git worktrees with optional native, bubblewrap, macOS Seatbelt, Docker/Podman or custom execution backends.
- Chat streams are resumable and remote clients share daemon state; crash recovery was not tested.
- Step timeouts, task token budgets and retry/escalation settings are documented.
- Command Center, task logs and task chat expose usage and progress.
- Costs are estimates based on provider-qualified model prices; unknown pairs remain unavailable.
- Engine caps project/system agents, task claims and process-wide verification.
- Bearer access, trusted MCP and planner confirmation policy provide distinct documented boundaries.
- Task detail combines plan, reviews, diffs and live file changes.
- Tasks retain plans, reviews, diffs, files and attachments.
- Configurable workflows distinguish pre-merge blocking gates and informational post-merge steps.
- Integrated Git worktrees, PR creation and GitHub issue import are documented.
- Merge behavior is configurable; planner confirmation claims coexist with global/per-task auto-merge.
- Task workflow links completion to direct squash merge or merged PR.
- Review columns and PR workflow fragments organize several changes, without a tested six-task review fixture.
- Fusion repository is MIT licensed; external provider terms remain separate.
- Core daemon, dashboard and clients are self-hostable.
- Fusion is early preview with beta releases and public support channels.
- Open-source local install offers evaluation with own providers and compute.
Sources
Open the Fusion page
Gas Towninitial researchresearch correction41 findings · 42 sources
Findings today
- Gas Town supplies a gt CLI and browser dashboard.
- Gas Town supplies built-in runtime presets and generic user-defined commands.
- Users install the underlying agent CLI and authenticate it themselves.
- A native host requires Git, Beads, Dolt and tmux for the full agent roles; Docker packages prerequisites.
- The product-owned gt CLI manages workspaces, agents, dispatch, convoys, scheduler and escalation; the browser…
- TOML formulas define reusable work steps, and custom runtime aliases configure external coding agents.
- Gas Town tracks work as Beads issues with stable prefix IDs, groups them in convoys and dispatches by issue ID.
- TOML formulas are frozen into templates and instantiated as tracked work.
- Dispatch can target an epic and its children or a convoy and tracked issues.
- gt prime reconstructs role/work context and gt seance finds earlier sessions or queries a predecessor.
- The bundled Beads ledger gives persistent issue IDs and work state; the dashboard displays issues, hooks, convoys…
- Agents use gt/bd commands to inspect hooks, instantiate work, assign issue IDs, report done and escalate blockers in…
- Gas Town manages multiple coding agents working on different tasks.
- gt sling either dispatches directly or creates a separate ephemeral sling-context bead.
- The Mayor is a product-configured AI coordinator with project/agent context.
- The daemon heartbeat auto-dispatches bundled or user plugins with an elapsed cooldown gate to idle dog agents, and…
- The activity feed exposes stuck, stalled, zombie, working and idle agents.
- The terminal feed groups agents by rig/role, lists in-progress/recent convoys and streams events.
- Users can tell the Mayor what to build, manually sling issue IDs or run minimal tracking mode with their own agent…
- The full workspace manager runs on the user-selected host, including a server reached by terminal or the detached…
- Git worktrees and optional Docker provide the scoped execution separation.
- Poured workflows retain completed step rows and resume from the last checkpoint after a session dies.
- The runtime image bundles prerequisites.
- Enabled deferred dispatch controls concurrency to avoid rate-limit exhaustion.
- OpenTelemetry emits structured session, dispatch, agent-state, mail, formula and daemon events.
- The configured scheduler caps polecats, queues work and respects readiness before dispatch.
- The Copilot autonomous preset uses --yolo and Kiro uses --trust-all-tools.
- Agent identities, work provenance and actions are tracked in structured ledger records.
- The dashboard exposes completed work, merge queues and verification status, but does not display proposed-code diffs…
- The federation workflow accepts completion evidence URLs tied to wanted-work IDs.
- The Refinery batches merge requests, runs verification on the stack and bisects a failing batch to merge only…
- gt done pushes a worker branch and creates a merge-request bead for the internal Refinery.
- Workers do not push directly to the integration branch; the Refinery merges passing batches and isolates failed ones.
- Completed work is tracked through merge-request beads and hooks can be archived.
- The Refinery implements a bisecting queue for batches of worker changes, with verification and failed-work redispatch.
- Gas Town source is MIT licensed at the pinned default-branch revision.
- The CLI, ledger, daemon and dashboard run on the user host or Docker runtime.
- Telemetry is off unless an operator sets a GT_OTEL endpoint; events are then exported over OTLP and correlated by…
- The core software license permits free-of-charge use.
- The latest returned release is v1.2.1 dated June 6, while the pinned default branch changed October 28.
- The core application is available as free MIT software for self-hosting.
Sources
Open the Gas Town page
gh-awinitial researchresearch correction29 findings · 17 sources
Findings today
- gh aw ships a native GitHub CLI extension for macOS, Windows and Linux; this is CLI/TUI access, not a separate…
- Built-in engines and custom imported definitions are separate.
- A personal Copilot subscription can use COPILOT_GITHUB_TOKEN.
- Install the extension, select/authenticate an engine, add Markdown workflow source and compile its lock file.
- gh aw compile, logs and audit provide workflow authoring and inspection operations.
- Declared MCP servers are filtered through the configured gateway tool allowlist.
- Workflow Markdown holds natural-language task instructions; YAML frontmatter sets triggers and policy.
- Cache-memory persists declared files between runs with workflow scope/retention.
- Workflows on distinct issues/PRs/branches may run concurrently; default per-engine groups serialize each engine.
- queue:max and cancel-in-progress settings determine pending-run retention and obsolete-PR cancellation.
- Schedule frontmatter can run a recurring workflow such as a daily report.
- Compiled workflows execute on GitHub Actions runners, including user-controlled Linux runners.
- AWF Docker isolation is the default; opt-in Cloud Hypervisor/NVX preview runtimes use KVM microVMs on eligible runners.
- Experimental engine.durable saves/restores native session checkpoints in artifacts, default seven days subject to…
- Top-level max-turns defaults to 500 for supported engines; Agy lacks this limit.
- gh aw logs and audit expose per-run duration, token/credit usage and tool/session information.
- AI Credits estimate inference per workflow run; Actions compute is a separate cost component.
- Workflow and engine concurrency groups bound overlap and preserve queued work where configured.
- The gateway applies explicit tool allowlists; engine-level tool enforcement differs by engine.
- The extension exposes workflow logs, audit reports and output artifacts, not a product UI for reviewing proposed…
- Workflow configuration separates deterministic CI jobs from agent reasoning and permitted outputs.
- create-pull-request safe outputs propose code in a separate permission-scoped job.
- Merge operations are separately configured safe outputs with scoped credentials; PR creation alone does not grant…
- The gh-aw compiler and runtime repository use MIT.
- The product code and execution worker can run on user-controlled runners, but GitHub Actions supplies workflow…
- The gh-aw extension/compiler is free MIT software without a paid extension plan.
- Release v1.2.2 (commit 399a445) was the latest stable release at the 2026-11-16 source pass, with v1.3.0 a…
- gh-aw itself is free; model and runner charges remain separate.
- The application adds no platform charge; inference and Actions minutes remain separate billed units.
Sources
Open the gh-aw page
Ghostexinitial researchresearch correctionfreshness recheck34 findings · 5 sources
Findings today
- The product ships desktop/native phone clients.
- Multiple coding agents are launched and represented in chat or terminal views.
- Users bring their existing agent; usage/account switching is documented for Claude and Codex.
- Installers and existing agent setup are documented; no first-task timing was measured.
- The ghostex command lets agents open sessions, prompt other agents and read replies.
- Optional views and plugins extend the workspace; provider tools remain separate.
- Vendor identifies a Rust/GPUI desktop shell with native terminal and Chromium/VS Code panes.
- Projects organize sessions and optional Kanban work.
- Plans can be opened, annotated and returned to an agent with line-number feedback.
- Session history and reference files can be revisited, without a verified managed memory contract.
- The optional integrated Beads board provides persistent issue cards with state and metadata separate from agent…
- Multiple sessions and coordinator threads are documented; concurrency quotas remain unknown.
- Ghostex coordinates child sessions through product commands.
- Scheduled prompts are listed as a product automation capability.
- Follow-ups may be queued or delivered to interrupt current work.
- Sidebar threads and coordinator views expose multiple sessions, without a tested fleet fixture.
- Agent/model/effort can be selected and a coordinator can manage multiple threads.
- Ghostex runs agents locally, on SSH machines or in boxes created in the user external cloud-provider account.
- Worktrees and optional agentbox Docker boxes are documented.
- Past sessions can be searched and resumed; crash recovery was not tested.
- Usage limits and session progress are visible; totals and failures were not reconciled.
- Shared chat guests can send instructions under host-controlled modes.
- Shared chat links have message controls, codes, expiry and immediate revocation.
- Shared chat activity has a guest message log.
- Readable diffs and annotations support review and feedback.
- Files, plans, HTML and diagrams can remain beside the conversation.
- Changes view integrates branches, worktrees, commits and pull requests.
- Changes view offers hunk/file revert and PR state links.
- Ghostex repository uses MIT; bundled third-party components retain separate licenses.
- Local desktop code is available and users connect their own remote machines.
- Settings document an analytics toggle and its default.
- Application is free; no per-task provider cost was established.
- Active release artifacts and community support are public, with iOS TestFlight access restrictions.
- Vendor explicitly says Ghostex is free; provider and compute costs are separate.
Sources
Open the Ghostex page
Happyinitial researchresearch correction37 findings · 40 sources
Findings today
- Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI…
- Happy Agent runs its own loop by default and calls Claude, Codex and Grok models on existing CLI sign-ins.
- Happy reuses existing Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP agents…
- Importing registers an existing folder without moving, copying or initializing Git.
- Happy Agent exposes a token-authenticated REST API for sessions, streaming events and control on user infrastructure.
- Skills are SKILL.md files and MCP servers are mcp.toml entries; agents can write both.
- The built-in Chief of Staff handles setup and task creation through ordinary conversation, including projects,…
- Subagent trees are capped at depth three and at most five agents including finished children.
- AGENTS.md files in the project tree are read by each agent and reread when they change; global AGENTS.md applies…
- Subagents run in the background by default and return completion to the parent.
- Bots and their subtasks may create a full conversation in a new workspace, with the creator as coordinator.
- Agents delegate bounded work, choose each child model and effort, receive background completion notices and send…
- Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts.
- Agent questions remain in the conversation and experimental Inbox; answering on one device closes the shared state.
- Per-session UI shows phase, tools, background processes, subagents, waiting state, whole-tree token usage and…
- The built-in Chief of Staff configures accounts, imports projects, pairs phones, deploys remote agents and creates…
- Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an…
- Parallel workspaces use Git worktrees on branches cut from the remote trunk.
- Conversations and child sessions persist across window closure and runtime restart; finished children accept…
- New workspaces copy configured sync files and run setup_commands.
- Smart provider pools can rotate same-provider accounts after authentication or quota-exhaustion errors.
- Session status includes active tools, background work, subagents, waiting state, tokens and changed files.
- Provider quotas are polled about every fifteen minutes and shown in the app; they are observations, not billing records.
- Team members see the same projects and sessions and can speak to the agent.
- Team mode verifies per-user WorkOS tokens.
- Read only, Workspace write, Auto and Full access share a permission model.
- Session transcripts retain provider-specific opaque data; compaction creates a visible message describing replaced…
- The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed…
- Named teammates operate on shared sessions and projects on the same team server.
- Happy Desktop shows files and diffs with conversations, and its documentation includes a recipe for a live, shared…
- The mobile app, original CLI and relay repository has the MIT license.
- The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely.
- Happy apps send pseudonymous usage events to PostHog, excluding message content, prompts, code and file names, and…
- Happy is free and MIT licensed.
- Happy Agent v0.4.108 adds GPT-6.1 Terra and stop-state persistence; Desktop v0.0.102 has opt-in beta Stem cells.
- The desktop application and self-hosted runtime are free.
- The core ADE has no software subscription charge; coding-model subscriptions, host resources and optional voice are…
Sources
Open the Happy page
Herdrinitial researchresearch correction31 findings · 34 sources
Findings today
- Herdr TUI runs as a Rust terminal program with a product CLI on macOS, Linux and Windows; it is not an Electron…
- Herdr TUI runs existing agent CLIs in real terminal panes.
- Install the Herdr binary or a package-manager build, start it where the repository lives and run existing agent…
- Herdr provides CLI wrappers and a local socket API for workspaces, tabs, panes, agent prompts, waits, state events…
- Plugins extend Herdr terminal panes and workflows, with a marketplace and CLI/API management.
- Herdr TUI is a Rust binary running in the user terminal rather than an Electron app.
- Scripts and agents create and name workspaces, tabs and panes.
- Saved session shape retains workspaces, tabs, panes, current directories, layout, focus and supported native agent…
- Multiple agent terminals run concurrently; working, blocked, done and idle states roll up into tabs and workspaces.
- Agents and scripts can start, prompt and wait on selected panes.
- Herdr ships an agent skill and CLI that let an agent in a Herdr pane start agents in other panes, prompt them, read…
- Known agents report or are detected as idle, working or blocked, with notifications when they finish or need input.
- The sidebar rolls a blocked pane up to its tab and workspace, and shows active work and done agents until viewed.
- Users can start one terminal task, split panes, prompt agents and wait on their state through the same CLI/socket…
- Local and saved SSH machines each own their server, sessions and processes.
- The TUI socket exposes worktree.list, worktree.create, worktree.open and worktree.remove with workspace provenance.
- Detach keeps original processes alive.
- Restored panes return to saved directories or remain visibly errored if the directory or shell is unavailable.
- Agent waits have explicit until and timeout_ms controls; an atomic prompt-and-wait avoids the race between separate…
- State derives from screen manifests or integration reports.
- Remote connection authentication stays with OpenSSH.
- Optional pane history stores recent terminal output locally and may contain secrets.
- Herdr native app ships a Changes panel for reviewing Git file changes and diffs.
- Herdr TUI lets one client own a terminal at a time; herdr agent attach and terminal attach accept --takeover to…
- Optional local pane-history replay preserves recent terminal contents after restart.
- Herdr TUI source is distributed under Apache License 2.0 at the pinned repository revision.
- The full TUI and its server can be built from source and run on the user machine or SSH host.
- Session data and optional pane history are stored in the local Herdr state directory; history may contain prompts or…
- The vendor states the native app, herdr-core and Herdr TUI are free and open source.
- The October 14 release fixes prefix shortcuts, Codex integration warnings, blocked Claude questions and Windows issues.
- The app, core and TUI are offered free and open source.
Sources
Open the Herdr page
Jcodeinitial researchresearch correction40 findings · 43 sources
Findings today
- Jcode provides a terminal UI and product CLI on macOS, Linux and Windows.
- Jcode is its own coding harness with Claude, OpenAI, Gemini, Copilot and Azure provider logins, local Ollama/LM…
- Jcode supports subscription OAuth and direct API providers, Claude subscription login and OpenAI/ChatGPT/Codex…
- Install the binary, run jcode in the project folder and choose a provider login.
- The TypeScript SDK launches a private Jcode process or attaches through api-bridge to a local or forwarded remote…
- Jcode loads global and project MCP configuration and imports Claude Code/Codex MCP servers.
- Users start an interactive project session or submit a noninteractive prompt through jcode run.
- Plans consist of phases, lanes and items with names, descriptions, lifecycle status, priority and confidence.
- Phases are ordered, lanes can run in parallel and items run in lane order.
- Repository and global AGENTS.md load into the corresponding scope.
- When one agent edits a file another has read, the server notifies the reader, which can inspect the diff.
- Native saved todo items have stable internal IDs, names, descriptions, priority, confidence, states and phase/lane…
- The coordinator owns the shared versioned plan and can propose, approve, assign and control tasks.
- Multiple agents can work concurrently in the same repository; the server manages messaging, completion status and…
- Only root sessions spawn swarm workers.
- Jcode agents can autonomously spawn a swarm, making the original agent coordinator.
- Ambient mode is implemented but disabled by default.
- Enter interleaves a message with the working agent and Shift+Enter queues it.
- Desktop offers a spatial session canvas and zoomed-out overview with task and orchestration views.
- Users start quick prompts, headless requests or swarm sessions, with provider/model/effort and feature configuration.
- The daemon owns sessions, tools and provider calls.
- Swarm coordination supports optional Git worktrees and worktree manager roles for separate code work and later…
- Normal uninstall retains config, authentication, memory and sessions unless purge is requested.
- Cloud handoff does not make machines identical.
- cloud wait exits unsuccessfully on timeout without cancelling the remote turn.
- Todo lanes show worker activity, observed tokens, throughput, connection, elapsed time and tool intent.
- The /usage and /info commands show provider limits, session information and tokens.
- Ambient mode admits only one ambient instance and gives interactive sessions priority.
- Temporary local environment access is scoped to the handoff lease, defaults to twenty-four hours and ends on…
- Plan item identity is preserved through matching-name replacement and explicit rename.
- Jcode Desktop renders file diffs beside live sessions, and the TUI /diff command cycles the diff display mode.
- The desktop client renders diffs, Mermaid diagrams, inline images and tool cards beside agent conversations.
- The inspected public Jcode CLI/desktop implementation has no dedicated native PR creation or management operation;…
- Jcode source is MIT licensed at the pinned revision, including a free-of-charge permission grant.
- The Jcode daemon, TUI and tools can run on a user-controlled machine or SSH host, with direct model credentials or…
- Default usage telemetry may include provider OAuth email, installation ID and numeric/categorical usage.
- Optional hosted plans start at USD 10 monthly with USD 20 inference credit and fifty Jcode Cloud machine hours.
- v1.0.0-preview.199, published November 6, is an opt-in v1 pre-release of experimental binaries, with production use…
- The application can be downloaded, used and self-hosted as free MIT software.
- The hosted plans disclose recurring USD charges, inference credit, cloud hours, API-price overage and separate…
Sources
Open the Jcode page
loki-modeinitial researchresearch correctionfreshness recheck40 findings · 14 sources
Findings today
- CLI runs on macOS/Linux, with current Control Plane web UI and optional editor integrations.
- Current supported coding providers are Claude Code/Agent SDK and OpenCode, with model routes separate.
- Existing Claude subscription login and API-key/local-model routes are documented separately.
- Install and setup/doctor check provider and project prerequisites; offline tour needs no provider.
- CLI and current Control Plane API create/inspect/control runs and outputs.
- MCP and agent instructions extend the CLI; legacy API details are scoped separately.
- Task text, PRD files and external tracker issues are accepted; tracker identity remains external.
- Run derives a delivery contract and checks from input task before implementation.
- Workspace repo dependencies and layered integration preserve cross-repo work identity.
- Local memory and context are available; managed persistent spec conformance needs separate evidence.
- Workspace runs execute independent repos concurrently within configured cap.
- Workspace scheduler orders child repo runs; agent assignment/claim enforcement remains untested.
- Loki owns multi-repo child execution and aggregates signed results, with review council in each supported run.
- Official user-installed GitHub workflow can start issue work from labels/comments.
- Newest release can continue an ambiguous task with a disclosed choice capped at PARTIAL; generic README stop-and-ask…
- Current UI groups run outcomes/receipts/costs, without a verified 12-state fleet fixture.
- Small edits, interactive chat and autonomous task/PRD flows are distinct entry routes.
- Local CLI or user-managed runner hosts execution; detach alone does not survive laptop sleep.
- Workspace tasks use separate worktrees; optional Docker scopes filesystem and credentials.
- Local run records persist and detached tasks survive terminal closure; runtime continuity was not stress-tested.
- Run spend caps and outcome limits are explicit; newest release may continue ambiguous work as PARTIAL.
- Run outcomes and sealed receipt verdicts have distinct vocabularies.
- Receipts record measured session costs/tokens with null/unrecorded fields; subscription cost is not zero.
- Workspace concurrency and integration stage gates bound multi-repo scheduling.
- Current Control Plane does not expose legacy RBAC or OIDC login.
- Current Control Plane uses bearer auth and loopback-only machine-mutating routes.
- Signed receipt and event digest provide scoped integrity evidence, not proof of code correctness.
- PR descriptions summarize requested change, checks and not-proven items.
- Signed receipt and local artifacts retain run checks and results.
- Task-derived checks, fail-to-pass behavior and review council produce scoped receipt verdicts.
- Primary flow opens PR after building and verifying, with local branch/no-PR alternatives.
- Deployment CLI has a signed-receipt gate distinct from PR publication.
- Verification checks code drift and rollback support records post-action health.
- Current Control Plane exposes merge queue and review-risk endpoints; high-volume UI behavior was not tested.
- Current source is BUSL-1.1 with use restrictions; future Apache conversion is not current license.
- Current core and Control Plane self-host without a Loki account; provider services remain separate.
- Diagnostics defaults and opt-out controls are explicitly disclosed.
- Existing self-hosted core is free; model and compute charges are separate.
- Current version is publicly released with changelog and issue support.
- Free self-hosted core and offline receipt sample support evaluation.
Sources
Open the loki-mode page
Lovableinitial researchresearch correction38 findings · 40 sources
Findings today
- Lovable provides native iOS and Android apps using the same account, projects and credits as its web app.
- A workspace subscription pools build credits for its projects and collaborators.
- Users describe a project or change in chat; the hosted builder explores the code, edits files and runs checks…
- The official MCP server lets external AI tools interact with Lovable projects using authenticated tools.
- Lovable can connect to custom MCP servers so the agent can access external tools and information.
- Natural-language prompts initiate project changes in the project chat.
- Plan mode investigates without changing code and produces a plan users can edit, revise and approve before Build mode.
- Project knowledge provides persistent instructions and context for Lovable across project requests.
- Read-only subagents can search files, inspect project code, perform lookups and browse the web, returning findings…
- Lovable can run multiple read-only research subagents concurrently on independent questions.
- Lovable starts Generic and Explore read-only subagents, displays their status and inspected steps, and receives…
- Users can send steering follow-ups while a build runs or stop it.
- The draft switcher shows working, updates available, new changes, needs input and failed states, with shared All…
- A /goal Build message continues toward an outcome for up to ten hours, accepts follow-ups and still pauses for…
- Web and mobile clients operate on the same hosted projects and require an active network connection.
- Each draft is a separate project copy with its own chat and preview.
- Accepted drafts enter project history.
- Build messages run up to ten hours and wrap up during the last half hour.
- Details view has a Timeline of tool calls and steps and a Changes tab showing resulting file edits.
- The response menu shows Credits used during execution and final cost after completion.
- Distinct Lovable accounts invited as project Editors can build in the shared project and access its editor/chat.
- Project and workspace roles include Viewer, Editor, Admin and Owner with explicit edit, publish, member and billing…
- Editors and above can publish by default.
- The Details Timeline records build steps and tool calls and Changes shows edits.
- Users can inspect per-change summaries and file diffs through Details, then return to Preview.
- Build results include file diffs and summaries in Details, with Timeline and Changes tabs.
- Lovable has browser testing, frontend tests and edge-function verification; most verification tools run when requested.
- GitHub Cloud and Enterprise connections provide two-way code sync, branch operations and pull-request creation.
- Editors and above can publish, while Enterprise policies can require an approval or block publishing.
- Every manual code save creates a version in project history and users can revert a broken edit.
- Vendor-authored service terms grant limited access and reserve ownership of the platform and underlying software to…
- Paid-plan editors can export the project as a ZIP; Git sync is available on all plans.
- Business and Enterprise workspace data are excluded from AI training by default; Free and Pro can opt out per account.
- Free includes five daily build credits capped at thirty monthly.
- Current release notes describe new AI image models on November 6 and memory maintenance on November 4.
- Lovable publicly asserts SOC 2 Type II and ISO 27001 compliance.
- An ongoing Free plan provides daily build credits capped monthly, unlimited workspace members and Git sync.
- Public USD monthly and annual credit tiers and included allowances are documented; Build mode consumption is…
Sources
Open the Lovable page
MonoCodeinitial research24 findings · 9 sources
Findings today
- Desktop installers support macOS Apple Silicon/Intel, Linux x64 and Windows x64.
- Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, omp, fx, Hermes, Antigravity and Devin CLI are listed.
- README explicitly says existing supported coding-agent subscriptions work; MonoCode does not sell tokens.
- Install/authenticate a provider, open a project folder, select an agent and send a message.
- Opt-in app CLI offers models.list, sessions.start/list/read/send/stop and note/worktree operations.
- Production uses React/Tauri; experimental native preview uses Rust/GPUI.
- Jira inbox includes issue descriptions/comments and starts work with a Jira identifier; it is an external tracker…
- Remote Plan mode creates a reviewable plan card whose Build action continues on the host.
- Operator notes.read/write stores project notes with IDs, titles and tags.
- README explicitly documents separate Git worktrees for parallel tasks and split sessions.
- sessions.start accepts provider, model, effort, permission mode and worktree scope.
- Experimental Monos can run user-configured scheduled tasks.
- sessions.stop cancels the current local turn and pauses queued messages; archive preserves its conversation.
- Installed provider CLIs execute in the chosen local project or worktree.
- Desktop/operator can create and choose Git worktrees for session file separation.
- Remote host restart retains transcripts and marks active turns interrupted; uncertain provider operations are not…
- Matching host archives are checksum verified; missing release artifacts cause an explicit error instead of falling…
- Provider permissions remain CLI-specific; native Supervised mode does not guarantee approval on every edit.
- Remote host stores transcripts/snapshots and preserves pending request identity across desktop restarts.
- Desktop and remote Changes/Git views display file diffs and history.
- Remote Git views stage/discard files, commit and push through the host.
- MonoCode source is MIT licensed; provider trademarks and notices remain separate.
- Desktop and remote host can run from repository source on user-controlled machines.
- The React/Tauri app is production; Rust/GPUI remains experimental preview and uses the same saved database.
Sources
Open the MonoCode page
multi-agent-shoguninitial researchfreshness recheck31 findings · 3 sources
Nimbalystinitial researchresearch correctionfreshness recheck41 findings · 7 sources
Findings today
- Desktop runs on macOS/Windows/Linux; native iOS and Android companions and team browser documents/trackers have…
- Multiple provider lanes include Claude Code SDK/CLI, Codex SDK/app-server/ACP, Cursor Agent, Grok Build and…
- Provider lanes use entered keys or previously authenticated user CLIs; local LM Studio lane is separate from coding…
- Open/create document, work with agent and review edits.
- nim CLI queries workspace/session/document/tracker data, mutates trackers and offers local stdio wiki MCP.
- MCP client, internal tool servers and extension SDK provide custom editor/provider integrations.
- Desktop is Electron/TypeScript; iOS uses SwiftUI and Android Kotlin/Compose.
- Native typed tracker intake supports local creation, GitHub issue adoption and session links.
- Plans are native tracker types, linked to sessions/files/commits, with editable document bodies.
- Tracker ready view exposes unblocked work, dependencies and collections.
- Project knowledge memory, wiki pages and linked session context support persistent knowledge.
- Content search, code excerpts and browser AI tools supply code/context awareness.
- Product-owned tracker has typed bugs/tasks/plans, saved views, priorities, labels, assignments and durable states…
- Agents use tracker CRUD/readiness and session links; humans see the same persistent records.
- Plans and requirements can remain in linked tracker/document files with revisions and review states.
- Parallel sessions and Blitz can run across isolated worktrees.
- Coordinating sessions can spawn workers with explicit reporting policy and selected reasoning effort.
- Product-owned session tools spawn, inspect, message and receive results from child/sibling/isolated sessions.
- Markdown frontmatter automations schedule recurring AI work by interval, daily or weekly.
- Super Loops expose pause/resume/stop; desktop/mobile can steer and cancel sessions and answer prompts.
- Nested workstreams and session kanban show parent/child activity and rollups; no high-load fixture was run.
- Direct sessions can grow into orchestrated workstreams with retained caller links.
- Local desktop execution plus user-controlled headless Node/Cloudflare sandbox execution are documented, with remote…
- Parallel coding sessions and loops can use separate Git worktrees.
- Desktop auto-continue and persisted session history are documented.
- Session states, workstream rollups, logs and context usage are visible; no operational accuracy benchmark was run.
- Humans collaboratively edit shared documents/trackers with presence and discussion.
- Team invite/join and owner/admin member/invitation controls are documented; SSO assurance remains unestablished.
- Local interactive permission prompts, plan approvals and per-project agent permissions are available.
- Tracker states, document revisions and commit/session links retain activity and decisions.
- Rendered document changes and code/PR diffs support accept/reject and review navigation.
- Documents, code diffs, mockups, browser captures and tests can remain linked to sessions/trackers.
- Built-in Git worktree, commits and GitHub PR review/merge are documented.
- In-app PR approve and merge uses gh authentication.
- Commit history links produced commits to AI sessions and retained tracker references.
- Application repository is MIT licensed; separate collaboration server license/parity is not established.
- Core desktop and headless runner can run on user infrastructure; hosted team sync is a separate service/project.
- PostHog anonymous analytics can be disabled.
- The Nimbalyst app and personal wiki are free.
- v0.82.7, published November 4, is marked a GitHub pre-release; the latest release not marked pre-release is v0.81.7,…
- Free application download with MIT source is available on desktop.
Sources
Open the Nimbalyst page
open-sweinitial research34 findings · 11 sources
Findings today
- Experimental desktop installation supports Apple Silicon macOS Ventura or later.
- Robin runs its own Deep Agents loop on Managed Deep Agents; the Claude Code connection is a read-only mirror.
- Deployments use model-provider API keys or LangSmith Gateway credentials.
- Setup documents backend deployment, GitHub App, Slack App, allowlists and model credentials.
- robin/oswe are product CLI entry points.
- Product-managed instance, workspace and personal MCP connections support headers or OAuth; collaborative threads…
- Robin Desktop uses Electron and downloads a backend-selected UI archive.
- Work starts in the dashboard, GitHub conversations, Slack or optional Linear delegation.
- Shared repository instructions, organization skills and private user instructions have documented scopes.
- Independent cloud threads and separate local worktrees can run in parallel.
- Local desktop refuses starting another active agent in the same tree or switching its branch underneath it.
- The runtime configures general-purpose subagents for independent work.
- Recurring automation can start system-owned coding threads.
- Slack Stop interrupts ordinary thread work, while other participants queued work may continue.
- This Mac bridges a selected local folder to the backend-managed agent loop.
- Local desktop can create a dedicated Git worktree per thread.
- Local threads keep their transcript on the backend and can reopen the bridge on follow-up.
- Admins can capture workspace toolchain snapshots for later sandboxes.
- LangSmith is the default trace provider.
- Workspace and Slack collaborative threads can be prompted by participants without using personal MCP credentials.
- Configured admins administer all workspaces; signed-in users can use every workspace.
- Workflow-file push approvals cover detected pushes rather than every shell/API write.
- Opted-in dashboard mutations and marked agent tools persist actor-attributed activity; unmarked operations are excluded.
- Opt-in Slack cards show a PR summary, size, branches and reviewers with GitHub review links.
- Desktop Changes compares against the initial Git snapshot and links the discovered PR.
- Human-review requests are refused for drafts, conflicts or failing required checks; this is a review-request gate.
- Robin opens and updates PRs, runs reviews and responds to CI feedback.
- Configured standard Slack human review can merge once reviewers approve, subject to its policy and feature flag.
- Review requests and desktop Changes link the relevant PR.
- Optional merge queue observes GitHub candidates; native observation does not execute merges or tests.
- Robin code is MIT licensed; vendor/ material is outside this repository grant.
- The core backend and web UI can be deployed using the documented Docker image.
- The documented optional PostHog and Segment integrations send nothing without keys.
- The project warns of breaking changes and calls desktop experimental; web UI is recommended.
Sources
Open the open-swe page
OpenChamberinitial researchresearch correction41 findings · 45 sources
Findings today
- OpenChamber has macOS, Windows and Linux desktop clients, a web/PWA client, VS Code extension and a CLI/server.
- The core workspace uses OpenCode to run coding agents.
- The Claude Code integration reuses Claude Pro or Max through the local Claude Code CLI sign-in without API keys.
- Desktop bundles OpenCode; CLI/Web requires Node.js 24.14+ and an installed OpenCode.
- Product CLI commands expose status, connect QR links, tunnels, startup control, logs, stop and update.
- Users configure local command or remote URL MCP servers with headers/environment settings, scoped personally or per…
- Git host issues and PRs become context for a new worktree/session; the message is not sent automatically.
- Plans are editable Markdown files retained at project level, imported from text/Markdown and optionally moved into…
- Agents can link todos to a plan and add dependencies on other todos in that plan.
- Project notes can be pinned into a session.
- Changes Walkthrough groups code-related edits, reads code/docs/tests and anchors its explanation to exact diff…
- The native project todo checklist persists across sessions, supports checked completion and ordering, and can…
- The managed-server project knowledge tool lets agents read and edit the same notes, plans and todos humans see, link…
- Multi-run starts several model sessions from one prompt, optionally each in its own worktree/branch.
- The native control tool creates sessions, sends prompts or follow-ups and can create worktree sessions.
- An agent can create a child session with a selected model, list status, read the latest assistant response and send…
- Native scheduled tasks send prompts in new sessions once, daily, weekly or by cron, optionally as goals.
- Stop and Pause abort the current turn and pause a goal; Resume re-arms it.
- The In work sidebar groups ongoing sessions and worktrees, shows status and news, and permits marking work done or…
- Natural-language requests can create another model session, an isolated worktree or a schedule, and inspect results…
- OpenChamber can run as desktop app or CLI/server on a workstation or the user's own server.
- A worktree session has its own checkout and branch to isolate concurrent edits; optional multi-run isolation creates…
- Archived worktrees preserve sessions, uncommitted changes and branch data for restore, but ignored files such as…
- Project setup commands run after worktree creation and on restore.
- Goals have optional token budgets, an automatic-continuation cap and stop on turn errors.
- The UI shows working, waiting, finished and failed sessions with approvals, schedules, provider limits, token use…
- Usage shows provider windows, model breakdown and pace; the agent usage tool can query those provider numbers and…
- OpenCode permission rules allow, deny or ask.
- Agent-created notes are labeled and stale whole-document replacements can be refused against the prior text.
- A guided walkthrough groups related edits into ordered stops with code anchors, shows outdated/uncovered areas and…
- Preview places the running app beside chat and can send element screenshots, styles and errors as agent context.
- A separate model auditor compares the latest turn to the goal, continuing until done, blocked or budget/turn limits.
- The Git panel can create/update PRs, mark drafts ready and merge, with equivalent merge requests or Gerrit changes…
- Users merge from the PR panel; Gerrit Submit waits for the change submit requirements.
- Walkthrough explanations are bound to exact code content.
- The OpenChamber application source is MIT licensed at the pinned revision.
- The full workspace/server can run on a user workstation or own server; optional Private Relay and tunnels provide…
- A Send anonymous usage reports switch in Settings turns off usage reporting, and Enterprise mode forces it off.
- The source application is available under a free-of-charge MIT grant.
- OpenChamber v2.7.0 was published November 8.
- The core application is free MIT software with user-hosted execution.
Sources
Open the OpenChamber page
Archived event links
Something wrong or missing?