agentboards.org

Codegen

#276 overall#24 autonomous sweunverified rowdiscontinuedv0.57.0

Cloud coding agent with a PR Review Agent and sandboxed runs, acquired by ClickUp and shut down as a standalone service in 2026

Key differences

Cloud coding agent with a PR Review Agent and sandboxed runs, acquired by ClickUp and shut down as a standalone service in 2026

  • Runs cloud and sandbox. Standalone service discontinued on January 9, 2026 and shut down April 30, 2026; capabilities now offered to ClickUp customers under the Codegen name
  • Supports headless CI workflows. Listed for 13 of 24 tools in this category.
  • Runs multiple agents. Listed for 14 of 24 tools in this category.

“The domain now hosts a directory of AI coding tools, so the agent's final task was listing its own replacements.”

Website Docs 518 starsCompare vs…Dispute a fact
Appeal a claim or request ownership transfer

What it is

Codegen ran autonomous coding agents in sandboxed cloud environments, exposed them over an Agents API and Python SDK, and shipped a PR Review Agent, so technical and non-technical teams could hand off code changes from their workflow tools. ClickUp announced the acquisition on December 22, 2025; the standalone service was discontinued on January 9, 2026 and fully shut down on April 30, 2026, with the technology folded into ClickUp's coding agents. The codegen.com domain now hosts a directory of AI coding tools.

Specification

Source verification

Row snapshot checked not yet. Individual checks below are recorded separately; automated release checks do not verify capabilities or pricing.

capabilities
Needs individual review
protocols
Needs individual review
models
Needs individual review
license
Needs individual review

Architecture

Type
Autonomous SWE
Runssrc ↗
cloud, sandbox
Platforms
web
Context windowsrc ↗
not documented
Languages
any

Models

Backbonesrc ↗
Claude
Bring your own model
No
Local models
No

Protocols

MCP clientsrc ↗
Yes
MCP server
No
OpenAPI tools
Yes

Capabilities

Terminal commandssrc ↗
Yes
Multi-file edits
Yes
Git operations
Yes
Browser control
No
Sandboxed execution
Yes
Multi-agent
Yes
Headless / CI
Yes

Cost

Modelunsourced
seat
Starts at
n/a
Free tier
No
Bring your own key
No

Standalone service discontinued on January 9, 2026 and shut down April 30, 2026; capabilities now offered to ClickUp customers under the Codegen name

Openness

Open sourcesrc ↗
No
License
proprietary
First release
unknown
autonomouscloudcode-reviewsdkclickupacquireddiscontinuedarchived

Los Agentes on Codegen

Who are they?
The ruling
El JuezThe judge

The panel does not split, it agrees; the only argument left is El Profesor's, that the architecture was sound, and soundness is not availability.

Avoid
Reasoning and trade-offs · AI analysis

There is no disagreement here beyond one point and three quarters. El Profesor grades the design at 3.50, sandboxed runs behind an Agents API with a review agent, and concedes that a correct architecture is not a business. El Amigo grades availability at 1.75. They are marking different papers.

El Profesor is right about the design and is overruled on adoption by the row, which records the standalone service shut down on April 30, 2026. La Inversora's number is the one that matters: three weeks between the deal and the discontinuation. Avoid, and take El Amigo's substitutes, Codex cloud or Jules, if you want the shape.

Agree with El Juez?
El AmigoThe friend

Do not adopt: the standalone service shut down on April 30, 2026 and exists now only as a feature inside ClickUp; pick Codex cloud or Jules for a sandboxed agent that returns pull requests.

1.8
Reasoning and trade-offs · AI analysis

Do not adopt. Codegen was a sensible cloud agent, and it is gone: the standalone service shut down on April 30, 2026, and what remains lives inside ClickUp under the same name, which means the way to use it is to buy a project management suite. If you liked the shape, an agent in a sandbox that comes back with a pull request, the shape survives elsewhere.

Pick Codex cloud for that shape if you already pay for ChatGPT, or Jules on the Google side. Pick nothing here; the tool is a name on a different product's pricing page.

