FORGE · the coworker platform

Build the coworker the work demands.

Give it a job and a budget. When it hits something it cannot do, it specifies the missing tool, has Codex build it, verifies it, asks your permission, and finishes the job. Then it keeps that tool forever.

Open the demo View pricing

Every assignment leaves two things behind: finished work, and a more capable coworker.

forge · assignment

Work complete

Scripted

Assignment contract

Fix annual checkout · Zendesk #4821

·Diagnose annual plan checkout
·Measure who else is affected
·Open PR + brief the owner

Zendesk read

ConnectionActive

GitHub PR

ConnectionActive

Log analysis

SkillActive

PR authoring

WorkflowActive

Artifact

Pull request + owner brief

Ready

Ready · 3 artifacts

Built to work with systems you already run

OpenAI
Codex
Composio
Octen
Zendesk
GitHub
Slack

How it works

Four beats. One coworker that gets more capable.

Every assignment leaves two things behind: finished work, and a more capable coworker.

Give it a job

Hand the coworker a contract: objective, deliverables, constraints, and a spend ceiling. It plans against real tools — not a chat transcript that evaporates when you close the tab.

Contracts define done before work starts
Estimated range, maximum authorised, live spend
Definition of done is machine-checkable

It builds what's missing

When the plan needs a tool it does not have, the coworker specifies the capability, has Codex build it in an isolated foundry, runs verification gates, and asks permission before install.

Missing tools become dashed tiles — visible, not hidden
Tests count up from real gates, not a spinner
Approved tools stay on the belt forever

It leaves real work behind

Every assignment leaves artifacts with provenance: reports, pull requests, briefs, receipts. Refresh the page — the work is still there, versioned, and attributable.

Declared artifacts appear before content arrives
Metrics tick as evidence lands
Receipts reconcile spend to the integer ledger

You stay in control

Approvals, budgets, and rollback are first-class. External writes require the payload you approved. Nothing spends past the ceiling you set.

Human gates on capability install and outbound write
Per-assignment and monthly credit ceilings
Honest degrade when an integration is not configured

Put a coworker on the job.

Open the demo assignment and watch a missing tool get specified, built, verified, and kept — then finish the work.

Open the demo View pricing