Owner action: directory and newsletter submissions

[aaronlab]

This tracks directory/newsletter submissions that require the owner's email, browser session, contact-form identity, or personal account.

Current priority: do these after the X single-post launch in #9. Directory and newsletter submissions are useful, but they are lower intent than owner-channel posts that reach Browser Use users directly.

Do not ask for stars, votes, backlinks, reciprocal placement, or artificial engagement. Submit once per target and ask for developer-tool/editorial feedback.

Fastest owner email actions

Use the short owner email packet first:

• docs/launch/owner-email-send-packet.md

Send from the owner's email account:

1. AgDex: agdex.ai@gmail.com
2. console.dev: hello@console.dev

After sending, record the sent note or any reply so Codex can log metrics and monitor follow-up.

Current Browser Use-first pitch

BrowserTrace is an MIT-licensed local debugger for Browser Use failures. It records screenshots, URLs, actions, model I/O, status, errors, and exports public-safe HTML traces.

The live demo replays a concrete Browser Use local HTML upload navigation failure: the run tries to upload file:///tmp/browsertrace-report.html, but the page navigates to the local file path and the upload preview never appears.

Stagehand, Skyvern, Playwright + LLM, and custom computer-use workflows are secondary integrations.

Repo: https://github.com/aaronlab/browsertrace
Live demo: https://aaronlab.github.io/browsertrace/
Browser Use guide: https://aaronlab.github.io/browsertrace/browser-use-debugging.html
Failure patterns: https://aaronlab.github.io/browsertrace/browser-agent-failure-patterns.html
PyPI: https://pypi.org/project/browsertrace/
Release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.18
Public-safe demo export: https://github.com/aaronlab/browsertrace/releases/download/v0.1.18/browsertrace-demo-public.html

Prepared docs

• Owner email packet: docs/launch/owner-email-send-packet.md
• Directory submission sheet: docs/launch/directory-submission-sheet.md
• Outreach targets: docs/launch/outreach-targets.md
• Day 3 targeted packet: docs/launch/day-3-targeted-communities-packet.md
• AgDex email draft: docs/launch/directory-submission-sheet.md -> ## AgDex Email Draft
• console.dev email draft: docs/launch/directory-submission-sheet.md -> ## console.dev Email Draft

Try-it commands if an editor asks how to run it

uvx --from "browsertrace[ui]" browsertrace doctor
uvx --from "browsertrace[ui]" browsertrace demo
uvx --from "browsertrace[ui]" browsertrace list
uvx --from "browsertrace[ui]" browsertrace

Persistent install:

pip install "browsertrace[ui]"
browsertrace doctor
browsertrace demo
browsertrace

Then open http://127.0.0.1:3000 and click demo: Browser Use local HTML upload navigation failure.

Browser-form directory checklist

Use these only after the owner-channel posts or first two owner emails:

• 4agent.dev: https://4agent.dev/submit (owner browser submission; use Observability or Browser category)
• AgentKart: https://www.agentkart.ai/submit (owner account likely required; skip if it only accepts autonomous agents)
• OSS AI Hub: https://ossaihub.com/submit (login required)
• FOSSHUNTER: https://fosshunter.com/submit (login required)
• AgentsTide: https://agentstide.com/ (owner email/contact route)
• BuilderAI Tools: https://builderai.tools/submit (owner email and Cloudflare Turnstile required)

Use later-pass directories from docs/launch/directory-submission-sheet.md only if the higher-intent posts and emails have already been handled.

Follow-up checklist

• Send AgDex email from owner email
• Send console.dev email from owner email/account
• Send Codex the sent note or reply
• Add one metrics row after each sent email, submission URL, or meaningful reply
• Convert useful replies into docs, issues, or release follow-ups

Stop rules

• Do not submit repeatedly to the same target.
• Do not pretend BrowserTrace is an autonomous agent marketplace listing; frame it as Browser Use failure debugging and agent developer tooling.
• Do not use paid sponsorship unless the owner explicitly decides to spend money.
• Do not ask for stars, votes, backlinks, or reciprocal placement.

[aaronlab]

Update 2026-05-09: directory/newsletter submissions can now point to stack-specific pages instead of only the repo.

Recommended submission links:

