World Edit


Kanal geosi va tili: Ukraina, Inglizcha


World Edit explores how AI, tools, and technology are changing the way we work, think, and build.

Связанные каналы

Kanal geosi va tili
Ukraina, Inglizcha
Statistika
Postlar filtri


Someone finally built a gaming AI companion that actually plays with you, not just talks. Pantelis calls it Varkos and runs it inside Skyrim.

Most "AI NPCs" can hold a conversation and stay in character, but they fall apart where it counts: weak world agency and latency. Varkos fights, fetches and carries loot, inspects items, follows complex multi-step orders, and can wait for a cue. Tell it "I will fire an arrow into the sky as the signal" and it registers the trigger, waits for the actual hit, then continues the plan. The mic stays live the whole session, so you do not open a menu to summon him, you just talk. Over time his personality even shifts.

The core bet is local. The author keeps the critical real-time path mostly on his own hardware: he claims 40-80 ms for speech recognition, around 20 ms to analyze an action, and starting a reply in under 500 ms in some scenarios. That is cheaper than the cloud, and it keeps a single-player game from turning into a metered, eavesdropped service.

The full code is not open yet. Fresh Show HN, August 24.

Watch it in action: https://youtu.be/7IW0Ylydpes
Project: https://pantel.is/projects/ai-gaming-companion/
Author: https://twitter.com/pkalogiros


Simon Willison nailed where agentic development is heading: AI writes code faster than a human can read it.

So the engineer's key skill is shifting away from code review toward broader verification — tests, evals, invariants, observability, security checks.

Code is getting cheaper. Proof that it is correct is getting more expensive.

AI has already learned to write code. Now we need to learn how to reliably verify that it works.

Source: https://simonwillison.net/2026/Aug/22/more-than-just-code-review/


Ox Alpha: A Powerful Model Without a Name

A free stealth model with a context window exceeding one million tokens, image support, tool integration, and long-form coding agent tasks has become available on OpenRouter. Based on its tokenizer, API behavior, and vision pipeline, it closely resembles a new model from the GLM family, although no official confirmation has been provided. Initial tests indicate strong performance with large repositories and frontend development; however, the service remains unstable at this time. Notably, the identity of the entity behind the model and the methods of data utilization remain unknown.

Ox Alpha:
https://openrouter.ai/stealth/ox-alpha

Overview:
https://oxalpha.com/


Claude Mythos 5 is now more accessible for defensive security — but not as a regular chat/API: Enterprise customers can now run Mythos 5 inside Claude Security to hunt for vulnerabilities in their own GitHub repositories. The user gets findings and patches, not direct access to the model.

https://claude.com/blog/bringing-claude-mythos-5-to-more-defenders


OpenAI has temporarily cut the standard API price for GPT-5.6 Sol: short-context is now $4/$20 per 1M input/output tokens instead of $5/$30 — input is 20% cheaper, output down by a third. The promotional pricing runs at least until November 21, 2026.

https://developers.openai.com/api/docs/pricing


DeepSeek released V4-Flash-Vision-Exp — the first vision version of V4 Flash in its API. It accepts text + images, works with tool/agent workflows, and supports Chat Completions, Responses, and Anthropic-compatible Messages API.

DeepSeek states that text capabilities remain at the V4 Flash level, while multimodal-agent results have approached those of Claude Opus 4.8. For example, in their table, Vision Exp scores 59.3% on DeepSWE compared to 58.0% for Opus 4.8, and 36.5% compared to 39.4% on ApexBench. These are vendor-reported results; a full independent evaluation of the new model is not yet available.

https://api-docs.deepseek.com/news/news260821//


Someone built `Lucasartsifier`, a tool that fixes one of the harshest problems in old Sierra adventure games: you could break the game in a way where it still runs, but can no longer be completed.

It decompiles SCI scripts, finds these “walking-dead” states, and generates patches. The best part: the author says he handles the design and playtesting himself, while Claude helps with implementation. So AI here is not “writing another todo app.” It is digging through old game engines and removing traps that annoyed players for decades.

Sources:
https://news.ycombinator.com/item?id=49355607
https://github.com/katiahayati/lucasartsifier/


Browser-use is a tool for agents that need to work with the web the same way a person does.

Not through an API or a separate integration, but directly through the browser: open a site, find the right thing, click a button, fill out a form, check a status, pull data from a dashboard or admin panel.

A lot of real operational work still lives there. CRMs, internal panels, contractor portals, forms, tables. Often there is no API, or building an integration is too expensive, but someone still has to go in and do the work by hand.

Browser-use closes that gap. It gives an agent access to places that used to stay manual simply because they were locked inside the browser.

Sources:
https://github.com/browser-use/browser-use
https://github.com/browser-use/browser-use-examples
https://github.com/browser-use/browser-use/releases


