RRepoGEO

REPOGEO REPORT · LITE

langchain-ai/openwork

Default branch main · commit 92719b25 · scanned 5/27/2026, 4:01:31 AM

GitHub: 1,399 stars · 187 forks

AI VISIBILITY SCORE
30 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 fail
Objective metadata checks
AI knows your name
3 / 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 langchain-ai/openwork, 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

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

OVERALL DIRECTION
  • highabout#1
    Add a concise description to the About section

    Why:

    COPY-PASTE FIX
    A desktop interface for building and running deep AI agents with filesystem access, planning, and subagent delegation, built on deepagentsjs.
  • mediumreadme#2
    Enhance the README's main heading to be more descriptive

    Why:

    CURRENT
    # openwork
    COPY-PASTE FIX
    # openwork: A Desktop Interface for Deep AI Agents

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 langchain-ai/openwork
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
electron/electron
Recommended in 5 of 2 queries
COMPETITOR LEADERBOARD
  1. electron/electron · recommended 5×
  2. subprocess · recommended 1×
  3. child_process · recommended 1×
  4. docker/docker-ce · recommended 1×
  5. LangChain.js · recommended 1×
  • CATEGORY QUERY
    How can I give AI agents direct filesystem and shell access from a desktop app?
    you: not recommended
    AI recommended (in order):
    1. subprocess
    2. child_process
    3. Electron (electron/electron)
    4. nodeIntegration (electron/electron)
    5. remote (electron/electron)
    6. ipcMain (electron/electron)
    7. ipcRenderer (electron/electron)
    8. Docker (docker/docker-ce)

    AI recommended 8 alternatives but never named langchain-ai/openwork. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a Node.js framework to build autonomous agents with planning and subagent delegation.
    you: not recommended
    AI recommended (in order):
    1. LangChain.js
    2. LlamaIndex.TS
    3. Agent Protocol
    4. OpenAI Node.js Library
    5. Autogen.js

    AI recommended 5 alternatives but never named langchain-ai/openwork. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    fail

    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 langchain-ai/openwork?
    pass
    AI named langchain-ai/openwork explicitly

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

  • If a team adopts langchain-ai/openwork in production, what risks or prerequisites should they evaluate first?
    pass
    AI named langchain-ai/openwork 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 langchain-ai/openwork solve, and who is the primary audience?
    pass
    AI named langchain-ai/openwork explicitly

    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 langchain-ai/openwork. 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/langchain-ai/openwork.svg)](https://repogeo.com/en/r/langchain-ai/openwork)
HTML
<a href="https://repogeo.com/en/r/langchain-ai/openwork"><img src="https://repogeo.com/badge/langchain-ai/openwork.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

langchain-ai/openwork — 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