Add Jev Social

[IRONICBo]

Summary

Adds Jev Social to Browser Automation as an agent-native local application.

Jev is a material actor in the product: it repeatedly chooses one bounded operation from targets observed in prior browser results, while socai executes that operation in the user's Chrome and returns evidence to the next decision step. Without that loop, the project becomes direct manual CLI use.

The record cites pinned first-party evidence for the decision surface, setup and interfaces, one clearly bounded real-run report, and the MIT license. It also states the browser/login/OpenRouter dependencies and makes no independent performance claim.

Disclosure: I maintain Jev Social.

Validation

• npm run validate:content
• npm test — 71/71 passed
• git diff --check
• all six listing and evidence URLs returned HTTP 200 on 2026-09-21

[github-actions]

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '4b562e82b4658af437094edd2ec1f26403ceb5eb'
git worktree add --detach '../agentfirst-base-70' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-70' --submitted-by 'IRONICBo' --slug 'jev-social'
npm run enrich:tool-assets -- --write --slug 'jev-social'
git worktree remove '../agentfirst-base-70'

Then commit the updated files to this PR branch.

[foo-bender]

Outcome: meets-policy

The listing passes the inclusion test. Jev Social is agent-native: Jev repeatedly chooses a bounded, typed social-browser operation from targets returned by prior results; socai executes it in the user's Chrome and feeds evidence back into the next decision. Target validation, attempted-operation removal, bounded finish behavior, partial-result handling, and evidence reporting are substantive agent behavior rather than generic browser compatibility. Browser Automation fits, and no duplicate was found on current main.

First-party evidence checked: the pinned README, pinned src/actions.js, pinned example report, pinned MIT license, product site, and canonical repository. These establish the Jev/socai decision loop, supported Instagram/TikTok/LinkedIn read operations, Node/OpenRouter/browser requirements, bounded 63.969-second example as one run rather than a benchmark, and MIT licensing. All submitted first-party URLs and the social image returned HTTP 200.

Checks actually run on this exact head in an isolated tree with Node 24.8.0: npm run validate:content passed; npm test passed. Current GitHub enrich check is successful.

Uncertainty: no independent end-to-end accuracy, speed, live-site compatibility, or access-gate benchmark was performed.

@bradvin This meets the current policy; the inclusion decision is yours.

Policy baseline: main 24ffc2c; README blob 464791e741200498ace6ba7f46c866d868b6bd9c.

[github-actions]

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '4b562e82b4658af437094edd2ec1f26403ceb5eb'
git worktree add --detach '../agentfirst-base-70' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-70' --submitted-by 'IRONICBo' --slug 'jev-social'
npm run enrich:tool-assets -- --write --slug 'jev-social'
git worktree remove '../agentfirst-base-70'

Then commit the updated files to this PR branch.

[foo-bender]

Outcome: changes-requested

@IRONICBo Jev Social otherwise passes the inclusion test: Jev repeatedly selects bounded operations from observed targets, socai executes them in Chrome, and results feed the next decision. That is substantive agent-native behaviour rather than generic compatibility. Browser Automation fits, and I found no duplicate on current main.

Please make these specific corrections:

• In tools/jev-social.md, remove “and replies” from the final agent-outcome bullet, or add pinned first-party evidence that Jev Social actually captures reply text. The cited README and src/actions.js document comments, not replies; the cited example report explicitly says no comment or reply text was captured in that run.
• Replace or omit the optional logoUrl. The submitted Google favicon URL currently ends at an HTTP 404 fallback; the project's first-party https://socai-io.github.io/jev-social/favicon.svg returns HTTP 200.

First-party evidence checked individually:

• Pinned README: https://github.com/socai-io/jev-social/blob/699c04890a7930827f8dfa2ba9eef6378c7b5fdf/README.md — validates the Jev/socai loop, interfaces, platforms, setup, bounded operations, and partial-result handling.
• Pinned actions: https://github.com/socai-io/jev-social/blob/699c04890a7930827f8dfa2ba9eef6378c7b5fdf/src/actions.js — validates observed-target construction, capability filtering, attempted-operation removal, and bounded finish.
• Pinned report: https://github.com/socai-io/jev-social/blob/699c04890a7930827f8dfa2ba9eef6378c7b5fdf/docs/example-report.md — validates four source rows, explicit limitations, and 63.969 seconds as one recorded run, not a benchmark.
• Pinned licence: https://github.com/socai-io/jev-social/blob/699c04890a7930827f8dfa2ba9eef6378c7b5fdf/LICENSE — validates MIT licensing and open-source pricing.

All four submitted evidence items are accessible and validated; none require correction or removal. I did not independently reproduce the live browser run, accuracy, speed, or access-gate behaviour.

Checks on merge a8faa2b7a72d1f090772367d85f0ffbf86349e82 (current main + this head), using Node 24.8.0: npm ci, npm run validate:content (16 categories, 45 tools), all 80 tests, and git diff --check passed. GitHub's current enrich check is successful.

Policy baseline: main 958e3d3; README blob 9cd199e9c9bada982eefde1f56267e14301efa9f.

[IRONICBo]

Addressed both requested corrections in 549462d:

• removed the unsupported reply-text claim; the listing now limits that capability to profiles, posts, and comments
• replaced the failing Google favicon URL with the first-party favicon.svg URL

The current enrich check passes.

[foo-bender]

Outcome: meets-policy

Policy assessment

Jev Social passes as agent-native browser research software. Jev repeatedly selects one bounded operation from platform capabilities and targets observed in prior results; socai executes it in the user's Chrome and returns evidence to the loop. Source validates target checks, attempted-operation removal, a bounded finish action, partial results at access gates, and evidence reporting. Browser Interaction fits, the limitations avoid unattended/bypass claims, MIT licensing is verified, and no duplicate was found. @bradvin for the inclusion decision.

Evidence checked

Validated all four pinned first-party sources: the repository README for setup, platforms, decision loop and limits; src/actions.js for observed-target construction and bounded operations; the example report for one explicitly non-comparative 63.969-second run and evidence limits; and the MIT LICENSE.

Checks run

• Reviewed the body, complete diff, listing, classification, category, duplicate search, current head/checks, licence, limitations, and all submitted evidence items. GitHub enrich is successful.
• Exact final head merged with current main af5b0fc05df21cf7cff658bd64be4d01ae2b5648 in an isolated worktree, Node 24.19.0: npm run validate:content passed; npm test passed 84/84.

Reviewer-owned SEO metadata
Tool path: tools/jev-social.md

• agentSummary — written: "Jev Social is for local social research where an agent should choose the next bounded browser operation from observed results. Jev selects supported read-only searches and page inspections, while socai executes them in the user's Chrome and returns evidence to the loop. Runs preserve operation history and can finish with partial results when access is blocked." Grounded in the pinned README, action source, and example report.
• seoTitle — written: "Jev Social: Browser-Grounded Social Research Agent". It states the validated agent role and grounding.
• seoDescription — written: "Inspect how Jev Social chooses bounded Instagram, TikTok, and LinkedIn research steps, runs them through socai in Chrome, and preserves evidence." Grounded in the pinned repository evidence.

Reviewer commit: 0458007e3b61dffdd970718f8793febfdde95f95 — IRONICBo@0458007. The existing description was preserved byte-for-byte.