Files

T

Build: Production / build (push) Failing after 12m39s

Details

fix(skills): pull upstream skill runtime resolution to stop event-loop starvation

The fork's listRuntimeSkillEntries rematerialized every skill's files from
the DB on every heartbeat run dispatch — fs.rm + fs.mkdir + per-file
readFile/writeFile, sequentially per skill. With 24 configured skills and
5 concurrent agents, this saturated the Node event loop badly enough that
executeRun continuations couldn't reach activeRunExecutions.add() within
the orphan-reaper's 5-min threshold, causing reaper to false-positive runs
as "process_lost".

Upstream's listRuntimeSkillEntries calls resolveRuntimeSkillSource, which
checks if the materialized directory already exists on disk and short-
circuits when it does. Fixes the symptom at the root.

Replaces these files with upstream/master content:
  - server/src/services/company-skills.ts
  - server/src/services/heartbeat.ts
  - server/src/services/workspace-runtime.ts
  - server/src/services/company-portability.ts
  - server/src/routes/company-skills.ts
  - server/src/routes/agents.ts
  - packages/adapter-utils/src/server-utils.ts

Pulls in supporting upstream files:
  - server/src/services/catalog-provenance.ts
  - server/src/services/skills-catalog.ts
  - server/src/services/github-fetch.ts
  - server/src/services/portable-path.ts
  - packages/skills-catalog/ (new package)
  - packages/db document_annotation_* schema + migration 0091
  - packages/shared document-annotation types/validators

Drops fork features (to be re-evaluated later):
  - Gitea/Forgejo git skill sources (server/src/services/git-source.ts deleted)
  - PAT support for private skill repos
  - Fork-specific secret-export portability extensions

Adds agentId: null to acquireRunLease test-probe call in routes/agents.ts
to satisfy the fork's environment-runtime agentId requirement (kept).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-29 09:26:51 -04:00

5.0 KiB

Raw Blame History

name, description, key, recommendedForRoles, tags

name

description

key

recommendedForRoles

Agent Browser

Use a controlled browser to verify behavior, capture evidence, or extract information from web pages that a static fetch cannot reach (SPAs, login-gated pages, dynamic content). This skill is about supervised verification, not unattended scraping.

When to use

You need a screenshot of a deployed page or a local dev server to confirm a UI change.
You need to read JavaScript-rendered content that curl/wget will not see.
A user reports a UI bug and you need to reproduce it interactively to capture console errors, network requests, or layout state.
You need to walk through a short flow (load page, click, observe) to verify acceptance criteria.

When not to use

The page is reachable as static HTML. Use curl/HTTP fetch — it is cheaper, faster, and more reliable.
The task is unattended large-scale scraping. That belongs to a dedicated scraper with rate limits, robots.txt handling, and a real user agent policy — not this skill.
The site is behind authentication you do not own credentials for, or whose terms of service prohibit automation.
The site involves sensitive accounts (banking, healthcare, government) where automation risks lockout or compliance issues.

Before launching the browser

Confirm the URL and what state should be true after navigation.
Decide what evidence is needed: full-page screenshot, viewport screenshot, console log, network trace, HTML snapshot, extracted text.
Decide the viewport size that matters for the task (mobile vs desktop). Default to a desktop size unless the task is mobile-specific.
For local dev servers, confirm the server is running and the port is what you expect.

Driving the browser

A typical verification session:

Launch with a real-looking user agent when the target is the public internet; an unrealistic UA flags automation traffic.
Set a sane viewport (e.g., 1366×768 desktop, 390×844 iPhone-ish).
Navigate and wait for the right signal. Prefer waiting for a specific selector or network-idle over arbitrary sleeps.
Capture evidence immediately after the wait condition succeeds, before any interaction perturbs the state.
Interact deliberately. One click at a time, with a wait between actions; re-screenshot after each meaningful state change.
Read the console and network panels for unexpected errors, 4xx/5xx responses, or slow requests.
Close the browser cleanly when done. Long-running browser sessions leak memory and hold ports.

What evidence to record

For a verification task, deliver:

A full-page or viewport screenshot of each meaningful state.
The console log, filtered to warnings/errors.
Any non-2xx network response with the URL, status, and a short response body excerpt.
A short narration: "Navigated to X, observed Y, clicked Z, observed W."

For a UI bug repro, also record:

The exact reproduction steps the user can follow.
Viewport size and (where relevant) device pixel ratio.
Whether the bug reproduces on first load vs after interaction.

Prefer programmatic auth (API token, magic link) over UI login.
If UI login is the only path, the user must provide credentials explicitly for this run. Never reuse credentials outside the session.
Do not store credentials in the session log, screenshot, or returned output.

Performance and politeness

Throttle to one navigation per few seconds when touching shared infra.
Respect robots.txt for public sites you are inspecting at any volume.
Cancel navigations if a page exceeds a reasonable timeout (e.g., 30s); the page is broken or rate-limiting you.
Do not retry forever on failure. Retry once with a longer timeout, then escalate.

Common failure modes

Selector not found. Page changed, or you are waiting before render. Take a screenshot to see actual state; adjust the selector.
Click does nothing. The element is offscreen, covered by a modal, or in a shadow DOM. Scroll into view or pierce the shadow root.
Headless detection. Some sites detect headless Chrome and serve a different page. Use a non-headless mode or a fingerprint-realistic configuration only when authorized.
Cross-origin iframe blocking. Iframes you do not own cannot be inspected; the page must offer the data outside the iframe or the task is infeasible.

Anti-patterns

Long unsupervised browser sessions that drift from the original task.
Scraping behind authentication you do not own.
Captioning a screenshot with "looks good" without saying what state was loaded and what selectors confirmed it.
Treating a passing screenshot as proof of correctness across viewports you did not actually test.

5.0 KiB Raw Blame History Unescape Escape