Factorize hosts jobs for your coding agents. Connect your agent → create a job → run it → inspect the result → automate it.
Start at app.factorize.sh. Sign up with email and password, verify email, and connect an execution account in Settings → Integrations. You supply execution, repository/model access and any provider accounts; Factorize hosts job configuration, triggers, queues and run history.
Connect a supported remote MCP client to:
https://app.factorize.sh/mcp
Follow Connect your agent for Codex/Claude Code configuration and browser consent. Then ask:
Show me my available execution integrations. Create a manual job called ‘Review recent changes’ using my repository’s target. Have it clone REPOSITORY_URL, review the latest commit and summarize any problems. Run it once and report the result.
The conversational agent calls list_execution_configs, checks existing jobs, creates a job, invokes it with a stable idempotency key, and reads get_run until completion. Current exe.dev targets select an account/agent, not a repository: put the repository URL in the prompt. Browser-only signup, integration credentials, resource selection and consent are separate from MCP job management.
Read Your first job, safe editing and configuration replacement, and stop/retry behavior. Add schedules, Linear, GitHub, ClickUp, or job chaining after a successful manual run.
MCP provides selected scoped operations, not every REST capability. REST contracts remain available in OpenAPI and authentication reference. Credential management and trace replay require an interactive owner session. Agents can use the generated llms.txt and llms-full.txt.
Use Node 24.12.0 and npm 11.19.0 (.node-version and package.json), then run npm ci, npm run dev, and npm test. The root test is the complete required validation used by CI; npm run check is an alias, and npm run test:backend / npm run test:browser are the focused shared lanes. The Worker lives in packages/api, React frontend in packages/app, and generated public contract in packages/api-client. Frontend calls documented /api/v1 routes. Keep local secrets in ignored packages/api/.dev.vars.
On exe.dev, use the Factorize validation runner image, then run npm ci and npm run test:local after checkout. The image supplies the pinned Node, npm, PostgreSQL authentication, Playwright Chromium, and browser OS dependencies; test:local resets only the local validation database, applies migrations, and runs the complete root suite. The bootstrap refuses remote database URLs. To prepare the database without running tests, use npm run bootstrap:test and export its three printed variables before npm test. Missing prerequisites must be fixed in the image and published as a new digest; do not repair a fresh VM by hand or mark work done after only git diff --check.
Run npm run generate --workspace=factorize-docs after guide edits and npm run validate --workspace=factorize-docs before publishing. See docs publishing and package migration for development and release gates.
Hosted users do not deploy Factorize. To operate your own instance, follow deployment, configuration, and operations. These contain Cloudflare/Worker, Postmark, provider OAuth registration, webhook infrastructure and secret setup.