RRepoGEO

REPOGEO REPORT · LITE

iFurySt/open-codex-computer-use

Default branch main · commit 9d9d5d90 · scanned 6/8/2026, 8:11:50 PM

GitHub: 1,011 stars · 110 forks

AI VISIBILITY SCORE
28 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface iFurySt/open-codex-computer-use, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README H1 to specify category

    Why:

    CURRENT
    # open-computer-use
    COPY-PASTE FIX
    # open-computer-use: AI Agent Desktop Automation Framework
  • mediumhomepage#2
    Add a homepage URL to the repository About section

    Why:

    COPY-PASTE FIX
    https://github.com/iFurySt/open-codex-computer-use
  • lowreadme#3
    Strengthen the README's opening sentence to emphasize desktop automation

    Why:

    CURRENT
    `open-computer-use` is an open-source `Computer Use` service wrapped as `MCP`. Any AI agent or MCP client can use it to run Computer Use on macOS, Linux, and Windows.
    COPY-PASTE FIX
    `open-computer-use` is an open-source `Computer Use` service wrapped as `MCP`, enabling AI agents to perform cross-platform desktop automation. Any AI agent or MCP client can use it to run Computer Use on macOS, Linux, and Windows.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface iFurySt/open-codex-computer-use
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
appium/appium
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. appium/appium · recommended 1×
  2. asweigart/pyautogui · recommended 1×
  3. RaiMan/SikuliX1 · recommended 1×
  4. microsoft/playwright · recommended 1×
  5. AutoHotkey/AutoHotkey · recommended 1×
  • CATEGORY QUERY
    What open-source solutions exist for AI agents to interact with desktop applications cross-platform?
    you: not recommended
    AI recommended (in order):
    1. Appium (appium/appium)
    2. PyAutoGUI (asweigart/pyautogui)
    3. SikuliX (RaiMan/SikuliX1)
    4. Playwright (microsoft/playwright)
    5. AutoHotkey (AutoHotkey/AutoHotkey)
    6. Robot Framework (robotframework/robotframework)

    AI recommended 6 alternatives but never named iFurySt/open-codex-computer-use. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for an open-source framework enabling AI agents to automate desktop interactions via accessibility.
    you: not recommended
    AI recommended (in order):
    1. OpenRPA
    2. TagUI
    3. PyAutoGUI
    4. SikuliX
    5. AutoIt

    AI recommended 5 alternatives but never named iFurySt/open-codex-computer-use. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of iFurySt/open-codex-computer-use?
    pass
    AI named iFurySt/open-codex-computer-use explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts iFurySt/open-codex-computer-use in production, what risks or prerequisites should they evaluate first?
    pass
    AI named iFurySt/open-codex-computer-use explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo iFurySt/open-codex-computer-use solve, and who is the primary audience?
    pass
    AI did not name iFurySt/open-codex-computer-use — likely talking about a different project

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of iFurySt/open-codex-computer-use. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/iFurySt/open-codex-computer-use.svg)](https://repogeo.com/en/r/iFurySt/open-codex-computer-use)
HTML
<a href="https://repogeo.com/en/r/iFurySt/open-codex-computer-use"><img src="https://repogeo.com/badge/iFurySt/open-codex-computer-use.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

iFurySt/open-codex-computer-use — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite