Agentic AI Comparison:
Cleric vs project-mariner

Cleric - AI toolvsproject-mariner logo (listing unavailable)

Introduction

Cleric investigates production alerts and changes, explains likely causes and can open fix pull requests for an engineer to approve. Project Mariner was Google’s experimental browser agent. Google states that it shut down on May 4, 2026. Ratings are subjective editorial opinions, not measured benchmarks.

Overview

project-mariner

Project Mariner was Google’s experimental browser agent. Google states that it shut down on May 4, 2026.

Cleric

Cleric investigates production alerts and changes, explains likely causes and can open fix pull requests for an engineer to approve.

Editorial ratings · 1–10, higher is better

These scores express our judgement of the cited product facts. They are not measured performance benchmarks. Each product is assessed for its stated purpose; a higher score does not make different workflows interchangeable.

Evidence gaps lower confidence and affect the relevant judgement. Unknown pricing does not mean free access. Research prototypes and retired products retain their historical scope, with adoption ratings reflecting current access.

Ratings assessed: 2026-10-20. Source verification dates may differ.

Documented capability: How useful and complete is the documented workflow for the product's stated purpose?

  • 1–2: No usable current workflow established, or only an unsupported promise.
  • 3–4: Historical, experimental or very limited workflow; substantial delivery gaps.
  • 5–6: Concrete but narrow workflow, or promising research requiring specialist review.
  • 7–8: Substantial documented end-to-end workflow with useful controls or customization.
  • 9–10: Exceptionally complete documented scope and controls; reserve 10 for unusually strong evidence.

Ease of adoption: Can the intended user obtain and set up a usable product today?

  • 1–2: Discontinued, unavailable, waitlisted, or no usable deployment path verified.
  • 3–4: Archived software, restricted research/preorder access or uncertain current service access.
  • 5–6: Developer-managed setup, significant configuration or sales-led implementation.
  • 7–8: Active accessible product with manageable setup for its intended user.
  • 9–10: Straightforward self-service access and setup, with unusually few adoption obstacles.

Value and cost clarity: How attractive and understandable is the cost model for the documented use?

  • 1–2: No current purchasable or usable offer; historical prices cannot support a purchase.
  • 3–4: Material price, entitlement, license or availability uncertainty limits budgeting.
  • 5–6: Plausible value with custom pricing, significant setup costs or incomplete selected-plan terms.
  • 7–8: Useful scope with clear entry pricing/allowances or accessible source, while accounting for running costs.
  • 9–10: Exceptionally accessible and clear cost model for substantial useful scope; never assume free compute.

Integration options: How useful and extensible are the verified user-facing connections for the intended workflow?

  • 1–2: No current user-facing connection verified, or former connections are unavailable.
  • 3–4: Inputs/exports or one focused connection; internal dependencies are not native connectors.
  • 5–6: Useful API, configurable tools or several relevant connections, with limited verified breadth.
  • 7–8: Broad relevant connections or an extensible documented API/MCP/tool ecosystem.
  • 9–10: Extensive documented ecosystem with multiple connection mechanisms and strong task relevance.

Metrics Comparison

Documented capability

Cleric: 8/10

Evidence confidence: high

Investigation, change verification and proposed fixes support the on-call workflow, with read-only defaults and explicit write permissions.

project-mariner: 7/10

Evidence confidence: high

The historical prototype observed pages and carried out requested browser steps under oversight.

Scores judge each product within its stated purpose, not interchangeability.

Ease of adoption

Cleric: 6/10

Evidence confidence: high

Teams must connect operational tools and agree permissions; an evaluation follows approval.

project-mariner: 1/10

Evidence confidence: high

The original service has shut down.

Match the access and setup requirements to your team.

Value and cost clarity

Cleric: 7/10

Evidence confidence: high

Team is $700/month for 1,400 credits, Pro $1,500 for 3,000 and Scale $3,000 for 6,000. Charges vary by investigation, change and chat usage.

project-mariner: 1/10

Evidence confidence: high

Former access plans are not a current purchase offer.

Budget for the complete workflow, including usage and implementation.

Integration options

Cleric: 9/10

Evidence confidence: high

A broad catalog covers observability, cloud, code, paging and collaboration, with HTTP MCP for internal tools.

project-mariner: 1/10

Evidence confidence: high

Original browser connections are retired; Gemini Spark is a separate product.

Select connections that support your actual workflow.

Conclusions

Choose Cleric for production investigations and change verification under engineering oversight. Project Mariner is historical context and cannot be adopted as a current service.

All AI Agents
Clericproject-mariner (listing unavailable)
Try the real workflow

The best framework is the one you can keep current and afford to run.

Run OpenClaw or Hermes with saved memory, one-click runtime updates, and your choice of Platform Credits, provider keys, or supported subscriptions.

Runs without your laptopBrowser + messaging appsCredits, keys, or subscriptionsMemory survives restarts

Plans start at $199/month. Cancel anytime.

Hosted agent

OpenClaw or Hermes

saved state
Browser
WhatsApp
Telegram
Slack
“I checked the inbox, handled the routine messages, and sent you the one question that needs a decision.”
Create an AI worker that keeps running after this tab closes.
Open Agent Teams