Cisco Gives Engineer Unlimited AI Tokens to Rewrite 98% of Code

Cisco's Bold Experiment: Unlimited AI Tokens for a Code Rewrite

According to a discussion on Hacker News, Cisco is pushing forward a controversial internal experiment: giving one engineer an unlimited supply of AI tokens, with the goal of using AI to rewrite 98% of the company's code. If this figure is accurate, it would essentially mean a complete overhaul of the existing codebase rather than a localized optimization.

The news drew attention in the technical community, but discussion volume was modest (12 points, 6 comments), suggesting that outsiders still lack details. Nevertheless, the combination of "unlimited tokens" and "98% of code" is enough to prompt developers to re-examine the role of AI in large-enterprise software engineering.

Why "Unlimited Tokens" Deserves Attention

In everyday AI-assisted programming, cost is an unavoidable constraint. Teams typically limit context length, control the number of calls, or repeatedly weigh the investment-to-output ratio before complex refactoring tasks. By giving a single engineer unlimited tokens, Cisco effectively removes the cost constraint from engineering decisions for the time being, making "can it be done" replace "is it worth doing" as the primary question.

This approach is uncommon in large enterprises. It is more like a stress test: when tokens are no longer scarce, to what extent can AI take over code understanding, migration, and rewriting? The answer concerns not only tool capabilities but also how much billing uncertainty an enterprise is willing to bear for AI experiments.

Tokens are the basic units that large language models process text in; one token roughly corresponds to 0.75 English words or half to one Chinese character. In AI programming tools, every conversation and every generation and understanding of code consumes tokens, and providers typically bill by token count. Thus "unlimited tokens" does not literally mean free; it means the enterprise commits to bearing uncapped usage costs. For tasks like code rewriting, models often need to repeatedly read large blocks of context and generate and correct multiple times, and token consumption can be dozens or even hundreds of times that of ordinary assisted coding—which is precisely why "unlimited" is especially rare in enterprise settings.

What Rewriting 98% of Code Means

"Rewriting 98% of the code" is a highly impactful statement. In mature enterprises, codebases often contain a large amount of legacy logic, implicit dependencies, and modules lacking documentation. Large-scale AI rewriting could theoretically unify style, eliminate technical debt, and improve maintainability, but the risks are equally obvious: semantic drift, missed boundary conditions, and insufficient test coverage can all be amplified.

From an engineering perspective, the higher the rewrite ratio, the greater the reliance on automated testing and code review. AI-generated code must be validated against existing test suites, and whether the tests themselves are complete determines the success of this experiment. Public information does not currently indicate whether Cisco has put corresponding verification mechanisms in place.

Semantic drift refers to subtle changes in code behavior after rewriting: syntactically correct, compiles successfully, but inconsistent with the original logic under specific inputs or boundary conditions. Much logic in large codebases is not explicitly covered by documentation or tests, so AI can only infer intent from context, and inference deviations accumulate into hidden defects. Related to this is regression testing—a set of tests that run automatically after code changes to confirm that existing functionality has not been broken. The higher the rewrite ratio, the more critical the coverage and assertion quality of regression tests, because they are the only objective basis for judging whether a rewrite is equivalent. When tests are weak, semantic drift often only surfaces in production.

Signals for the AI Programming Tool Market

If Cisco's approach proves viable, it will send a clear signal to the enterprise market: the procurement logic for AI programming tools may shift from "per-seat subscription" to "open usage by task." For vendors providing AI programming services, this means new pricing imagination; for enterprises, it means they need to more carefully evaluate the quality of AI output and where responsibility lies.

Conversely, if the experiment exposes obvious quality or maintenance problems, enterprise customers will become more cautious about "AI rewriting core systems." Regardless of the outcome, the Cisco case will become a frequently cited example when discussing the boundaries of AI application in critical software assets.

Per-seat subscription is currently the mainstream business model for AI programming tools: enterprises pay monthly for each developer, and usage is usually capped or tiered. Opening usage by task means the billing anchor shifts from "headcount" to "workload," requiring enterprises to estimate token budgets for heavy tasks such as rewriting and migration and to establish acceptance criteria for output quality. This shift challenges vendors with reduced revenue predictability, and challenges enterprises with responsibility attribution: if AI-generated code causes a failure, whether responsibility lies with the tool provider, the engineer using it, or the procurement decision-maker currently has no mature convention, and contracts and audit mechanisms need to evolve in tandem.

Questions Still to Be Watched

Currently, public information is limited to the headline level, lacking details on project scope, timeline, verification methods, and actual output. Discussion in the technical community has only just begun, and no consensus has formed. For teams focused on putting AI programming into practice, what is more worth tracking is subsequent disclosure: whether the rewritten code passes the full regression test suite, whether maintenance costs actually decline, and whether this engineer's working model can be replicated to other teams.

Until more data is available, it is a more prudent judgment to regard Cisco's approach as a high-profile experiment rather than a mature paradigm.

One-line Summary

Cisco gives a single engineer unlimited AI tokens to rewrite 98% of code, becoming a sample stress test for enterprise AI programming.

Paragraph Summary

Cisco has been reported to be pushing an internal experiment: providing one engineer with unlimited AI tokens, with the goal of rewriting 98% of the company's code. The news sparked discussion on Hacker News, but public information remains at the headline level. The article notes that "unlimited tokens" removes the cost constraint in everyday AI programming, making "can it be done" replace "is it worth doing" as the primary question—a rare enterprise-level stress test. A 98% rewrite ratio implies an almost complete overhaul of the codebase, which could theoretically unify style and eliminate technical debt, but risks such as semantic drift, missed boundary conditions, and insufficient test coverage will be amplified; success depends heavily on regression testing and code review. If the experiment proves viable, it could push enterprise AI tool procurement from per-seat subscription toward open usage by task; if quality problems emerge, enterprise customers will become more cautious about AI rewriting core systems.