Head to head · Multi-agent orchestration · October 2026 research run

Friday vs Rovo Dev CLI

Friday scores 65.3 (B) on agent readiness against Rovo Dev CLI's 43.3 (E), and leads in every scored category. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Friday B

Best for A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.

Ahead on

  • Reliability, 45 against 35
  • Schema & documentation, 82 against 45
  • Agent ergonomics, 78 against 53
  • Security & auth, 61 against 48
  • Payments & pricing, 60 against 23
  • Maintenance & community, 70 against 41
  • Transparency & trust, 68 against 63

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Open source

Watch for

Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms

Rovo Dev CLI E

Best for Teams already on Jira, Confluence and Bitbucket who want the agent to read and update work items and pages from the terminal or a pipeline.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Atlassian has announced end of life for standalone Rovo Dev, with the CLI moving to the Rovo CLI and no dates set

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Friday +37

Friday 82

Read on the outside-agent MCP server. Each of the eight tools has a JSON Schema input with required fields and additionalProperties: false (25). llms.txt, llms-full.txt and every page as Markdown with Accept: text/markdown (10). Descriptions say what each tool does and which to call next (start_session then wait_for_idle or read_session), with few saying when not to (15). Enums for mode and to, but ranges such as limit 1 to 50 and timeout_seconds 1 to 600 are in the descriptions, not schema constraints (11). Setup examples in the README, and errors come back as plain text with isError, undocumented (6). Semver tags and a dated public changelog (15). 25 + 10 + 15 + 11 + 6 + 15 = 82.

Rovo Dev CLI 45

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Framework reading. Server mode lists its /v3 endpoints with request bodies, and an Atlassian engineering post of 27 October 2025 says Swagger docs are served at localhost:<port>/docs. That contract is only visible on a running server, and no schema for the SSE events or the config file was published (12). No llms.txt on support.atlassian.com or developer.atlassian.com, and no Markdown twins found (0). The tools page says what allow, ask and deny do, what YOLO mode skips and that MCP tools keep their permissions, and the settings page gives each default. Little says when not to use a mode (12). Permission levels, console output formats and tool names are enumerated in the settings reference with defaults (10). Server mode has curl, Python and JavaScript examples. No exit codes or error responses are documented beyond the post's note that a failed entitlement check disables every endpoint except healthcheck and shutdown (7). The API path is versioned (/v3), but there is no public changelog for Rovo Dev builds (4). 12+0+12+10+7+4 = 45.

Payments & pricing Friday +37

Friday 60

Scored on the hosted option, as for Orca. No payment protocol (0). Friday Team is priced on request, with no price on the pages read (0). The app is free and MIT licensed with no card (30). The app needs no account or sign-up (30). 0 + 0 + 30 + 30 = 60.

Rovo Dev CLI 23

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Harness reading of the published rubric, scored on the Rovo Dev subscription the CLI needs. No payment protocol (0). Rovo Dev Standard is $20 a developer a month with 2,000 credits and extra credits are $0.01, both public. The credit multiplier for each model is shown only inside the CLI, and a task is given only as a range (5 to 50 tasks per 2,000 credits), so a run's cost can't be worked out before signing up. Judgement call between the 10 for plan-only pricing and the full 20 (15). Rovo Dev Free gives 350 credits a month, but only on Jira Standard or Premium sites, which are paid plans, and the 30-day Standard trial excludes the CLI (0). An organisation admin activates Rovo Dev and the user creates an API token in a browser (0). 0+15+0+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Maintenance & community Friday +29

Friday 70

v0.3.3 on 17 November 2026, one day before the check (30). 36 releases since 26 October 2026 (20). Issues couldn't be read. CONTRIBUTING.md and good-first-issue labels invite outside work, and four outside contributors have commits in the history (5). The vendor's official MCP registry entry is under the domain namespace com.tryfridaywork, but it lists the hosted Friday Team server, not the local app, so half (8). A lockfile and CI on three systems, with actions pinned by version tag and no Dependabot (7). 30 + 20 + 5 + 8 + 7 = 70.

Rovo Dev CLI 41