Anthropic showed a strong example of Claude in experimental science. Claude designed protein binders for 15 targets, and independent labs, Adaptyv Bio and Twist Bioscience, physically confirmed success for 14 of them.

The hit rate depended on the mode: 22.6–26.7% in the multi-target run and 35.1% in single-target mode. Important detail: Claude did not “invent a drug.” It ran a protein design workflow with specialized models, GPUs, and wet-lab validation. But for a task that can usually take weeks or months per target, this is already a serious result.

Source:
https://www.anthropic.com/research/Claude-accelerates-protein-design


OpenAI has temporarily slowed frontier training because of cyber risks. The company paused RL training for deployment-bound models for two weeks, and its largest planned frontier RL run has still not resumed.

The reason is the Hugging Face incident and internal evaluations of Astra, where OpenAI says a `Critical` cyber-capability threshold is no longer ruled out. These models are now being isolated during training itself: research sandboxes, network isolation, and tool-use monitoring.

Sources:
https://openai.com/index/pacing-model-development-cyber-capabilities/
https://openai.com/index/hugging-face-model-evaluation-security-incident/


Cursor added `Origin Code Hosting`.

It is code hosting inside Cursor: repositories, code browsing, pull requests, comments, merge, and GitHub sync.

Cursor is also expanding the infrastructure around cloud agents: prebuilt dev environments, faster agent startup, and integrations with Vercel, Buildkite, Depot, and Google Workspace.

The direction is practical: Cursor is moving beyond the editor and pulling more of the development workflow into one place: repo, PR, review, CI, preview deploys, and agents.

Source: https://cursor.com/changelog


Video oldindan ko‘rish uchun mavjud emas
Telegram'da ko‘rish
Unitree showed a humanoid robot called Superman. The company claims a 2-meter standing jump and a top speed of 12.66 m/s.

For now, these are Unitree's own numbers, without independent measurement. Hopefully, kryptonite is included in the box.

Sources:
https://x.com/UnitreeRobotics/status/2089240553682809175
https://www.youtube.com/watch?v=O7OkiZfIlS4


Andrew Ng described how the software engineering role is changing because of coding agents.

His team at DeepLearning.AI analyzed more than 10,000 job postings, interviewed AI experts, hiring managers, and recruiters, and used surveys plus other public data. Based on that, Ng identifies four groups of AI engineering skills: building AI applications, core software engineering, using coding agents, and shaping the build.

The main point is not that programmers should “know how to use AI.” That is already the baseline.

Ng writes that AI systems are less deterministic than traditional software. So engineers need evals, error analysis, guardrails, and a clear sense of where an agent loop can break a product or damage data.

He also pushes back against vibe coding without engineering fundamentals. A coding agent can produce code quickly, but the human still has to understand architecture, testing, security, reliability, cost, and tradeoffs.

The bigger shift is that the engineer’s role is moving from “implement this spec” to “help decide what should be in the spec.”

In this model, a strong engineer is not just someone who generates code with an agent. They frame the task, give the agent the right context, verify the result, and take ownership of the product decision.

Source: https://www.linkedin.com/pulse/ai-engineering-skills-map-andrew-ng-m479c


Garry Tan described an idea on The a16z Show that captures where agentic companies may be heading: a future AI company could accumulate “employees” inside markdown files.

It sounds exaggerated, but the logic is strong.

After using coding agents for individual tasks, the next step is to turn well-executed processes into reusable skills. A person and an agent go through a task once, capture the right process, add instructions, code, and tests, and then the agent can run that process again. Every new mistake becomes a bugfix for the skill.

Tan puts it very directly:

“A markdown file is an employee.”

Timestamp: 00:23:36.

Taken literally, of course, a .md file does not replace a person. The stronger idea is that AI lets companies turn tacit knowledge into executable knowledge.

Before, it was: “Sarah knows how to do this properly.”

Then: SOP / Notion / wiki.

Now, potentially: SOP → skill → the system executes the process itself.

But there is an important limit here. “A markdown file is a perfect employee” skips the hardest question: who decides whether the result is correct?

The more serious the task, the more important evals, permissions, observability, provenance, and human approval become. Without that layer, skillification can easily become automated repetition of mistakes rather than organizational memory.

That is why the idea of skillification is much more interesting than the trendy “AI employee” slogan.

Sources:
https://www.youtube.com/watch?v=fsTtKywmWlU
https://podcasts.apple.com/us/podcast/garry-tan-on-taste-agents-and-founder-ambition/id842818711?i=1000782943964


Google DeepMind is moving sign language translation into the phone keyboard.

Its SL2T model turns American Sign Language into English text. Google is adding it to Gboard and Live Transcribe on Pixel 11.

A person signs in front of the camera, and the phone turns it into text for messages, search, documents, or live replies.

