November 2026 status archive, page 15 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
2 ADEs
Capyresearch correctionfreshness recheck49 findings · 44 sources
Findings today
- Cloud VMs, desktop devices, Dock machines and movable threads are documented; own-cloud is Enterprise by agreement.
- Monthly plans grant shared credits, with no member fee; cloud compute and model usage have separate costs.
- Web and desktop clients are documented, a headless Dock CLI hosts threads, and docs state there is no mobile app.
- Capy runs its own agent plus a Claude Code mode, with a wide provider catalog; other native harnesses were not found.
- Cloud GitHub onboarding, repoless projects, desktop folders and Dock pairing are documented.
- A public bearer-key API covers threads, Captains, automations, reviews, usage and issues; capy dock is a device runner.
- MCP servers, marketplace plugins and portable repository instructions are documented.
- Prompts, Slack, Linear delegation and native Issues feed durable threads.
- There is no plan mode; plans live in prompts, Captain notes and Drive, with no acceptance-criteria field.
- Issues add sub-issues and blockers, and threads can grow into Captains; blocker enforcement was not established.
- Repository and Drive instructions, skills and saved files provide scoped shared context.
- Images, files and scoped Slack context are documented; architecture indexing and review enforcement are unverified.
- Native Issues (GA in 0.7.0) add backlog, assignment, labels and search separate from threads.
- Threads read, file, update and close shared issues, which are also in the public API.
- Repository specification files and Drive support an instruction-based spec workflow with human and agent edits and…
- Concurrent child agents and thread-level activity aggregation are documented.
- Issues hold assignees, and Captains and parents dispatch work; exclusive task claims were not established.
- Subagents and Captain crews delegate with explicit prompts, per-child models and returned results.
- Stored prompts support cron, GitHub/Slack events, webhooks and standing or fresh threads.
- Steer, interrupt and queued messages coexist with Stop run, Needs you and Failed status.
- Status, Needs you, Captain digests and issue blockers support an overview; no fleet fixture was run.
- A thread can stay simple or be promoted to a Captain that directs other threads.
- Cloud threads use Firecracker microVMs; device threads use worktrees and are explicitly not sandboxed.
- Cloud machine identity survives backing replacement; filesystem and process continuity differ.
- Versioned setup, snapshots and startup entries prepare and rebuild managed environments.
- Credits and connection exhaustion have visible stop/recovery behavior; broad failure guarantees are unverified.
- Live progress and spend/token breakdowns are documented; aggregate metrics were not tested.
- Per-thread cost, usage splits and exports exist; child, epic and provider reconciliation were not established.
- Plan-specific cloud machine and concurrent-RAM limits are documented; compute-aware arbitration and verification…
- Work is shared in an organization by default, and anyone with access can write in a thread; live ordering was not…
- Org roles, membership changes and private thread/project sharing are documented; enforcement was not tested.
- Device access has approve, deny and always-allow controls; the merge rule is an instruction, and cloud commands have…
- Threads retain conversation/activity and Drive retains attributed file versions; immutable audit guarantees are…
- PR pages expose diffs, checks and findings, with review comments sent back to the agent.
- Ownership transfer exists and shared threads are open to teammates; runtime takeover was not tested.
- Threads retain PR/child results and Drive saves files beyond cloud-machine lifetime.
- CI failures trigger repair and dedicated reviews triage findings; spec gates and enforced branch policy are unverified.
- Branch/commit/push/PR creation, comments and CI follow-up are documented.
- The documented merge rule requires a specific explicit ask; technical authority enforcement is unverified.
- PR links and merge events connect results to durable threads; rollback mechanics are unverified.
- Pull request pages, review guides, findings and stacks support batch review; a six-task queue was not run.
- The Capy application and hosted service use vendor-authored terms.
- Threads stay in Capy cloud even on devices; own-cloud is Enterprise by agreement, and export is through the API.
- Capy documents storage, retention, deletion, subprocessors and telemetry, and provider terms apply on your own keys.
- Only the fixed and variable rate parts of a scenario can be priced from public sources.
- Public downloads and dated releases are available; support response commitments were not verified.
- Capy publicly states SOC 2 Type II and provides a Trust Center; the report scope and period were not inspected.
- Local threads on your own subscriptions or keys need no plan; cloud threads need a plan or balance.
- Public plan, model and hourly machine rates exist, with cancel/top-up controls and custom enterprise terms.
Sources
Open the Capy page
Podiumproduct changeresearch correction48 findings · 18 sources
Findings today
- Podium ships desktop, CLI and browser clients, including phone-browser control.
- Podium launches the native Claude Code, Codex, Grok, OpenCode, Cursor and Pi CLIs in persistent terminals on…
- Podium supports native coding-agent logins and managed provider credentials.
- Docs describe a first-run flow (install, podium, register a Git repository, confirm a detected logged-in harness)…
- The podium CLI covers issue create, show, update, claim, dependencies, artifacts, session send/status/read/stop and…
- Podium gives agents its own issue tools over CLI and MCP, and agent profiles import and export Claude Code agent files.
- Desktop releases use a Tauri 2 shell that serves the Podium web UI; mobile source uses Expo and React Native.
- Podium issue records are native and authoritative with stable references, CLI creation and editing, and agent-driven…
- Issue brief, acceptance criteria, state paragraph and todos persist on the durable issue record.
- Podium supports persistent parent and child issues, phases and typed dependency links, including reparenting an…
- v0.3.0 routes Podium issue instructions and relay environment through terminal and engine session launch.
- Not established.
- Podium exposes native issue creation with an optional start flag, separate dispatch, editing, comments, labels,…
- CLI and MCP address the same canonical issue records for reads, creation, edits, claims, state, dependencies and…
- The spec CLI and service (living specs under pspec with stable SP IDs) are in v0.3.0.
- Docs and release notes describe many sessions running as independent terminals, one worktree per issue, and several…
- Issues carry an assignee, claim sets assignee and in_progress, a coordinator session can be set per issue, sessions…
- Podium orchestrates delegation itself: podium agent spawn starts a full child session on an issue with a chosen…
- The server owns a scheduler for cron and one-time automations that spawn agent sessions, skipping overlaps and not…
- Chat and native CLI views share a session.
- Release 0.3.0 ships a flight deck showing a whole mission in one view: phases, every task and its state, who works…
- A quick task can be an interactive session or an issue; an issue can grow into a mission by gaining children while…
- The published Podium execution choices are local user machines and a user-owned VPS or paired machine.
- Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes…
- Closing a browser tab does not stop the agent process on a running Podium host.
- Only machine setup is documented: the installer installs missing runtime tools and pairs a host, and the state…
- Podium exposes retryable errors, optional auto-continue with backoff, bounded waits and provider quota.
- Podium offers local logs and crash export, structured session status, issue stats, a usage and analytics sheet with…
- Since 0.2.0 Podium shows what each task costs, on the task header and the usage sheet, with per-session rows and…
- Podium reports host memory, load and disk, auto-hibernates idle sessions under pressure, and provides named advisory…
- The issue UI displays owner and visibility read-only and deliberately omits sharing controls.
- Podium defines member/admin instance roles and admin-only membership management.
- Agent-session management requests go through an operator approval broker with approve and deny; the privacy docs say…
- Issue actions, approval steps, comments and mail are recorded server-side.
- Review is a documented loop: issue stage review, diff and checks, artifacts, offers with merge or send-back buttons,…
- The durable issue, session transcript, artifacts and mail persist for any later agent, and a live session can be…
- Artifact commands store immutable server-side copies of issue-linked files, including images, video, HTML and…
- In the experimental Shipping path a configured validation profile runs before landing (default argv bun run test…
- Issues own branches and worktrees, and issue actions rebase, open a pull request with gh (pr create --fill) and…
- The operator accepts work through offers and runs the merge action under a branch merge-lock; in the experimental…
- Shipping orders record approved base and head SHAs, tested integration SHA, landed ref and validation result in a…
- The shipping service records revision-specific approval, configured validation and delivery receipts.
- The public repository is licensed Apache 2.0, and the website presents Podium as an open-source agent development…
- Local desktop and self-hosted installs run on user-controlled machines with a documented state directory.
- Docs state repositories and native harness credentials stay on machines you control and server state lives in a…
- No Podium price is published: podium.do/pricing returns 404 and the docs list billing as not implemented.
- Podium is pre-1.0.
- Podium is open-source Apache-2.0 software, and the download page calls it free and open source.
Sources
Open the Podium page
Archived event links
Something wrong or missing?