Redirect broken pages that still have backlinks
Leta uses Ahrefs to find dead pages other sites still link to, and Codex redirects each one with a clear match on a new branch.
With Letaido's Codex integration, an AI agent turns SEO data, Linear issues and approved copy into coding tasks for Codex when you ask.
Redirects, titles, landing pages and renames, built on a branch. Open one to watch it run.
Leta uses Ahrefs to find dead pages other sites still link to, and Codex redirects each one with a clear match on a new branch.
Leta finds pages with many Google impressions but few clicks, and Codex rewrites their title tags and meta descriptions on a new branch.
Codex builds a new landing page from the approved copy in a Google Doc, and Leta opens a draft pull request for review.
Codex builds the site change described in a Linear issue on a new branch, and Leta comments on the issue with what changed.
Codex replaces an old product name across your site's pages and components on a new branch, and lists every file it changed.
Five ways to hand Codex a coding task, and who each one suits.
| Option | Start a task in plain words | Reads marketing data for the task | Works without a local repo | Runs while your laptop is off |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | |
| Codex app, CLI and IDE extension | Yes | Partly | Partly | Partly |
| Codex Cloud | Yes | Partly | Yes | Yes |
| Codex in Slack and Linear | Yes | Partly | Yes | Yes |
| Codex GitHub Action and SDK | Partly | Partly | Partly | Partly |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | Leta collects the input from your other apps, writes Codex a brief and reports back in the chat once Codex is done. | Marketers turning Ahrefs, Search Console, Linear or Google Docs input into site changes. | No event trigger, so each job begins in a chat. Codex reaches your site's code through a GitHub connection. |
| Codex app, CLI and IDE extension | Sign in with ChatGPT or an API key, then describe the change. Codex inspects the code on your machine, makes edits and runs tools. MCP servers and plugins add outside data. | Developers working in a checked out repo. | Needs a ChatGPT sign in or an OpenAI API key. Desktop scheduled tasks that use local files need the computer on and the app running. |
| Codex Cloud | Tasks run in a cloud environment with a repo from your connected GitHub or GitLab account, and keep working while your computer sleeps. | Longer coding tasks you review and turn into a pull request later. | Needs ChatGPT sign in. Repo work needs a connected GitHub or GitLab account and an environment for it. |
| Codex in Slack and Linear | Mention @ChatGPT in Slack, or assign a Linear issue to Codex. Repo work runs as a Codex Cloud task and the result comes back to the thread. | Teams that already file website requests in Slack or Linear. | Codex in Linear needs a paid ChatGPT plan. In Slack, an admin sets up the app and a shared cloud environment. |
| Codex GitHub Action and SDK | A GitHub workflow runs Codex on a GitHub runner on repo events with a saved prompt, or your developers control Codex from their own code. | Engineering teams building Codex into CI or internal tools. | The Action needs an OpenAI API key as a repository secret. An SDK program keeps running without your laptop only on a server or runner you host. |
Connect Codex once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
A Codex job begins with your request in a chat.
Nothing to link: no OpenAI key, no ChatGPT plan. Optionally choose which model Codex uses.
A GitHub token or the GitHub App gives Codex access to check out your site and push branches.
Say what should change. Leta collects the data and writes Codex a brief.
Allow all read operations once per app; approve each kind of write once.
5 actions to open a Codex session, give it tasks and collect the answer.
Add Codex from the apps list in Letaido. No key is involved, because Codex runs inside Letaido. Choose a default model if you want one, and connect GitHub so Codex has your site's code.
No. Codex in Letaido uses Letaido's AI access, and what it uses is billed with the rest of Leta's work.
On its own, Codex can add outside data through MCP servers and plugins. Letaido is not an MCP server. Inside Letaido, Codex calls Letaido's own connectors and asks you through the usual approval cards.
Yes. A task can run anywhere from a few minutes to a few hours. Carry on with other work, and Leta writes in the chat once Codex finishes.
Every job here ends with a pushed branch or a draft pull request. None of them merges. Look over what Codex proposes in GitHub first.
Codex Cloud runs coding tasks in OpenAI's cloud with your ChatGPT sign in, and repo work needs an environment set up for it. With Letaido, one request gets Leta to read Ahrefs, Search Console or Linear first, so Codex starts with the right data.
Allow all read operations once per app; approve each kind of write once.
Connect Codex, then ask for a job like "Add 301 redirects for our dead pages that still have backlinks". Leta gets it done the moment you ask.
Get LetaidoOpen a Codex session on your Letaido server, hand it a task in plain words, or close it.
See which sessions are busy or idle, and fetch the complete reply to a finished task.