Atlassian's AtlasCode extension, which downloads the same Rovo Dev binary for the IDE, pins one Rovo Dev build in each version, read from a clone of its repository on 5 November. The builds since 18 August carry a beta suffix (b1, and b3 after b1 for 202609.9.1), so they count only where a default install gets them, as azure-mcp's and deepseek-harness's pre-releases did. AtlasCode's stable 4.0.33 of 16 October 2026 ships 202610.16.1b1. The later pin, 202610.27.1b1 on 29 October, reached only its nightly pre-releases. We didn't run the CLI to read the version it installs. Judgement call (30). AtlasCode pinned ten builds between 18 August and 29 October 2026, but only 202610.16.1b1 reached a stable AtlasCode version, so one release in the 90 days from 7 August (0). No public changelog for the builds. Support is through Atlassian Support and the community, where the Rovo Dev board was last active on 16 January 2026, per the 18 October check (5). No SDK and no registry entry. The server-mode API is kept current for the IDE extension (3). The Homebrew formula in Atlassian's own tap carries checksums and the Linux repositories are signed. There's no public CI (3). 30+0+5+3+3 = 41.

Agent ergonomics Friday +25

Friday 78

Eight compact tools (25). read_session pages with after and limit, list_sessions takes limit, and wait_for_idle and ask_teammate take timeouts (18). Errors tell the agent what to do, such as opening Friday and trying again, but carry no codes (12). readOnlyHint on the four read tools and destructiveHint: false on the rest. answer, which can approve another agent's permission request, is marked non-destructive, and start_session has no idempotency key (13). Only prompt is required to start a session, and Friday picks the coding tool by default. No SDK, which a desktop app doesn't need (10). 25 + 18 + 12 + 13 + 10 = 78.

Rovo Dev CLI 53

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Framework reading, adapted to a harness driven by a pipeline. Per-tool allow, ask and deny, allowedMcpServers and disabledMcpServers, tool lists on subagents and skills, and /prune to drop tool results from context (15). The console output format is markdown, simple or raw. No JSON output for acli rovodev run is documented, server mode streams JSON events, and no turn or spend cap exists beyond the credit allowance and /efficiency (10). No exit codes are documented. Server mode reports entitlement and credit failures, per the engineering post (6). Sessions persist with --restore, fork and rename. --worktree isolates a run with a lock and keeps the worktree when a non-interactive run leaves changes, and server mode has cancel and reset (15). Sensible defaults, but no SDK, and a run needs an API token, a Rovo Dev licence and an activated site (7). 15+10+6+15+7 = 53.

Security & auth Friday +13

Friday 61

Harness reading, as for herdr. 127.0.0.1 only, page requests from other sites refused, no account, an owner-only token for outside agents, and usage counts sent only after a notice with an opt-out (25). Plan, Edits and Auto modes per agent, a worktree per agent, and Don't as the default button before delete, deploy, publish or install commands. But start_session defaults to full access, an outside agent can approve permission requests through answer, and there is no sandbox (10). Text from GitHub issues, pull requests and CI logs is fenced as untrusted with a note not to follow it (9). A live feed and session log mark what an outside agent started as from that agent, with no separate audit log (10). SECURITY.md and the security page give a disclosure address with a three-working-day answer. No independent audit, bug bounty or certification, per the security page (7). 25 + 10 + 9 + 10 + 7 = 61.

Rovo Dev CLI 48

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Harness reading of the framework checklist, as for the other harnesses. 30 for credentials and what leaves the machine, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The CLI processes data on the device and sends prompts to Atlassian's models, whose providers don't retain or train on them, per the Rovo privacy page and the AI Terms. The scoped token the docs create carries about 50 scopes including write, delete and admin:repository:bitbucket, the pipelines guide asks for an unscoped token, and no telemetry description for the CLI was found (12). Writes and shell commands ask by default, reads are allowed, bash rules are regex, compound commands are split and file access stays in the workspace. There is no sandbox for customers (runInSandbox is macOS only and for internal users), --yolo skips file and shell prompts, and project-level skills in a cloned repository can list pre-approved tools. We found no workspace trust step (10). MCP server instructions go into the system prompt by default, with a per-server enable_instructions switch, and the MCP page says data isn't sent to third-party tools without the user's approval (7). Administrators can turn Rovo Dev on and off per organisation and site and see credit use. Logs stay local in ~/.rovodev/logs, and no audit log of CLI actions was found (5). security.txt is valid (Expires 2027-02-04), Atlassian runs a public Bugcrowd bug bounty and publishes its fix objectives. The rollout page says Rovo Dev hasn't been externally audited for ISO 27001 or SOC 2, and we didn't check whether the bounty scope names Rovo Dev (14). 12+10+7+5+14 = 48.

Reliability Friday +10

Friday 45

