Moonshot AI has introduced Kimi Work, an AI agent that runs on your own desktop. The Beijing-based AI entity announced it this week along with downloads for macOS and Windows. Kimi Work reads local files, drives your real browser, and runs scheduled tasks. It targets knowledge workers whose bottleneck is access to files and live sessions.
Most agent tools of the past two years ran in the cloud. You type a goal, a remote server spins up a sandbox, and a hosted browser acts. Kimi Work runs locally instead, reaching files and sessions you already use.
What is Kimi Work?
Kimi Work is a downloadable application, not a web chat. You give it goals in plain language, and it acts on your machine. Independent community mentions report that it runs on Kimi K2.6, Moonshot’s flagship model.
K2.6 is an open-weight Mixture-of-Experts model released on April 20, 2026. It activates about 32 billion parameters per token. It carries a 256K-token context window for long, multi-step work.
How Kimi Work Operates
Four building blocks define the product. Knowing them helps you reason about what it can do.
- Agent Swarm: Kimi Work can run many sub-agents in parallel on your machine. According to Moonshot release, the swarm scales to 300 sub-agents. The system splits a task into parts, then coordinates the results. K2.6’s swarm is documented up to 4,000 coordinated steps.
- WebBridge: This browser extension lets the agent use a browser like a person. It searches, scrolls, extracts data, and fills forms across tabs. Because it uses your real session, it inherits your existing logins and cookies.
- Cron scheduling engine: A built-in scheduler runs jobs on a daily, hourly, or conditional basis. Per Moonshot, triggers include LLM agent calls and Python or shell scripts. A “Keep Computer Awake” toggle keeps overnight jobs from stalling.
- Local files and code: The agent reads folders you mount and runs Python in the background. According to Moonshot release, original files stay in place unless you approve a change.
The desktop app also ships finance-specific data. It is pre-integrated with market data for A-shares, Hong Kong stocks, and US equities. According to Moonshot release, this removes the need for custom API setup. Finished research can convert into PowerPoint decks or Excel sheets.
Use Cases With Examples
- Document triage: Point the agent at a folder of quarterly PDFs. Ask it to summarize them into one document, keeping originals intact. The swarm assigns one reader per file, then merges findings.
- Web data collection: Tell WebBridge to pull historical prices for three tickers. It opens your browser, sets the date range, and extracts the tables. Python then normalizes columns and writes an Excel workbook.
- Scheduled briefings: Define a 7:00 AM job in the cron engine. Each morning it gathers headlines and drafts a markdown briefing. With “Keep Computer Awake” on, the job survives overnight.
- Office generation: Ask for a short market-brief deck after a research pass. The agent drafts sections in parallel and renders native slides.
Kimi Work vs Cloud Agents
The core difference is where the agent runs and what it can reach. The table compares Kimi Work against a typical cloud agent.
| Dimension | Kimi Work (local) | Typical cloud agent |
|---|---|---|
| Execution location | Your desktop | Vendor servers |
| File access | Mounts your local folders | Uploaded or sandboxed files |
| Browser | Your real, logged-in browser via WebBridge | Hosted virtual browser |
| Scheduling | Built-in cron engine | Often external or limited |
| Underlying model | Kimi K2.6, reported | Vendor’s hosted model |
| Setup | Install app, grant folder access | Zero-install, open a tab |
| Security responsibility | Falls on the user | Falls on the vendor |
Neither approach wins outright. Local execution keeps data on your device and reaches real files. Cloud execution trades that control for zero-setup convenience and managed safety.
Scheduling: The Cron Engine in Practice
Kimi Work is driven by natural language, not a public API. Its scheduler is a cron engine, so it accepts standard cron schedules. The five fields are: minute, hour, day-of-month, month, and day-of-week.
# Standard cron schedules the engine understands
0 7 * * * # every day at 07:00
0 * * * * # every hour, on the hour
30 8 * * 1-5 # 08:30 on weekdays only (Mon-Fri)
0 0 1 * * # 00:00 on the first day of each monthYou pair a schedule with a plain-language task. A daily briefing job reads like this.
Schedule: 0 7 * * * (every day at 07:00)
Task: "Draft today's market briefing and save it to
~/KimiWorkspace/briefing.md. Ask before writing."The approval gate then applies to that write, and to any web action.
Key Takeaways
- An “Ask before acting” gate, with YOLO mode off, prompts before any file write.
- Kimi Work is a local desktop agent for macOS (Apple silicon) and Windows.
- An Agent Swarm runs up to 300 sub-agents in parallel on your machine.
- WebBridge drives your logged-in browser; a built-in cron engine runs scheduled jobs.
- It reads local folders and runs Python, keeping originals unless you approve changes.
Marktechpost’s Interactive Explainer
Check out the Details here. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.
Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us
