<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Interpreter on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/code-interpreter/</link><description>Recent content in Code Interpreter on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 03 Mar 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/code-interpreter/index.xml" rel="self" type="application/rss+xml"/><item><title>Aliyun Bailian (7): Built-in Web Search and Code Interpreter</title><link>https://www.chenk.top/en/aliyun-bailian/07-builtin-tools/</link><pubDate>Tue, 03 Mar 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-bailian/07-builtin-tools/</guid><description>&lt;p>The previous article built a coding agent by hand: define tools, loop, dispatch, repeat. That&amp;rsquo;s the right pattern when the tools are &lt;em>yours&lt;/em> (your filesystem, your test runner). But for two extremely common tools — searching the web and running a snippet of code — Model Studio now runs them server-side. You enable a flag, the platform does the search-or-execute round trip inside one API call, and you get the final answer back. This article is the practical guide to those built-in tools.&lt;/p></description></item></channel></rss>