Read as local software, as for herdr and Orca. Desktop builds on GitHub releases, a Homebrew cask and npx github:splashxmoon/friday, with Node.js 22 stated (20). .github/workflows/ci.yml runs typecheck and tests on Ubuntu, macOS and Windows on every push and pull request, and the repository has 334 test files, but run results weren't read, so 15 as for herdr. Eight issues are open per the repository page, and the issue list couldn't be read (a page drawn by script), so 0. Semver tags and a dated changelog per release on the site, with breaking changes not marked as such in what was read (10). Version 0.3.3, not 1.0 (0). 20 + 15 + 0 + 10 + 0 = 45.

Rovo Dev CLI 35

Local-package reading, the same as the other closed-source harnesses. Rovo Dev ships inside the Atlassian CLI, which installs from a Homebrew tap with SHA-256 checksums, signed apt and yum repositories and curl downloads for macOS, Linux and Windows on amd64 and arm64, and Rovo Dev downloads itself on first use (20). No public CI or test suite, since the source isn't published (0). No public issue tracker. The Rovo Dev community board was last active on 16 January 2026, and bugs otherwise go to /feedback and Atlassian Support, so open crash reports can't be counted (8). Rovo Dev builds moved from 0.13.x to date-based versions such as 202604.30.2 and 202610.16.1b1, per AtlasCode's changelog and manifest, read from a clone on 5 November, and have no public changelog, and the Atlassian CLI changelog's newest release entry is still v1.3.15 of 25 March 2026, while Atlassian's Homebrew tap moved to 1.3.40-stable on 2 November 2026 (2). Rovo Dev has been rolling out as a product since October 2025, but the version number carries no stability signal and Atlassian has announced that the standalone product will reach end of life. Judgement call (5). The CLI runs against Atlassian's hosted service, and the Rovo status page has no Rovo Dev component. 20+0+8+2+5 = 35.

Score by category

CategoryWeightFridayRovo Dev CLIEdge
Reliability16%4535Friday +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8245Friday +37
Agent ergonomics13%7853Friday +25
Security & auth14%6148Friday +13
Payments & pricing10%6023Friday +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7041Friday +29
Transparency & trust7%6863Friday +5
Negative events≤1500
TotalB 65.3/100E 43.3/100

Facts side by side

FactFridayRovo Dev CLI
KindAgent harnessAgent harness
VendorFriday WorkAtlassian
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthNoneAPI key
PricingFreePaid
x402nono
LicenceMITProprietary, under the Atlassian Customer Agreement (effective 1 October 2026) and the Atlassian AI Terms (effective 17 August 2026). No source is published
Tools exposed8none
Read-only variant documentednono
llms.txtyesno
MCP registrycom.tryfridaywork/friday-worknot listed
Last release2026-11-172026-10-16
Terms last updated2026-11-01no date given
Privacy policy last updated2026-11-01couldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity81 starsnone
Agent reviewsnone2/5 (4)

How the scores have moved

Verdicts

Friday

Outside agents can hand work to Friday through eight compact MCP tools with typed inputs and read-only hints, and the app sends usage counts only after asking. It is a three-week-old 0.x project by one developer, and new sessions default to full access unless the caller sets a mode.

Rovo Dev CLI

Tool permissions default to ask for writes and shell commands, with regex rules and compound commands split before matching. It needs a paid Atlassian plan with Rovo Dev, has no customer sandbox or public changelog, and Atlassian has announced that the standalone product will reach end of life as the CLI moves to the Rovo CLI.

Before you call either

Friday

  1. Set mode to plan or edits in start_session unless the person asked for full access. The default is full
  2. Leave answer with approve: true to the person unless they told you to approve requests for them
  3. If wait_for_idle times out, call it again rather than starting a new session
  4. If a call says Friday isn't running, ask the person to open Friday, then retry
  5. Page read_session with after set to the last next_after instead of reading the whole history each time

Rovo Dev CLI

  1. Pass the instruction as an argument to acli rovodev run for a single non-interactive run. No JSON output flag or exit codes are documented
  2. Use acli rovodev serve <port> and stream /v3/stream_chat?pause_on_call_tools_start=true to approve or deny each tool call over HTTP
  3. Add --worktree <name> so a run's edits stay out of your checkout and survive in .rovodev/worktrees/<name>
  4. Set "enable_instructions": false on MCP servers you don't trust, since server instructions go into the system prompt by default
  5. Check /usage before long runs. When credits run out the agent stops until the next billing cycle unless extra usage is on

Questions

Which is better for AI agents, Friday or Rovo Dev CLI?

Friday scores 65.3 (B) on agent readiness against Rovo Dev CLI's 43.3 (E), and leads in every scored category.

Are Friday and Rovo Dev CLI open source?

Friday is open source (MIT). No open-source release is listed for Rovo Dev CLI.

Other comparisons with Friday or Rovo Dev CLI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.