---
schema_version: 7
rubric_version: "0.3"
canonical_url: "https://podium.do/compare/agents/jcode-vs-podium/"
data_url: "https://podium.do/compare/agents/jcode-vs-podium/data.json"
generated_at: 2026-11-22
last_checked_at: 2026-11-13
last_cross_checked_at: 2026-11-21
oldest_checked_at: 2026-11-06
publisher: "Podium"
---

# Jcode vs Podium

> Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. Sourced findings follow the same evidence rules for Podium and its competitors. Facts labeled Podium team research come from Podium's own team and have no linked source. None of this removes the conflict of interest.

> Based on data from adecomparison.com by Podium (https://adecomparison.com; source repository https://github.com/madeinorbit/ade-comparison, snapshot 4322f0c of 2026-11-22), used under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Source links and check dates are kept. Podium arranges the findings into pairs, applies its publication checks, and added its own research where marked "Podium team research". Data license terms: https://github.com/madeinorbit/ade-comparison/blob/4322f0c035f303791413639d1462a138443d8c1e/DATA-LICENSE.md

40 criteria sourced for both products; 26 criteria also agent cross-checked for both. 49 criteria with a sourced finding for at least one product. "Sourced" findings passed publication validation. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. Humans approve the rubric, templates and prototype; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent.

Each row gives the finding's status, support, check date and answer. Scope, limitations, atomic answers and sources for every finding are in each product's document, under the criterion ID. Judgment rules are in the rubric.

- Jcode source checks: 2026-11-08 to 2026-11-13. Details: https://podium.do/compare/agents/products/jcode/index.md
- Podium source checks: 2026-11-06. Details: https://podium.do/compare/agents/products/podium/index.md
- Rubric: https://podium.do/compare/agents/rubric/index.md
- Canonical HTML: https://podium.do/compare/agents/jcode-vs-podium/
- Machine-readable JSON: https://podium.do/compare/agents/jcode-vs-podium/data.json
- Methodology: https://podium.do/compare/agents/methodology/

## Access and agent choice

### ACC-01: Client access

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. Jcode provides a terminal UI and product CLI on macOS, Linux and Windows. jcode run is noninteractive, serve starts a persistent daemon and connect attaches clients. Jcode Desktop has a universal macOS DMG (macOS 13+), Linux x86_64 packages with ARM64 when available, and a portable Windows 10/11 ZIP; Linux packages are not repository-signed and the Windows app is not code-signed. The /mobile command moves a session and its swarm to Jcode Cloud and requests a phone-app push; an existing cloud session only requests the notification. The native iPhone client has a public TestFlight beta requiring a Jcode account. No Android release is listed.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium ships desktop, CLI and browser clients, including phone-browser control. The native iPhone app is private beta; the complete download offering contains no native Android app.

### ACC-02: Agent and model choice

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. Jcode is its own coding harness with Claude, OpenAI, Gemini, Copilot and Azure provider logins, local Ollama/LM Studio and named OpenAI-compatible endpoints. Model-provider access does not establish running Claude Code or Codex CLI as its harness. Jcode v0.99.1 implements Antigravity as a Google Cloud Code model-provider transport using an HTTP client and model catalog. This does not establish a separate Antigravity coding-agent session. Jcode supplies its own agent loop. Its provider transports do not run the named third-party coding-agent harnesses.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium launches the native Claude Code, Codex, Grok, OpenCode, Cursor and Pi CLIs in persistent terminals on machines you control. The 0.2.0 release calls Pi fully supported. Models come from each harness catalog, and capabilities differ per harness: Pi declares no quota, handoff or hooks. Mixed-harness operation was not exercised.

### ACC-03: Subscriptions, API keys and vendor credits

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Jcode supports subscription OAuth and direct API providers, Claude subscription login and OpenAI/ChatGPT/Codex login, plus local model servers. /account switches provider accounts.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports native coding-agent logins and managed provider credentials. Claude subscriptions (via native login or a managed setup-token) and local ChatGPT/Codex login are supported paths, alongside Anthropic and OpenAI API keys. Docs list billing and hosted metering as not implemented product claims.

### ACC-04: Onboarding and project prerequisites

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Install the binary, run jcode in the project folder and choose a provider login. Remote Unix hosts can run a persistent daemon reached through SSH socket forwarding.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Docs describe a first-run flow (install, podium, register a Git repository, confirm a detected logged-in harness) and a headless VPS installer with machine joining. Setup time and failure rate were not measured, and no self-serve managed cloud setup is documented. The current README and installation guide use podium.do/download and podium.do/install.sh as the canonical stable entrypoints.

### ACC-05: Programmable access

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The TypeScript SDK launches a private Jcode process or attaches through api-bridge to a local or forwarded remote daemon, with session and streaming operations.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The podium CLI covers issue create, show, update, claim, dependencies, artifacts, session send/status/read/stop and review actions, and the server exposes the same issue commands as a bearer-token MCP tool endpoint. No documented public HTTP API, SDK or webhooks were found.

### ACC-06: External tools and extensions

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Jcode loads global and project MCP configuration and imports Claude Code/Codex MCP servers. Only stdio MCP servers are supported; HTTP/SSE entries are skipped. Markdown skills can load on relevance or explicit invocation.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. Podium gives agents its own issue tools over CLI and MCP, and agent profiles import and export Claude Code agent files. No Podium documentation for user-configured MCP clients, plugins or custom tools was found.

### ACC-07: Client implementation

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Desktop releases use a Tauri 2 shell that serves the Podium web UI; mobile source uses Expo and React Native. A native iPhone release is described as private beta.

## Planning and context

### PLAN-01: Intake and external tracker relationship

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Users start an interactive project session or submit a noninteractive prompt through jcode run. External-tracker intake was not established.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium issue records are native and authoritative with stable references, CLI creation and editing, and agent-driven filing from conversation. The in-product assistant has Linear search, create and move tools when a key is configured, but no import or two-way tracker sync was found.

### PLAN-02: Durable task plans

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Plans consist of phases, lanes and items with names, descriptions, lifecycle status, priority and confidence. Updates target names; generated internal IDs survive plan replacement when names stay the same.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Issue brief, acceptance criteria, state paragraph and todos persist on the durable issue record. Release 0.3.0 removed the separate design and notes fields and appended their text to the brief. On the human issue page the title, description and acceptance are editable and the brief is read-only; agents edit the brief and other fields through issue commands.

### PLAN-03: Hierarchy, dependencies and evolving scope

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Phases are ordered, lanes can run in parallel and items run in lane order. A lane can name earlier prerequisite tasks; cancelled/deleted prerequisites do not satisfy it. Completely blocked is a condition with a reason, separate from lifecycle state.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports persistent parent and child issues, phases and typed dependency links, including reparenting an existing issue without replacing its identity. Since 0.3.0 issue types are task, phase and decision: epic and other kinds are retired, and any issue with children acts as a parent. Dependency types are fixed to blocked-by, related, discovered-from, supersedes and duplicates. Cycles are refused and docs list an open blocker as a reason an issue cannot start. No mandatory workflow preset applies in the baseline.

### PLAN-04: Shared context and memory

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Repository and global AGENTS.md load into the corresponding scope. Jcode also stores memory and skills, with explicit /memory and /skills controls. Memory correctness has not been tested.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. v0.3.0 routes Podium issue instructions and relay environment through terminal and engine session launch. Claude stream sessions use appended instructions and boundary callbacks; Codex server sessions use developer instructions, Grok ACP uses rules, and OpenCode uses the prompt system field. Claude and Codex boundary hooks can re-prime after compaction. Transcript mirroring is on by default; full-text indexing needs the command-palette flag, which defaults off. Agent profiles can carry markdown instructions. Curated memory, skills and memory correction or deletion controls remain unestablished. No instruction-delivery or compaction scenario was run.

### PLAN-05: Architecture and API awareness

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. When one agent edits a file another has read, the server notifies the reader, which can inspect the diff. This does not prove automatic conflict-free integration.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Not established. Podium mirrors daemon transcripts by default, keeps a full-text index only when the command-palette flag is on, and stores session attachments. No repository code search, architecture awareness or API retrieval feature was found.

### PLAN-06: Native issue management and idea backlog

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Native saved todo items have stable internal IDs, names, descriptions, priority, confidence, states and phase/lane membership. They are separate items inside a session plan, not a cross-project issue backlog.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes native issue creation with an optional start flag, separate dispatch, editing, comments, labels, assignment, search, board filters, archive, sibling ordering and an issue tree. Issue records have their own identity separate from sessions and stages are durable. The idea-to-mission scenario was not run. v0.3.0 refuses an agent close or done update while issue sessions are computing unless --confirm-interrupt is supplied; guidance says to request review and close only on user instruction.

### PLAN-07: Agent-native issue operations

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The coordinator owns the shared versioned plan and can propose, approve, assign and control tasks. Workers receive an assigned todo lane rendered before work starts. Other workers cannot freely mutate the shared plan.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. CLI and MCP address the same canonical issue records for reads, creation, edits, claims, state, dependencies and artifacts. Relayed agents have worker capability scoped to their issue subtree, with --outside-scope confirmation for other existing issues. attachSession is not subtree-gated, but direct rehoming from a real issue is refused and an agent attach naming a Proposed target is refused. That does not make every Proposed subtree inert: operator attachment or spawn-time cwd binding can leave a session attached to a Proposed issue; newSubissue without targetId then bypasses the proposed-parent guard, creates a human-audience backlog child and attaches the existing session. This path remains at v0.3.0 source and was not exercised live. Concurrent-edit handling remains unknown.

### PLAN-08: Living product specifications

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The spec CLI and service (living specs under pspec with stable SP IDs) are in v0.3.0. Specs is an experimental, default-off feature listed on the edge channel: the flag controls the Specs UI, the spec line in CLI help and whether agents are told about the spec CLI. The podium spec command itself is dispatched, and the server specs service has no flag check, so direct CLI use does not need the flag. This agrees with the docs, which call specs not baseline rather than blocked. Not run end to end.

## Coordination and automation

### COORD-01: Parallel work

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Multiple agents can work concurrently in the same repository; the server manages messaging, completion status and file-change notifications. Actual concurrency and performance benchmarks were not rerun.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Docs and release notes describe many sessions running as independent terminals, one worktree per issue, and several paired machines under one server, with session and issue state visible on the flight deck, board and CLI. Agent-initiated spawns are limited to 10 per target issue per UTC day. Achieved concurrency is unmeasured.

### COORD-02: Ownership and dispatch

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Only root sessions spawn swarm workers. The root coordinator assigns shared-plan tasks and controls that plan through a single coordinator slot.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Issues carry an assignee, claim sets assignee and in_progress, a coordinator session can be set per issue, sessions have seats, and work can be placed on a chosen machine or agent profile. claim has no exclusivity check of its own, locks are advisory leases and Podium does not serialize agents editing one worktree, so exclusive ownership is not enforced.

### COORD-03: Inspectable delegation and communication

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Jcode agents can autonomously spawn a swarm, making the original agent coordinator. Server-managed messages support direct, repository-wide and server-wide communication and completion status.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium orchestrates delegation itself: podium agent spawn starts a full child session on an issue with a chosen harness, model, effort or agent profile, mail carries messages, and bounded await reports the child result. Children are real sessions shown as seats on the flight deck. Agent-initiated spawns take a daily budget per issue. A complete delegated task with retained child findings was not run.

### COORD-04: Unattended triggers

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Ambient mode is implemented but disabled by default. It runs one proactive background agent, self-schedules wakeups and prioritizes interactive sessions; later design ideas in the document are not all shipped.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The server owns a scheduler for cron and one-time automations that spawn agent sessions, skipping overlaps and not backfilling occurrences more than an hour late. The Automations UI is an edge-visibility feature that defaults off and docs list automations as non-baseline. Agents can subscribe to issue and session events.

### COORD-05: Intervention and attention

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Enter interleaves a message with the working agent and Shift+Enter queues it. Commands can resume, fork, compact or rewind sessions.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Chat and native CLI views share a session. v0.3.0 defaults human controller chat to steer and immediately types it into running Claude Code, Codex, Grok and OpenCode TUIs that declare native busy-input queuing; undeclared harnesses wait for a boundary, and compaction waits. Mail and automation keep when-ready delivery. Stop, resume, questions, decision issues and offers remain available. This is inspected implementation, not a cross-harness runtime parity result.

### COORD-06: Fleet and epic management UI

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Desktop offers a spatial session canvas and zoomed-out overview with task and orchestration views. No six-task navigation fixture or measured effort was run.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Release 0.3.0 ships a flight deck showing a whole mission in one view: phases, every task and its state, who works on what, what is blocked and by what, and proposals. Done work stays visible. The CLI prints the same snapshot. The waterfall source is dormant and the Timeline view was deleted, so per-task timeline history is not shown. The shared 12-task UX scenario has not been run.

### COORD-07: Workflow flexibility and orchestration visibility

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Users start quick prompts, headless requests or swarm sessions, with provider/model/effort and feature configuration.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. A quick task can be an interactive session or an issue; an issue can grow into a mission by gaining children while keeping its identity; no mandatory workflow preset applies in the baseline. Per-agent harness, model and effort are chosen at spawn or through agent profiles, and the deck shows seats. The coordinator-with-two-reviewers scenario was not run.

## Execution and reliability

### RUN-01: Laptop-independent execution

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The daemon owns sessions, tools and provider calls. It can run locally or on a user SSH server, where it continues after disconnect; a local client can forward the remote Unix socket. Detached cloud turns run on the session recorded cloud host and reject a second active owner. /mobile migrates session and swarm to the managed Jcode Cloud host.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The published Podium execution choices are local user machines and a user-owned VPS or paired machine. No vendor-operated agent host is in the complete download offering.

### RUN-02: Workspace and process isolation

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. Swarm coordination supports optional Git worktrees and worktree manager roles for separate code work and later integration. These are checkout boundaries, not hostile-code sandboxes. The optional Jcode Cloud service offers cloud-agent virtual machines.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.

### RUN-03: Recovery, expiry and continuity

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Normal uninstall retains config, authentication, memory and sessions unless purge is requested. A remote daemon keeps working after disconnection and --resume reopens its saved session.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Closing a browser tab does not stop the agent process on a running Podium host. Idle sessions may hibernate under configurable policies; a stopped session keeps its transcript, branch and resume reference. Release 0.2.0 says a failed update rolls back and running sessions keep running through the upgrade; database rollback remains a manual restore. Terminal reattachment goes through the driver adopt contract with process-identity and observation-lease checks. Worker-crash and multi-day behavior were not tested.

### RUN-04: Development environment reliability

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Cloud handoff does not make machines identical. Metadata-only environment requests transfer scoped project files or allowlisted credentials; local callbacks have a limited lifetime and disconnect revokes future access. Copied resources remain until removed or rotated.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Only machine setup is documented: the installer installs missing runtime tools and pairs a host, and the state directory holds server-managed secrets. Dependency caching, services, ports and automatic repair for project environments were not found.

### RUN-05: Limits and failure handling

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. cloud wait exits unsuccessfully on timeout without cancelling the remote turn. Failed inspection and remote-turn failure remain errors; an active owner blocks a detached turn.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes retryable errors, optional auto-continue with backoff, bounded waits and provider quota. Claude stream and hosted headless drivers enforce a supplied turn deadline, with no deadline when timeoutMs is absent. The one-shot headless server runner supplies its budget, default ten minutes. Agent spawns have a daily per-issue budget. Operator-configurable task-wide turn, token and spend caps remain unestablished; quota display is not enforcement.

### RUN-06: Truthful status and operational statistics

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Todo lanes show worker activity, observed tokens, throughput, connection, elapsed time and tool intent. Missing telemetry is not inferred from context size. Waiting/stopped workers show available reasons.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Podium offers local logs and crash export, structured session status, issue stats, a usage and analytics sheet with hourly list-price cost, per-task costs and host load panels. The 0.3.0 notes report a vendor benchmark of about 330 MB server memory against about 1.2 GB for an earlier Podium build, and 8 to 52 percent faster start; the method is published in the repository and was not reproduced here. Usage export and cross-reconnect consistency were not established.

### RUN-07: Per-task API and compute cost

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The /usage and /info commands show provider limits, session information and tokens. Token and quota visibility is not proof of per-task invoiced spend.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Since 0.2.0 Podium shows what each task costs, on the task header and the usage sheet, with per-session rows and descendant rollups. The 0.3.0 deck adds a mission cost chip. Figures are token estimates at public model list prices, not subscription invoices or provider bills.

### RUN-08: Compute-aware scheduling and verification

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Ambient mode admits only one ambient instance and gives interactive sessions priority. Its later design/resource-policy examples are not all implemented; no safe load test was performed.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium reports host memory, load and disk, auto-hibernates idle sessions under pressure, and provides named advisory resource leases. The merge-queue panel was removed; a shipping queue remains behind the Shipping flag. Concurrency limits and bounded test queuing were not established.

## Human collaboration and control

### TEAM-01: Live human collaboration

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The issue UI displays owner and visibility read-only and deliberately omits sharing controls. Backend share handlers and a Members settings section with invites and admin or member roles exist; they do not establish a finished human collaboration workflow. Docs say small teams can share an instance but the interface prioritizes one operator.

### TEAM-02: Roles and access boundaries

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-13 (9 days old); not separately cross-checked. The local daemon pairs devices without human organization roles. The enterprise contact page does not establish roles or SSO for the separate closed hosted service.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium defines member/admin instance roles and admin-only membership management. The released client authentication uses password-backed sessions and paired-device tokens without enterprise SSO.

### TEAM-03: Approvals and temporary access

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Temporary local environment access is scoped to the handoff lease, defaults to twenty-four hours and ends on disconnect/session switch. The credential allowlist excludes arbitrary home files and SSH private keys. This is not a verified general command-approval system.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Agent-session management requests go through an operator approval broker with approve and deny; the privacy docs say lifecycle commands and automation requests may require operator approval. Harness permission prompts appear as a Permission needed state; credential copying during pairing is a per-grant opt-in. Command-level policy enforcement beyond the harness own modes was not established.

### TEAM-04: Decision and activity history

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Plan item identity is preserved through matching-name replacement and explicit rename. Transcript/log integrity and multi-user attribution were not tested.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Issue actions, approval steps, comments and mail are recorded server-side. Issue activity events, including approval steps, are pruned by the server's janitor once they are older than 14 days or fall outside the newest 50,000 rows. That policy does not define all content retention, export or tamper-evident audit guarantees.

### TEAM-05: Review experience and guidance

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-11. Jcode Desktop renders file diffs beside live sessions, and the TUI /diff command cycles the diff display mode. No guided human review measurement was run.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Review is a documented loop: issue stage review, diff and checks, artifacts, offers with merge or send-back buttons, and a Tray of review-ready work. Release 0.3.0 adds quoting text from a reply or review finding into the next message and a full-height reading view with an outline. The board has a key map with a help sheet. Guided-review quality and narrow-screen use were not measured.

### TEAM-06: Colleague takeover and continuity

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The durable issue, session transcript, artifacts and mail persist for any later agent, and a live session can be handed to another machine in an edge feature. Colleague takeover by a second person was not established.

## Verification and delivery

### SHIP-01: Retained artifacts and outputs

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The desktop client renders diffs, Mermaid diagrams, inline images and tool cards beside agent conversations. Persistent revision-bound cross-task artifact retrieval remains unverified.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. Artifact commands store immutable server-side copies of issue-linked files, including images, video, HTML and documents, which render in the issue sidebar and offers and stay readable after the worktree is gone. Each task has an artifacts page grouped into screens, documents and reports, with filters and search. Revision linking remains untested.

### SHIP-02: Verification and spec gates

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. In the experimental Shipping path a configured validation profile runs before landing (default argv bun run test with a 10 minute timeout) and a failed validation holds the order. Lint, type, CI and spec conformance gates and independent review requirements were not found as product-enforced policy.

### SHIP-03: Git and pull request workflow

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. The inspected public Jcode CLI/desktop implementation has no dedicated native PR creation or management operation; agents can use generic shell/MCP tools. The optional closed Jcode Cloud service does not have enough public workflow detail to establish a product-wide PR value.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Issues own branches and worktrees, and issue actions rebase, open a pull request with gh (pr create --fill) and merge, subject to a merge-style setting (ff-only by default, with auto-rebase before merge). Podium does not resolve branch conflicts, and PR review comments and CI response were not established.

### SHIP-04: Merge and deployment authority

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The operator accepts work through offers and runs the merge action under a branch merge-lock; in the experimental Shipping path approval is frozen to an exact head and delivery lands on a local target branch by default. Release and deployment are not product features found in the sources.

### SHIP-05: Completion evidence and rollback

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Shipping orders record approved base and head SHAs, tested integration SHA, landed ref and validation result in a durable delivery receipt, and stale approvals hold the order. Shipping is experimental. The pr action records a PR URL on the issue. Build and deployment links and rollback were not found.

### SHIP-06: Batch review and high-volume shipping

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. The shipping service records revision-specific approval, configured validation and delivery receipts. The Shipping panel is an experimental edge toggle, off by default; the separate Queues panel was removed.

## Ownership, privacy and economics

### OWN-01: Source and license

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. Jcode source is MIT licensed at the pinned revision, including a free-of-charge permission grant. Optional hosted inference/cloud services have separate commercial scope.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The public repository is licensed Apache 2.0, and the website presents Podium as an open-source agent development environment. Hosted extensions and hosted-service terms are not established.

### OWN-02: Hosting and exit

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The Jcode daemon, TUI and tools can run on a user-controlled machine or SSH host, with direct model credentials or local servers. Optional Jcode Cloud is not required for local use.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Local desktop and self-hosted installs run on user-controlled machines with a documented state directory. The docs describe stopped full-state backup and automatic pre-migration database-only snapshots retaining three copies. Those snapshots omit artifacts, transcripts, uploads, configuration and secrets; no portable structured export/import contract was established.

### OWN-03: Data handling and telemetry

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-11. Default usage telemetry may include provider OAuth email, installation ID and numeric/categorical usage. Full transcript sharing is separately opt-in. jcode telemetry disable, JCODE_NO_TELEMETRY=1, DO_NOT_TRACK=1 or a no_telemetry file disables telemetry.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-21. Docs state repositories and native harness credentials stay on machines you control and server state lives in a documented directory. Since 0.2.0 a daily usage report is on by default and can be turned off; crash reports stay opt-in. Usage reports carry an install id, schema version, Podium version, OS, architecture, bucketed install age and machine count, session counts per harness and whether issues were used. Crash reports carry the same install id, versions, OS and architecture, a fixed error type and up to 20 stack frames, each with a Podium source file path, line and function when there is one; error messages and frames outside Podium are dropped. Neither tier sends prompts, transcripts, your code or paths outside the Podium source tree. Model-provider handling is the harness own. Hosted analytics and website analytics are separate paths.

### OWN-04: Price and included usage

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. Optional hosted plans start at USD 10 monthly with USD 20 inference credit and fifty Jcode Cloud machine hours. Extra inference defaults to a zero-dollar cap; paid overage uses provider API prices after raising the cap. Remote Rust builds start at the USD 20 plan. This is separate from free MIT local software. Paid plans allocate Jcode Cloud VM machine hours in proportion to their monthly price.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. No Podium price is published: podium.do/pricing returns 404 and the docs list billing as not implemented. The software is open source and free to download; model and compute costs are the user's own.

### OWN-05: Scenario cost and controls

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

### OWN-06: Availability and support

- **Jcode**: Sourced (sourced); support: partial. Checked 2026-11-08 (14 days old); not separately cross-checked. v1.0.0-preview.199, published November 6, is an opt-in v1 pre-release of experimental binaries, with production use directed to the stable channel. Open issue topics include syntax highlighting, ACP cancellation and compaction refusals, without reproduced universal findings.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium is pre-1.0. Stable v0.3.1 (2026-11-06), an update fix, follows v0.3.0 (2026-11-05), v0.2.0 (2026-10-11) and v0.1.0 (2026-08-21), with edge and dev prerelease channels. Windows and Linux desktop are Experimental, the native iPhone app is in private beta and hosted Podium is unconfirmed. Support runs through GitHub issues, Discord and private vulnerability reporting.

### OWN-07: Enterprise assurance

- **Jcode**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

### OWN-08: Useful free tier and evaluation access

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The application can be downloaded, used and self-hosted as free MIT software. Optional token/cloud plans and Rust-build trials have separate prices and trial conditions.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium is open-source Apache-2.0 software, and the download page calls it free and open source. Download links for macOS, Linux and Windows redirect to GitHub release assets without a login (observed by HTTP requests; not installed). No Podium charge is documented for self-hosting; agent provider usage is separate. The native iPhone app is private beta and hosted access is unconfirmed.

### OWN-09: Pricing transparency

- **Jcode**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-08 (14 days old); agent cross-checked 2026-11-08. The hosted plans disclose recurring USD charges, inference credit, cloud hours, API-price overage and separate build-overage limits. Local application use and model subscriptions remain separate cost routes.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