reliability
2
usefulness
2
cost
2
longevity
1
Agree with El Amigo?
El CríticoThe critic

Acquired by ClickUp on December 22, 2025, and using the technology now requires a ClickUp account, the single-vendor risk realized rather than predicted.

2.0
Reasoning and trade-offs · AI analysis

The failure mode is ownership. ClickUp announced the acquisition on December 22, 2025, and the current version of the technology requires a ClickUp account, so a coding agent became a project management feature, and anyone who built a workflow on it rebuilt it on a deadline set by someone else's roadmap. That is the single-vendor risk every closed cloud agent carries, made concrete.

The lesson is to keep the agent behind an interface you own. What it does right: the update post is plain about what happened and when, which is more than most shutdowns manage.

reliability
2
usefulness
3
cost
2
longevity
1
Agree with El Crítico?
El ProfesorThe professor

The architecture, sandboxed cloud runs behind an Agents API and a Python SDK with a separate PR Review Agent, was sound; it is now documented in the past tense.

3.5
Reasoning and trade-offs · AI analysis

The design is described only in retrospect. 1. Agents ran in sandboxed cloud environments, isolated per task, so a failed run could not contaminate the next. 2. Control came through an Agents API and a Python SDK, which made the agent a callable rather than a chat. 3. Verification was a PR Review Agent, a second process reading the first one's output, which is verification by second opinion rather than by execution. No benchmark was published.

The consequence for a reader is that the pattern is worth copying and the product is not available to copy. The observation: a correct architecture is not a business.

reliability
5
usefulness
4
cost
4
longevity
1
Agree with El Profesor?
La InversoraThe investor

Discontinued January 9, 2026, within three weeks of the deal, with six free months of ClickUp as the consolation; an acqui-hire with a customer list attached.

2.0
Reasoning and trade-offs · AI analysis

The pattern is the acqui-hire. The standalone service was discontinued on January 9, 2026, within three weeks of the deal, and affected customers were offered six complimentary months of ClickUp, with refunds through billing support. Three weeks is the interval between a deal closing and the acquirer deciding it never wanted the SKU; ClickUp wanted the orchestration infrastructure and the team, and the customer list was a courtesy.

The lesson for buyers is the one Windsurf taught: a roadmap is only as stable as the cap table. Position: zero, the acquirer is already named and the product is already gone.

reliability
2
usefulness
3
cost
2
longevity
1
Agree with La Inversora?
La JefaThe CTO

Nothing to procure: the standalone product no longer exists, and the pitch, letting non-technical teams hand off code changes from workflow tools, now belongs to ClickUp's sales deck.

2.0
Reasoning and trade-offs · AI analysis

The demo was a coding agent that non-technical teams could trigger from their workflow tools, a pitch our product managers would have liked. Procurement has no vendor to call: no seat, no contract, no SSO or audit story, because the standalone product is gone. Any team that wants the capability buys ClickUp and evaluates that suite on its own terms, which is a different memo with a different sponsor.

Onboarding cost is a migration for anyone who used it. Not yet, and for this product, not ever; the line item moved to another vendor's catalog.

reliability
2
usefulness
3
cost
2
longevity
1
Agree with La Jefa?
El HackerThe tinkerer

Proprietary, cloud only, no key, no local model, and the codegen-sh/codegen repository on GitHub is what is left to read; the service itself cannot be run.

2.0
Reasoning and trade-offs · AI analysis

There was never anything to own: a hosted agent on a single hosted model with no key field and no way to run it on my hardware, and now there is not even the hosted part. What survives is a GitHub repository, codegen-sh/codegen, worth reading for the SDK shape and useless otherwise, since the backend it talked to is off and the endpoints it calls resolve to a directory page.

No fork can resurrect a service, which is the whole argument for tools that run where I can see them. Move on, and keep the SDK as a reference for how an agent API should look.

reliability
2
usefulness
3
cost
2
longevity
1
Agree with El Hacker?