• Primary homepage/live demo: https://aaronlab.github.io/browsertrace/
• Browser Use guide: https://aaronlab.github.io/browsertrace/browser-use-debugging.html
• Stagehand guide: https://aaronlab.github.io/browsertrace/stagehand-debugging.html
• Skyvern guide: https://aaronlab.github.io/browsertrace/skyvern-debugging.html
• Playwright + LLM guide: https://aaronlab.github.io/browsertrace/playwright-llm-debugging.html
• Release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.6

Short positioning: local flight recorder for AI browser agents. It records screenshots, URLs, actions, model input/output, status, and errors, then exports a standalone HTML trace with optional redaction.

[aaronlab]

Update 2026-05-09: I added a dedicated directory/newsletter submission sheet for v0.1.7.

Sheet:
https://aaronlab.github.io/browsertrace/launch/directory-submission-sheet.md

Source path:
docs/launch/directory-submission-sheet.md

Use it as the owner submission queue. It includes canonical links, one-line pitch, short description, Product Hunt draft, directory pitch, and tracking command. Owner-only channels still need to be submitted from your personal account/email.

[aaronlab]

Historical note (2026-05-11): this earlier launch update is superseded by the PyPI release v0.1.16.
Current quick trial path: uvx --from "browsertrace[ui]" browsertrace doctor, uvx --from "browsertrace[ui]" browsertrace demo, then uvx --from "browsertrace[ui]" browsertrace.
Persistent install: pip install "browsertrace[ui]". Current release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.16.

Update 2026-05-09: directory/newsletter submissions should now point to v0.1.10.

Release:
https://github.com/aaronlab/browsertrace/releases/tag/v0.1.10

Submission sheet:
https://aaronlab.github.io/browsertrace/launch/directory-submission-sheet.md

Short pitch update: BrowserTrace is a local flight recorder for AI browser agents. The current release includes browsertrace demo for first-run onboarding and browsertrace export --public for public-safe trace sharing. Ask for developer workflow feedback, not stars, votes, or reposts.

[aaronlab]

Historical note (2026-05-11): this earlier asset/update points to an older release.
Current public-safe demo export: https://github.com/aaronlab/browsertrace/releases/download/v0.1.16/browsertrace-demo-public.html.

Directory/newsletter submissions can now include the public-safe demo export as proof that BrowserTrace can share traces without exposing prompts, model output, screenshots, or URLs:

https://github.com/aaronlab/browsertrace/releases/download/v0.1.10/browsertrace-demo-public.html

Use this link after the live demo when a target asks for a downloadable or privacy-safe artifact.

[aaronlab]

Directory queue refreshed with additional current targets:

• OSS AI Hub: https://ossaihub.com/submit
• FOSSHUNTER: https://fosshunter.com/submit
• AgentsTide: https://agentstide.com/
• BuilderAI Tools: https://builderai.tools/submit

Updated docs:

• docs/launch/directory-submission-sheet.md
• docs/launch/outreach-targets.md

I intentionally did not add ToolHunter because the submit URL checked as 404.

Use the existing directory pitch and submit only once per target. Do not ask for votes, stars, swaps, or artificial engagement.

[aaronlab]

Submitted agentfirst.directory directory PR:

• Add BrowserTrace to browser interaction tools bradvin/agentfirst.directory#30

This is framed narrowly as an AI browser-agent failure timeline debugger and includes a note in the PR body that the maintainer can reject it if they consider it adjacent devtooling rather than agent-first browser tooling.

Local validation in the target repo:

• npm test -> 28 passed
• npm run validate:content -> Content validation passed for 13 categories and 24 tools
• git diff --check -> clean

BrowserTrace tracking docs updated in docs/launch/directory-submission-sheet.md, docs/launch/outreach-targets.md, and metrics log.

[aaronlab]

Directory submission monitoring update (2026-05-10):

• bradvin/agentfirst.directory#30: OPEN, mergeable.
• The enrichment workflow feedback was already handled on the PR branch.
• Current reported check: Enrich Tool Assets passed.
• Latest PR comment records local verification: submitter sync, asset enrichment, npm test (28 passed), content validation, and git diff --check.

No additional follow-up is needed unless the directory maintainer asks for changes.

[aaronlab]

Directory blocker audit update (2026-05-10):

