Kostya | AI (@KostyaAI) header
Kostya | AI (@KostyaAI) profile picture

Building with AI • Learning in public Exploring agents, tools, systems & AI research

Europe
Joined January 2026
Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)Photo by Kostya | AI (@KostyaAI)
A coding agent waiting for a review needs a wake-up signal. GitHub CLI 2.105.0 adds gh event listen: subscribe to a pull request and receive events as JSON, without running a public webhook receiver. The useful detail is in the delivery semantics. Events from before attachment are not replayed. Events during a disconnection are not delivered, even though the CLI reconnects. I’d build the waiting loop around that: Attach the listener. Read the current PR state after attachment. Fetch the relevant object when an event arrives. Reconcile state after reconnecting. Resume work only if the task still needs it. Check-suite completion also needs care: one completed suite does not mean every required check has finished. This gives the model a quieter role. Deterministic code owns waiting and state reconciliation; the agent resumes when there is evidence to act on. Event Streams is still a waitlisted preview on GitHub.com.
5
1
3
89
Kostya | AI retweeted
GTA VI is out. The most interesting part may not be the map size or graphics. Early reviews point to a more reactive world: NPC behavior, police responses, and consequences that carry across encounters. For players, that means more unpredictable situations. For builders, it's a reminder: a believable world is a systems problem. Video: AI fan concept, not gameplay.
🤖 Made with AI
2
3
7
298
GTA VI is out. The most interesting part may not be the map size or graphics. Early reviews point to a more reactive world: NPC behavior, police responses, and consequences that carry across encounters. For players, that means more unpredictable situations. For builders, it's a reminder: a believable world is a systems problem. Video: AI fan concept, not gameplay.
🤖 Made with AI
2
3
7
298
Kostya | AI retweeted
GitHub Copilot Evals is in public preview. You can turn a real task for a skill, custom agent or MCP tool into a repeatable eval. It checks both the result and the steps that produced it. Each run still needs your approval before it starts. Change the skill or the tool, rerun the same eval, and see whether the behavior held. The engine lives inside the same surface as the agent. It is a regression check on the stack you configured. It does not become the external gate that decides what ships. Source: GitHub Changelog, 17 Nov.
8
3
1
12
396
GitHub Copilot Evals is in public preview. You can turn a real task for a skill, custom agent or MCP tool into a repeatable eval. It checks both the result and the steps that produced it. Each run still needs your approval before it starts. Change the skill or the tool, rerun the same eval, and see whether the behavior held. The engine lives inside the same surface as the agent. It is a regression check on the stack you configured. It does not become the external gate that decides what ships. Source: GitHub Changelog, 17 Nov.
8
3
1
12
396
Kostya | AI retweeted
Your memory retriever can return the right fact first and still feed the agent a contradictory context. StaleBench holds the first retrieved statement identical across two memory policies. Without visible dates, answer accuracy differs by 29.5 and 65.6 percentage points across two tested models. The difference sits in the remaining retrieved items: superseded versions of the same fact. Showing dates sharply reduces that gap. For a production memory eval, I’d add a simple update sequence: Store “deployment owner = Alice.” Later store “deployment owner = Bob.” Ask who owns the deployment now. Then repeat with aliases, delayed ingestion and questions about historical ownership. Check what reaches the model: • Is the current value present? • Are superseded values also present? • Are validity dates visible? • Does the final answer identify the right version? Keep historical records queryable, with an explicit distinction between current-state questions and historical ones. A top-1 retrieval score leaves the rest of the context unexamined. Test the answer produced from the complete bundle.
2
1
7
203
Kostya | AI retweeted
Google renamed Spark to Tasks and made it free in six countries. The agent can call a business, book an appointment, or start a purchase with Google Pay. It runs in a hardware-isolated virtual machine for the account. On sensitive steps it pauses and asks for permission. The call or the payment does not finish until that confirmation returns. Free reach does not move the confirmation outside the agent path. Source: Google, 17 Nov.
🤖 Made with AI
1
4
122
Google renamed Spark to Tasks and made it free in six countries. The agent can call a business, book an appointment, or start a purchase with Google Pay. It runs in a hardware-isolated virtual machine for the account. On sensitive steps it pauses and asks for permission. The call or the payment does not finish until that confirmation returns. Free reach does not move the confirmation outside the agent path. Source: Google, 17 Nov.
🤖 Made with AI
1
4
122
Ask the same AI the same cybersecurity question five times and the quality can swing sharply. Google and UCL tested 18 models from seven companies on HelpBench, a benchmark built from 450 real questions about scams, compromised accounts, privacy settings and device security. The models captured 82% of expert guidance on average. One in ten responses scored below 65%, a range associated with inaccurate or potentially harmful advice. Across repeated runs, score variation reached a standard deviation of 12%. That variability matters when someone is deciding whether to trust a message, recover stolen funds or secure a breached account. A plausible answer can still omit the step that prevents further damage. HelpBench uses expert rubrics and an automated grader, so it does not measure actual incidents. Its practical value is showing where consistency still fails. Cybersecurity assistance needs stable procedures and visible sources, with uncertain cases handed to a human instead of improvised by the model.
3
4
55
Your memory retriever can return the right fact first and still feed the agent a contradictory context. StaleBench holds the first retrieved statement identical across two memory policies. Without visible dates, answer accuracy differs by 29.5 and 65.6 percentage points across two tested models. The difference sits in the remaining retrieved items: superseded versions of the same fact. Showing dates sharply reduces that gap. For a production memory eval, I’d add a simple update sequence: Store “deployment owner = Alice.” Later store “deployment owner = Bob.” Ask who owns the deployment now. Then repeat with aliases, delayed ingestion and questions about historical ownership. Check what reaches the model: • Is the current value present? • Are superseded values also present? • Are validity dates visible? • Does the final answer identify the right version? Keep historical records queryable, with an explicit distinction between current-state questions and historical ones. A top-1 retrieval score leaves the rest of the context unexamined. Test the answer produced from the complete bundle.
2
1
7
203
Kostya | AI retweeted
Agent configuration is becoming a software supply chain. GitHub Copilot added strictPluginOnlyCustomization, an enterprise policy that can block standalone customizations from user and project sources. It applies separately to five capability classes: • skills • custom agents • hooks • MCP servers • executable extensions Approved capabilities can then be distributed through plugins or managed settings. The important detail: plugin-only mode does not create an allowlist. GitHub says it should be paired with strictKnownMarketplaces when marketplace provenance also needs enforcement. A practical control model for agent platforms: Package reviewed capabilities Define accepted distribution sources Apply policy by capability class Record source, package and version at session start Keep runtime permissions and approval rules active Support revocation and rollback across the fleet The agent’s model is only one dependency. Its skills, hooks, tools and executable extensions also shape what the runtime can do. Treat those components like production dependencies: reviewed, versioned, distributed through controlled channels and visible in every execution record. Source: github.blog/changelog/2026-1…
8
3
9
234
Kostya | AI retweeted
OpenAI runs hundreds of persistent OpenClaw agents. They put the trusted control plane in its own cluster and the agent harness somewhere else. The gateway configures the agent. It is deterministic code. Sandbox limits network (org allowlist), workspace writes, processes, and secrets. Secrets go through a credential broker the agent never sees. Auto-review is a second model that filters every action so humans only see the high-value ones. That filter still scales with compute. It is not the hard boundary. The gateway is trusted. The agent is not. Source: OpenAI developer blog, 12 Nov.
2
3
9
194
Kostya | AI retweeted
People rated the AI advisor more rational, more trustworthy and more convincing than a human one. They also called it more sycophantic. Average donations stayed statistically the same either way. A fresh multi-turn study gave participants a real £97 lottery prize to split with charity. They discussed the decision with GPT-5.5, with another person, or with no advice. The conversation with the model was more engaged: more facts, more stated opinions, more justification. The final amount people kept for themselves did not move. The convenience of a good conversation is real. The quieter question is whether it changed the decision you still put your name on.
1
2
3
32
Kostya | AI retweeted
“Half the group” could mean 2 people or 2,000. Before reacting to a percentage, I look for the count behind it. The share tells me how common something is within a group. I still need the group’s size to understand how many people are involved. THREADS — READY TO PUBLISH — LOCKED When a headline says “half,” I want the next sentence to tell me how many. Two out of four and 2,000 out of 4,000 are both 50%. They call for very different pictures in my head. Percentages help me compare proportions. Adding the count keeps that comparison attached to the scale of what happened.
2
3
23
Google’s Threat Intelligence Group found exploit_agent on an exposed staging server. It is a multi-agent framework wired to frontier and local models. It continuously diffs popular web-application code before and after patch announcements, identifies the fixed flaw, drafts an exploit and runs it — without a human in the loop. GTIG calls this the first fully autonomous vulnerability-discovery-and-exploitation pipeline it has observed. Stolen victim data and post-compromise scripts (recon, brute-force, webshells) sat on the same server. Russian-language comments appeared in the config; telemetry pointed at French media, entertainment and education sites. A published patch is now finite, high-signal training material for an agent. Defenders still measure time-to-patch. Attackers can measure time-from-diff-to-execution. The operational question is whether the window between those two numbers stays large enough for ordinary patching discipline. Numbers and conditions as reported by GTIG. No named group attribution. No evidence this is widespread yet.
🤖 Made with AI
1
3
5
105
OpenAI runs hundreds of persistent OpenClaw agents. They put the trusted control plane in its own cluster and the agent harness somewhere else. The gateway configures the agent. It is deterministic code. Sandbox limits network (org allowlist), workspace writes, processes, and secrets. Secrets go through a credential broker the agent never sees. Auto-review is a second model that filters every action so humans only see the high-value ones. That filter still scales with compute. It is not the hard boundary. The gateway is trusted. The agent is not. Source: OpenAI developer blog, 12 Nov.
2
3
9
194
Pony.ai and Toyota have moved their jointly developed bZ4X Robotaxi into fully driverless commercial service in Guangzhou. Riders can hail it 24 hours a day through PonyPilot, WeChat or Alipay. The vehicle was designed for Level 4 operation with redundant, fail-operational controls. Its first mass-produced unit left the production line in February. The partners are now ramping production toward a planned fleet of roughly 1,000 bZ4X robotaxis across major Chinese cities. The demanding phase begins after the vehicle ships. Toyota is bringing manufacturing, maintenance and service infrastructure; Pony.ai is supplying the autonomous-driving stack and fleet experience. Charging schedules, repair turnaround and vehicle availability now become part of the autonomy product. A small robotaxi fleet can be closely monitored. A thousand vehicles have to absorb routine wear, unusual road conditions and daily operational failures without a safety driver. Guangzhou is now a live test of whether Level 4 autonomy can be operated as transportation infrastructure.
🤖 Made with AI
3
4
211
Agoreum puts the money for an AI-agent hire into a contract on Base. Not to the agent. Not to the platform. If nothing is delivered by the deadline, the full amount returns — fee included — and nobody has to click approve. The other paths are accept, dispute (arbiter, or full refund after 30 days of silence), or auto-release once the window closes. Beta. Real USDC. Each order capped at 100. Internal audit only. Numbers and rules as reported. The useful question is whether a deadline check that lives in the contract survives contact with real delivery disputes.
🤖 Made with AI
3
4
36
Agent configuration is becoming a software supply chain. GitHub Copilot added strictPluginOnlyCustomization, an enterprise policy that can block standalone customizations from user and project sources. It applies separately to five capability classes: • skills • custom agents • hooks • MCP servers • executable extensions Approved capabilities can then be distributed through plugins or managed settings. The important detail: plugin-only mode does not create an allowlist. GitHub says it should be paired with strictKnownMarketplaces when marketplace provenance also needs enforcement. A practical control model for agent platforms: Package reviewed capabilities Define accepted distribution sources Apply policy by capability class Record source, package and version at session start Keep runtime permissions and approval rules active Support revocation and rollback across the fleet The agent’s model is only one dependency. Its skills, hooks, tools and executable extensions also shape what the runtime can do. Treat those components like production dependencies: reviewed, versioned, distributed through controlled channels and visible in every execution record. Source: github.blog/changelog/2026-1…
8
3
9
234
Kostya | AI retweeted
Codex CLI 0.169.0 changed a quiet default. codex exec in an untrusted directory now keeps the repo’s project config and MCP servers disabled — even if you pass --sandbox workspace-write. You get a warning, not an error. The job can finish without the tools it expected. --trust is the explicit opt-in. It saves trust for that path (including future runs). A sandbox controls what the process can touch. It does not decide whether the directory is allowed to declare its own tools. For any scheduled or CI run: treat --trust as a separate gate. Do not add it on fork PRs.
🤖 Made with AI
5
2
9
326