This is not just gesture recognition. Sign language has its own grammar, facial markers, body movement, and spatial structure, so SL2T is closer to translation than transcription.

Google says the model was trained on 100,000+ hours of data across more than 50 sign languages. The first launch is narrow: Pixel 11, ASL to English.

If the quality holds up in real use, signing could become a native phone input, like voice dictation.

Source:
https://deepmind.google/blog/putting-sign-language-ai-into-users-hands/


Raspberry Pi is a small computer that people often use at home as a server, connecting it to cameras, sensors, robots, and Home Assistant.

Google showed how to run local AI on Raspberry Pi 5 through LiteRT and Gemma. Not in the cloud, but directly on a small board next to the router.

This is interesting for smart home. A camera near the door can do more than detect motion: it can understand that a courier left a package. Sensors can do more than show CO2 levels: they can explain that the air in the room is bad and it is worth opening a window.

In Google’s demo, the Reachy Mini robot on Raspberry Pi 5 sees, listens, responds, and moves locally. Gemma 4 E2B on Pi 5 delivers around 9 tokens/sec decode and stays within ~1.4 GB peak memory.

Source:
https://developers.googleblog.com/mastering-edge-ai-on-raspberry-pi-with-litert-and-gemma/


Meta frames its AI strategy as a political position: superintelligence should be available to many people, not concentrated in the hands of a few companies or governments.

In “The Future is for Everyone,” Zuckerberg pushes the idea of personal superintelligence — AI as a personal tool for work, learning, creativity, business, and health.

That explains Meta’s bet on open-weight models, smart glasses, agents, and its own AI infrastructure. The company wants powerful AI to live not only inside corporate systems, but also in personal devices and everyday workflows.

But this is not altruism. It is strategy: if personal AI becomes the main interface of the future, Meta wants to be the company that gives people that interface.

Sources:
https://www.meta.com/thefutureisforeveryone/
https://about.fb.com/news/2026/08/the-future-is-for-everyone/


Anthropic described Model 2 for the first time in its August 2026 Risk Report.

It is an internal Mythos-class model, not a public release. Anthropic does not plan to release it externally, and there is no model card, public benchmark set, pricing, or API access.

Anthropic says Model 2 is slightly more capable than Mythos 5 overall: stronger in some areas, weaker in others. The company calls it a noticeable improvement for many internal-use tasks, but not a jump on the scale of Opus 4.6 to Mythos Preview.

The evaluation is also limited. Anthropic did not run the full predeployment evaluation suite for Model 2, so its own confidence in the capability assessment is lower.

Model 2 is already used inside Anthropic alongside Mythos 5 for coding, data generation, research, engineering, and other agentic use cases. Some of that work runs through persistent agent deployments.

One concrete number from the report: Claude now writes “a large majority” of the code merged into Anthropic production codebases.

Source:
https://www.anthropic.com/aug-2026-risk-report


Z.ai released GLM-5.3.

One detail matters in this release: there is no new base model. GLM-5.3 is built on the same base as GLM-5.2, and Z.ai attributes the gains to scaled post-training: more real environments, longer tasks, and RL on workflows that look closer to an engineer's work.

The unexpected jump came in cybersecurity. GLM-5.3 scored 84.5% on CyberGym, and on ExploitBench it moved from 24.4% in GLM-5.2 to 54.4%.

Another detail: since GLM-5.2, Z.ai maintains a disclosure ledger with 2,436 vulnerability findings. 53 are already publicly disclosed, 2,383 are still under embargo. 1,097 are classified as critical/high. The oldest vulnerability traces back to code introduced in 1981; average lifetime before discovery: 26.6 years.

Weights are not open yet. Z.ai says it will release them in about two weeks, after safety evaluation and hardening.

This points to a new problem for open-weight coding models. RL that teaches a model to solve real tasks can also teach it to move through an exploitation chain. In that context, the pause between API release and open weights is not a formality; it becomes part of the safety mechanism.

Sources:
https://z.ai/blog/glm-5.3
https://cvd.z.ai/


OpenAI showed Ultrafast mode for GPT-5.6 Sol on Cerebras infrastructure.

For now, it is a limited preview in the OpenAI API, not a mass ChatGPT mode.

The number is sharp: up to 14x faster than Standard processing and up to 750 output tokens/sec. Cerebras also reports a 5.6x end-to-end speedup on GDP-Val and around 7x faster HLE runs in its own tests.

For developers, this changes the agent loop in a practical way. When a frontier model responds almost in real time, less time gets lost waiting between planning, tool calls, and returning to code.

Sources:
https://openai.com/index/previewing-ultrafast/
https://www.cerebras.ai/blog/accelerating-gpt-5-6-sol-ultrafast-with-openai

20 ta oxirgi post ko‘rsatilgan.