I checked the current non-GitHub directory submission routes that were still marked as Maybe in the launch queue:

• AgentKart: sign-in button is present; the static submit form has no usable submit handler from the fetched page, so treat it as owner-account required.
• OSS AI Hub: submit flow requires login before submitting tools.
• AgentsTide: visible public route exposes contact email only; use the owner-email directory pitch if you want to submit there.
• BuilderAI Tools: form is high-fit (AI Observability & Evaluation) but requires owner email plus Cloudflare Turnstile.

Tracking docs updated and pushed in dcb4006:

• docs/launch/directory-submission-sheet.md
• docs/launch/outreach-targets.md
• docs/launch/metrics-log.md

Verification:

• RED confirmed for the new metadata test before the docs were updated.
• Targeted metadata test: 1 passed.
• Full metadata suite: 214 passed.
• Full local suite: 296 passed.
• Remote CI run 25627965783: success.
• Remote Pages run 25627965756: success.

No maintainer follow-up is needed for existing external PRs right now; they remain open/mergeable with no new review feedback.

[aaronlab]

Directory route audit update (2026-05-10):

Checked the remaining Maybe directory routes:

• Agent Hub (https://agent-hub.dev/): homepage and /agents/ route return HTTP 200, but no visible submit, contact, GitHub, mailto, form, issue, or suggestion route was found in the fetched HTML. Treat as blocked unless a public submission route appears later.
• AgDex (https://agdex.ai/): contact page says tool submissions are accepted by email with tool name, website URL, category, and short description. Use the owner-email directory pitch and send to agdex.ai@gmail.com.

Tracking docs updated:

• docs/launch/directory-submission-sheet.md
• docs/launch/outreach-targets.md

No automatic directory submission was made; AgDex should be sent from the owner's email, and Agent Hub has no public route to use.

[aaronlab]

AgDex owner-email draft is now prepared in the submission sheet.

Source:

• docs/launch/directory-submission-sheet.md -> ## AgDex Email Draft

Use from the owner's email account only:

• To: agdex.ai@gmail.com
• Subject: Tool submission: BrowserTrace
• Includes the fields AgDex asks for: tool name, website URL, category, and short description.
• The draft also includes repo, public-safe demo export, and comparison links.

Commit: 3a9bf8d docs: add agdex email submission draft
Verification for that commit:

• Targeted AgDex template test passed.
• tests/test_metadata.py -> 221 passed.
• Full local suite -> 304 passed.
• Remote CI and Pages -> success.

[aaronlab]

console.dev owner-email draft is also prepared in the submission sheet.

Source:

• docs/launch/directory-submission-sheet.md -> ## console.dev Email Draft

Use from the owner email/account only:

• To: hello@console.dev
• Subject: Devtools suggestion: BrowserTrace
• Frames BrowserTrace as an MIT-licensed local debugger for AI browser-agent runs.
• Includes the live demo, repo, comparison page, and public-safe demo export.
• Explicitly says this is not a sponsored review request.

No stars, votes, backlinks, or reciprocal placement are requested; the ask is only editorial consideration for a relevant developer tool.

[aaronlab]

Directory owner-action refresh (2026-05-10): the submission sheet and short owner checklists now include the second-pass browser-form directory queue.

Use docs/launch/directory-submission-sheet.md for exact links and link order.

Ready owner actions:

• AgentKart: try the submit form from the owner login; the unauthenticated form is visible but has no static action/method.
• OSS AI Hub: submit from the browser JavaScript page; use repo, live demo, and public-safe export links.
• FOSSHUNTER: submit once from the owner account and wait for review.
• AgentsTide: use the visible Submit Free Listing path, with hello@agentstide.com as the owner-email fallback.
• BuilderAI Tools: use the Submit Tool for Review form; category AI Observability & Evaluation.

Recent tracking commits:

• e38c1ca clarified AgentKart owner submission path.
• 918eee2 unblocked AgentsTide directory submission.
• c8db1f1 updated BuilderAI submission path.
• b25f325 clarified OSS AI Hub submission path.
• 32bba7a surfaced the second-pass directory queue in the short owner checklists.

Do not ask for stars, votes, backlinks, reposts, or reciprocal placement. Submit once per target and send the submitted URLs or email-sent notes back to Codex for metrics and follow-up tracking.