Skip to content
SYBERLABS

04 / Job application workspace

RelayEarly release

Every application has a history.

A workspace for job seekers who draft with AI assistants, with one record per job and human approval of the exact wording.

Relay works alongside ChatGPT, Codex, Claude, Grok and your notes in Notion or Obsidian. Each job keeps its research, confirmed facts and draft versions in one history. Acceptance applies to the exact wording of a specific draft version, and Relay never submits an employer form.

View sourceIntegration setup

Why

Why a record, not another assistant.

People already hunt for jobs with ChatGPT, Claude, Grok, Notion and Obsidian. The work falls apart in the gaps: a new chat forgets the last draft, a tracker overwrites a decision, an interview note resets an application’s status.

Relay is the record that remembers. Research keeps its history, acceptance belongs to the text, and every handoff is bound to a job and a version so stale work is rejected instead of silently replacing a newer review.

Use

How a job moves through Relay

Fictional example records ship with the app; no real applicant data is included.

  1. 01 / Import

    Bring the research

    Add a job from a title and posting URL, pull a public Greenhouse or Lever board, map a tracker CSV, or import notes from Notion or Obsidian. Matching URLs join the same record.

  2. 02 / Facts

    Confirm what is true

    A reusable candidate fact ledger that you confirm. Agent drafts are checked against it for selected claim patterns; unsupported claims are flagged, not silently passed.

  3. 03 / Draft

    Hand off to your assistant

    Export a packet, let ChatGPT, Codex or Claude draft, and bring a version-bound draft back. Where the browser supports WebMCP, an assistant can stage a draft directly for review.

  4. 04 / Accept

    Approve the exact words

    Acceptance records approval of one draft version. Change the text and it needs review again.

  5. 05 / Send and record

    You press submit

    A human Inspect Accept arms a first-party Chrome extension to fill a form once. Relay does not POST the employer form, and outcomes are recorded with a receipt.

Four screens from a local build.

Captured on 2026-10-05 from relay@0000605 built and run locally with its own migrations and the mocked local sign-in. Every company, role and fact shown is a fictional example record; no real applicant data.

  • Relay Runtime with the fictional Northstar Example — Backend Engineer job selected: review queue on the left, exact answers and attachments panels, and a disabled Approve & send control.
    Runtime with a fictional example job selected. Approve & send stays disabled until an agent prepares the application. Fictional example records, local build of relay@0000605, 2026-10-05.
  • Relay draft review for the same fictional job: Save draft and Accept exact draft controls with the note that acceptance records approval of these exact words and nothing is sent.
    Exact acceptance. Accepting records approval of one draft version’s wording; changed wording needs fresh acceptance and nothing is sent. Fictional example records, local build of relay@0000605, 2026-10-05.
  • Relay Tracker listing three fictional jobs by status, with a notice that two imported applications arrived without a receipt and are excluded from reply rates.
    Tracker. Three fictional jobs by status; imported submissions without a receipt stay visible but are excluded from reply rates. Fictional example records, local build of relay@0000605, 2026-10-05.
  • Relay profile page, the candidate fact ledger, showing two confirmed fictional facts available for agent citations and a resume extraction box.
    The fact ledger. Two fictional facts confirmed by the user and available for agent citations; Relay records the confirmation and does not verify facts itself. Fictional example records, local build of relay@0000605, 2026-10-05.

Inspect

What leaves Relay, and what comes back.

Recorded by running the repository’s own modules: the bounded packet, the returned draft, the identity and version gate, the claim gate, and the five refusals that leave nothing written.

This map needs JavaScript. It replays a recorded handoff: a posting canonicalised to one job, a bounded packet handed to an assistant, the returned draft re-validated, one claim flagged, and acceptance refused while a blocker is open.

Design

How it is built

  • One history per job

    Posting observations are preserved as rows; rediscovery keeps an existing interview or submitted status instead of resetting it.

  • Version-bound handoffs

    Draft packets and editor checks carry the job identity and generation-time version, and reject stale work.

  • Claim checks

    Word and number overlap between a draft and cited confirmed facts. The check is heuristic and says so: it does not establish factual truth.

  • Edge deployment

    TypeScript and React on Cloudflare Workers with Drizzle ORM, a Manifest V3 extension, and Playwright tests.

Evidence

  • Tested

    The domain, handoff and profile modules were executed under Node for the site’s recorded Relay map; the D1 acceptance write is reproduced as a rule.

  • Implemented

    Runtime, Tracker, the fact ledger, CSV and job-board import, and every integration listed in the repository.

  • Not yet

    No public deployment and no customer counts, hiring outcomes or throughput improvements are claimed. Autonomous hunting is not included.

Reflects SyberLabs/relay@0000605 · verified 2026-10-05. Each state is earned by code, a named test, a measurement under stated conditions, or a deployment; none is promoted by wording.

Facts

Status
Early release
Built by
Seth Carlson and Mateo Robles
Technology
TypeScript, React, Vinext, Cloudflare Workers, D1, Drizzle ORM, Chrome extension (Manifest V3), Playwright
Boundary
Relay prepares and tracks application materials. It does not submit employer forms, host an MCP connection, or sync accounts in the background.

Other projects

All work