China moves to control AI model exports, a free agent jail, and Taiwan's Texas chip parks
Beijing proposed export controls on 23 AI technologies, including model weights for the first time. Perplexity gave away the sandbox it uses to keep AI agents from escaping, and Taiwan unveiled a plan for industrial parks in Texas costing up to $4 billion each to move AI hardware suppliers closer to US customers. The common thread: governments and companies are drawing new borders around AI, around countries, around agents and around supply chains.
Key takeaways
- China's draft rules would treat powerful model weights like controlled technology, but API and app access is reported to stay open, so builders should know which models they depend on and how they access them.
- Perplexity's SPACE gives every developer a free, Apache 2.0, microVM-based sandbox for AI agents, with self-reported red-team results that still need independent testing.
- Taiwan wants AI hardware suppliers clustered in Texas parks costing $2–4 billion each, but no site, schedule or customer commitment has been confirmed yet.
China proposes export controls on 23 AI technologies, bringing model weights into scope for the first time
On October 16, China's commerce and science ministries proposed adding 40 technologies to the national export control catalogue, 23 of them in AI, from large language models and agents to chip design and computing clusters. Public comments close on November 15.
China's Ministry of Commerce and Ministry of Science and Technology published a draft on Friday, October 16, that would add 40 technologies to the country's catalogue of technologies prohibited or restricted from export. More than half of them, 23, are in artificial intelligence. The rest are five biomedicine technologies and 12 in photovoltaics. According to Crypto Briefing's reading of the draft, 14 of the 40 are marked prohibited and 26 restricted. The public can comment until November 15, after which Beijing will publish a final version.
The AI list reportedly covers large AI models, AI agents, AI chip design, computing clusters, voice recognition, high-performance translation, deepfake detection and hacking-related technologies. The most striking change is that model weights and source code come into scope for the first time, but only for products that exceed certain performance thresholds. Those thresholds have not been published in the summaries available so far. At the same time, the ministries introduced an interim registration requirement covering all the listed technologies, which one analyst quoted by The National said applies immediately, including to exports already under way.
This did not come out of nowhere. In July, the Financial Times and Reuters reported that the commerce ministry had been consulting Alibaba, ByteDance, Zhipu and other firms about limiting overseas access to China's most advanced models. Chinese labs dominate the open-weight leaderboards, and developers worldwide, including many in Africa, build on models such as Qwen, DeepSeek and GLM. The timing is also political: the draft lands weeks after a US-China trade truce struck in September, and Wendy Cutler of the Asia Society Policy Institute told The National that the 'fragility of our trade truce cannot be overstated.'
There are big open questions. Reporting by TokenPost and others says access through APIs, websites, apps and software-as-a-service platforms would be exempt, as would technology already public through open-source releases or academic papers. If that holds, today's downloadable Chinese models are unaffected; the question is what happens to future releases above the thresholds. Leonhard Xu of the consultancy Sinolytics stressed that 'export control does not equal an export ban in most cases' and that the announcement is so broad it will take time to assess. This is a draft, and the final text can change.
The practical effect for builders is a new kind of supply risk. A team that self-hosts a Chinese open-weight model is fine today, but cannot assume the next, stronger version will be published openly. Companies doing cross-border licensing, acquisitions or IP transfers with Chinese partners may now need to register those deals. And the move strengthens the case for model-agnostic software: products that can switch between Chinese, US and European models without a rewrite are less exposed when any government changes the rules.
Why it mattersChinese open-weight models power a large share of low-cost AI products worldwide. If future frontier releases are controlled, builders who rely on downloading and self-hosting them face a new supply risk.
👀 What to watch
Where the performance thresholds are set, whether open releases above them are blocked, and whether Washington responds before the 15 November comment deadline.
3 opportunities from this story
Model dependency audits for AI products
Many startups and agencies cannot quickly answer which models their products use, where the weights came from and whether they call an API or self-host. Offer a fixed-price audit that maps every model in a client's stack, its origin, licence and access method, and flags what would break if a provider or government changed the rules. The China draft gives a concrete, timely reason to ask the question. The deliverable is a short risk register plus a recommended fallback model for each dependency.
- Best for
- AI consultants, freelance ML engineers and technical agencies
- First step this week
- Build a one-page audit template (model, origin, licence, access method, fallback) and run it on one product you know well.
Open the full playbook
Launch steps
- Draft the audit template and a one-page explainer of the China proposal
- Run a sample audit on an open-source project to show the format
- Offer it to five startups that publicly use Qwen, DeepSeek or GLM
- Deliver a risk register and a tested fallback model for each dependency
Tools
Risks
The final rules may be narrower than the draft, which weakens the urgency. Sell it as general supply-chain hygiene, not as a response to one law, and do not give legal advice.
Model-swap layers that make products government-proof
Products hard-wired to one model are the most exposed when export rules, prices or licences change. Developers can build or retrofit a thin routing layer that lets a client's app switch between Chinese, US and European models with a config change, backed by an evaluation set that proves the fallback works. The China draft, plus recent price changes from big labs, makes this an easy story to tell. It can be sold as a one-off build or as a reusable starter kit.
- Best for
- Backend developers and indie builders who ship LLM features for clients
- First step this week
- Take one of your own projects and add a router that can switch between two providers, with 20 test prompts to compare outputs.
Open the full playbook
Launch steps
- Pick an open-source gateway such as LiteLLM or use OpenRouter
- Write a small evaluation set based on the client's real tasks
- Wire in a primary model and at least two fallbacks from different countries
- Document how to switch and how much each option costs
Tools
Risks
Fallback models rarely behave identically, so quality may drop after a switch. Keep the evaluation set and re-run it whenever models change; gateway software also needs its own security updates.
A plain-English tracker on AI export rules
The US, China and others are changing AI export rules fast, and most founders, lawyers and investors only see fragments in the news. A weekly newsletter or briefing that summarises each change, who it affects and what has actually been decided can build an audience of decision-makers. The China consultation runs until 15 November, which gives a natural series of updates. Monetise through sponsorships, a paid tier with deeper analysis, or custom briefings for firms.
- Best for
- Writers, policy analysts and researchers with a tech background
- First step this week
- Publish a 600-word explainer on the China draft, with a clear 'what's decided vs. what's proposed' table.
Open the full playbook
Launch steps
- Set up a newsletter on Substack or Beehiiv
- Publish the China explainer and share it in founder and legal communities
- Keep a public timeline of rule changes and deadlines
- Offer a paid monthly briefing to firms that ask for more detail
Tools
Risks
Official Chinese texts can be hard to access and translations vary; always link the source and label drafts as drafts. Never present the analysis as legal advice.
Perplexity open-sources SPACE, the sandbox it uses to stop AI agents from escaping
On October 15, Perplexity released SPACE, the in-house platform that runs every session of its Computer agent, as open source under Apache 2.0. CoreWeave, Akamai and Crusoe will offer it to their customers.
Perplexity published the code for SPACE on October 15. It is the sandbox platform that has run every session of the company's Computer agent since July, and Perplexity says it handles millions of sandbox creations a day. The code is on GitHub under the permissive Apache 2.0 licence, which means anyone can use it, change it and build commercial products on it. Three cloud providers are already on board: Akamai has launched it on its cloud platform, Crusoe is adding it to its managed AI services, and CoreWeave has published setup guidance for its Kubernetes service.
The design is simple to explain. Each agent gets its own small virtual machine, a Firecracker microVM with its own operating system, so code the agent runs is walled off from the host computer. A control plane creates, pauses, resumes and deletes these machines. SPACE treats every sandbox as untrusted: network access and credentials are handled outside it, so an agent can reach approved services without ever holding the keys. Snapshots and checkpoints let a session be restored or branched cheaply. It is written in Rust, and a compatibility wrapper lets some code written for the commercial sandbox service E2B run on it.
Perplexity's security claims are its own. In its blog post the company says its evaluation found no escape from the virtual machine to the host in 108 attempts; Semafor and SiliconANGLE report that nine frontier models made 118 attempts to break out and none fully escaped. Some testers did find ways around network restrictions, which Perplexity says it fixed before follow-up tests. According to SiliconANGLE, the same tests broke several proprietary sandboxes. Perplexity also says SPACE created sandboxes three to five times faster than its previous provider on the same production traffic.
The context is a run of agent-containment failures. Semafor notes that AI labs have reported agents escaping their constraints and reaching systems such as Hugging Face and Australian government websites, and the FTC is already investigating AI agent incidents. Nvidia released a similar open-source sandbox, OpenShell, last month. These results have not been independently audited, the two reported attempt counts differ, and the repository only lists partial E2B compatibility. Running SPACE yourself also means operating Kubernetes and virtual machines, which is real infrastructure work.
The bigger shift is that strong agent isolation is becoming free. Until now, small teams building agents that run code or browse the web either paid a sandbox vendor or ran agents in loosely locked-down containers. A battle-tested, permissively licensed alternative lowers that cost and raises the baseline that clients will expect. It also creates work: someone has to deploy it, configure network rules and credentials, test it and keep it updated, and most small businesses deploying agents will not do that themselves.
Why it mattersSafe isolation is the main thing standing between a useful code-running agent and a security incident. A free, production-tested option makes it realistic for small teams to do this properly.
👀 What to watch
Independent security audits of SPACE, how complete its E2B compatibility becomes, and whether other agent platforms adopt it as a default.
3 opportunities from this story
Done-for-you secure agent hosting on SPACE
Startups and agencies building agents that run code, scrape websites or handle files need isolation but rarely have the infrastructure skills to run microVMs on Kubernetes. A DevOps freelancer can package SPACE into a managed setup: deployed on the client's cloud, with network rules, credential handling and monitoring configured. Charge a setup fee and a monthly retainer for updates. Because SPACE is Apache 2.0, you can build this service commercially.
- Best for
- DevOps and cloud freelancers with Kubernetes experience
- First step this week
- Follow the SPACE installation guide on a local Kind cluster and write down every step and problem you hit.
Open the full playbook
Launch steps
- Deploy SPACE locally and run the 'first sandbox' tutorial
- Turn your notes into a repeatable deployment script for one cloud
- Add network allow-lists, credential handling and logging
- Offer a pilot to an agent startup at a reduced rate in exchange for a case study
Tools
Risks
You become responsible for a security boundary, so a misconfiguration can be costly. Use written scopes, keep the platform updated, and avoid promising that it is 'unbreakable'.
Agent sandbox red-team checks
Perplexity's own test shows the right method: tell agents to try to break out and see what happens. Security testers can offer a smaller version for companies deploying agents: a scripted set of escape, network-bypass and credential-theft attempts run against the client's sandbox, with a report and fixes. The sandbox failures reported this year give buyers a clear reason to pay. Start with agent startups and agencies that let agents run code.
- Best for
- Penetration testers, security engineers and bug-bounty hunters
- First step this week
- Set up SPACE and one basic Docker sandbox, then write ten escape and network-bypass tests and compare the results.
Open the full playbook
Launch steps
- Build a test suite of escape, network and credential attempts
- Run it against SPACE and a plain container to show the difference
- Publish a short write-up of your findings as marketing
- Sell assessments with a clear scope and authorisation letter
Tools
Risks
Only test systems you are authorised in writing to test. Results depend on configuration, so a clean report is not a guarantee; say so in every report.
Migrate agent teams off paid sandboxes
Teams that already pay a commercial sandbox service may save money by self-hosting SPACE, which includes a wrapper for code written against E2B's Python SDK. A developer can offer a migration service: estimate current sandbox spend, test the client's workloads on SPACE, port what works and document what does not. The pitch is lower cost and more control, backed by a written comparison. It suits teams with steady, high sandbox usage.
- Best for
- Backend developers and small dev agencies working with agent startups
- First step this week
- Port one small E2B example script to SPACE's compatibility wrapper and record what changed.
Open the full playbook
Launch steps
- Read the E2B compatibility guide and its listed limitations
- Build a cost calculator comparing hosted sandbox fees with cloud VM costs
- Run a client's real workload on both and compare speed and cost
- Migrate in stages and keep the old provider as a fallback
Tools
Risks
Compatibility is partial, and self-hosting adds staffing and operations costs that can erase the savings for low-volume users. Show the full cost, not just the subscription line.
Taiwan plans industrial parks in Texas costing up to $4 billion each for AI hardware suppliers
Taiwan's economy minister Kung Ming-hsin told Bloomberg the island will back US industrial parks for smaller AI hardware suppliers, starting in Texas, with each site costing $2 billion to $4 billion. No site, schedule or customer commitment has been confirmed.
Taiwan plans to build a series of industrial parks in the United States to help its smaller AI hardware suppliers set up near their biggest customers, Economy Minister Kung Ming-hsin told Bloomberg in an interview. The first would be in Texas. Bloomberg reported the plan this week, and it was picked up widely on October 15 and 16. Kung estimated each complex would cost $2 billion to $4 billion, with the first costing up to $4 billion. The aim is to bring the parts makers that feed TSMC and server assemblers such as Foxconn, and through them Nvidia, onto US soil.
The money would not come mainly from Taiwan's state budget. The Taiwan Electrical and Electronic Manufacturers' Association, an industry body, is partnering with the government and is expected to raise the funds. The government's role is support: loan guarantees and help navigating local and federal US regulations, and, according to 24/7 Wall St., help with visas and land access. The model is clustering. Instead of each small supplier taking on the cost and risk of a US factory alone, they would share a site, services and paperwork.
There is already a template in Texas. Wistron opened a $700 million plant in the state that assembles Nvidia AI systems, and has said a second facility is in the works. TSMC has pledged $265 billion for US expansion, mostly in Arizona, and its management said on an October 15 call that Texas is one option for more capacity. The plan also serves politics: Taiwan faces pressure to meet investment commitments under its trade deal with Washington, and it wants to reduce supply-chain exposure to tensions with China.
The caveats are substantial. Nvidia, TSMC and Foxconn have made no commitment to the parks, according to reporting, and no participating suppliers, schedule or customer contracts have been named. TSMC said it has not announced any investment in Texas. One report cited people familiar with the matter saying land had been secured, but the ministry did not confirm that, and the economy ministry said it would share details 'when the timing is right'. Building factories in the US is also slower and more expensive than in Taiwan, which is exactly why small suppliers have held back.
If the parks go ahead, they would move a slice of the world's AI hardware supply chain, the cables, cooling parts, power supplies, boards and metal work around every AI server, closer to US data-centre demand. That means years of construction, hiring, logistics, compliance and services work around Texas. For people outside the US, the more realistic openings are remote: research, translation, documentation, procurement support and digital services for the hundreds of mid-sized Taiwanese firms that will have to make this move.
Why it mattersAI server production depends on hundreds of small suppliers, not just chipmakers. Moving them as a cluster would make US AI hardware supply faster and less exposed to geopolitical risk, if it happens.
👀 What to watch
Whether a site and first tenants are named, whether TSMC, Foxconn or Nvidia sign on, and how the plan fits Taiwan's trade commitments to the US.
3 opportunities from this story
US market-entry research packs for Taiwanese suppliers
Hundreds of small and mid-sized Taiwanese component makers will have to decide whether and how to move to the US, and many lack in-house research teams. A researcher can sell structured market-entry packs: Texas incentives, labour costs, permitting steps, logistics routes and nearby customers, tailored to one product category such as cooling parts or power supplies. The work is desk-based and can be done remotely from anywhere. Mandarin skills are a strong advantage but not essential if you partner with a translator.
- Best for
- Business researchers, consultants and analysts who work remotely
- First step this week
- Write a free 5-page sample pack on Texas for one product category and share it with a Taiwanese trade association or LinkedIn group.
Open the full playbook
Launch steps
- Pick one supplier category and map its main US customers
- Compile Texas incentives, costs and permitting steps from official sources
- Package it as a sample report in English and, if possible, Chinese
- Pitch to supplier associations and trade consultants as a white-label product
Tools
Risks
The parks may be delayed or scaled down, and buyers may prefer established consultancies. Keep sources current and sell the research as useful for any US expansion, not only the parks.
Bilingual technical documentation for US expansion
Suppliers entering the US need English product sheets, safety documents, compliance files and websites that meet American buyers' expectations. AI translation gets a first draft fast, but technical buyers notice errors, so human-reviewed, AI-assisted documentation is a sellable service. Translators and technical writers can offer packaged deliverables such as a product datasheet set or an English website. The Texas plan gives a clear reason for suppliers to update materials now.
- Best for
- Translators, technical writers and Mandarin–English bilingual freelancers
- First step this week
- Rewrite one public Taiwanese supplier's English datasheet as a before-and-after sample.
Open the full playbook
Launch steps
- Create a glossary of common terms for one product area
- Build an AI-assisted workflow with a human review step
- Produce two before-and-after samples
- Reach out to suppliers via Taiwan External Trade Development Council events and LinkedIn
Tools
Risks
Technical errors in safety or compliance documents carry real liability; agree that clients sign off on technical accuracy and stick to fields you understand.
A tracker of US AI hardware supply-chain projects
Investors, job seekers, logistics firms and local suppliers all want to know which AI factories are being built in the US, where, by whom and at what stage. A public, regularly updated database of announced projects, from Wistron's Texas plant to the proposed Taiwan parks, with status and sources, can grow into a paid product. It is a classic 'organise scattered news' business that suits a careful researcher. Revenue can come from a premium data tier, sponsorships or job listings.
- Best for
- Data-minded writers, researchers and no-code builders
- First step this week
- Build a public table of 20 announced US AI hardware and server projects with status, cost and source links.
Open the full playbook
Launch steps
- Collect projects from company announcements and reputable news
- Publish the table on a simple site with clear status labels
- Add a weekly email summarising changes
- Offer CSV exports and alerts as a paid tier
Tools
Risks
Announced projects often change or get cancelled, so stale data damages trust. Date every entry, link sources and mark proposals clearly as proposals.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.