跪拜 Guibai
← All articles
Artificial Intelligence · Programmers

Goldman Sachs Pulls Claude Code From Traders After Four Months of Ungoverned AI Scripts

By 深蓝AI ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

When a 12,000-engineer institution yanks AI coding permissions from traders after a single summer, every company running on loose AI-generated code is on notice: the absence of review, testing, and audit turns productivity into liability. The cheap engineering gates described here cost one afternoon to install, and they're the difference between keeping AI tools and losing them to a blanket ban.

Summary

In July, Goldman Sachs CIO Marco Argenti encouraged non-engineers to vibe code: let AI turn ideas into working tools, then hand them to engineers. By October, the firm had silently revoked traders' access to Claude Code and GitHub's AI coding tools. Bloomberg reported a revised internal policy restricting those tools to engineers after a productivity and risk assessment. The difference between a summer of encouragement and a fall of revocation came down to a missing layer: the code had no review, no tests, no audit, no rollback, yet it ran daily on machines handling client trade data.

That's an engineering problem, not an AI trust problem. A trust chain built from code review, automated tests, static checks, staged rollout, and monitoring/rollback treats any code the same regardless of author. AI code that passes those gates is as safe as human code; human code that skips them is as dangerous as a trader's script. Goldman's internal AI platform has governance built in, but traders were using external tools outside its radius.

The practical path for small teams: put all executable code in version control, install pre-commit hooks with secret scanning (gitleaks, detect-private-key), add semgrep for static analysis, and write down answers to three questions: who uses AI, with what data, under what terms. The comparison table in the piece covers six dimensions from code review to incident response, and the last row, traceability after an incident, is the one that often gets overlooked.

Takeaways
— Goldman Sachs revoked traders' access to Claude Code and GitHub's AI coding tools in October, four months after CIO Marco Argenti publicly encouraged vibe coding.
— The revoked code lacked review, tests, audit, and rollback, yet ran daily on machines handling customer trading data.
— Bloomberg reported the October policy change followed a productivity and risk assessment; engineers retained access.
— The article identifies five engineering gates: code review, automated tests, static checks, staged rollout, monitoring and rollback.
— Goldman's internal AI platform has governance controls; the problem was external tools used outside its radius.
— Three questions any firm should answer: who uses AI, with what data, under what terms.
— Replit CEO Amjad Masad stated that AI agents on personal computers pose a systemic security risk to companies and governments.
— Korean investment firms are restricting personal AI and buying enterprise contracts, while acknowledging data leaks are hard to fully avoid.
— Practical steps for small teams: put all code in version control, install pre-commit with secret scanning (gitleaks and detect-private-key), run semgrep with --config=auto.
— The comparison table contrasts ungoverned vibe coding vs governed AI code across review, tests, secrets, runtime, data boundary, and incident response.
Conclusions

The same model that wrote the trader's script hasn't changed; what changed is that the code now runs inside a process with review and tests. That framing makes AI quality a non-issue and governance the only lever firms control.

Static analysis catches patterns that human review and AI alike gloss over: disabled certificate checks, permissive file defaults, shell injection. Because models learn from examples that include these mistakes, rules become a proxy for senior judgment.

Legal enterprise contracts and internal AI platforms both fail when employees prefer newer external tools; the time gap between governance updates and model releases is where risk accumulates.

Goldman's role as Anthropic's IPO underwriter while restricting Claude Code shows that security policy and business interests can run on separate tracks without contradiction.

Concepts & terms
vibe coding
A practice where non-engineers use AI to generate working code without fully understanding it, often outside standard development processes.
pre-commit hook
A Git hook that runs automated checks before each commit, catching issues like secrets committed to a repository.
gitleaks
An open-source scanner that finds secrets (tokens, passwords, private keys) in Git commit history.
semgrep
An open-source static analysis tool that runs configurable rulesets to detect security and code-quality bugs.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