Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
165393 stories
·
33 followers

Datadog LLM Observability: Features, Pricing, and Alternatives

1 Share
Datadog LLM Observability: Features, Pricing, and Alternatives

If you’re evaluating Datadog LLM Observability, you’ll want to know how it fits alongside your existing application performance monitoring (APM) tools and what it costs as your LLM applications scale.

Read the whole story
alvinashcraft
29 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Microsoft Perception – Find the risk, Investigate the threat, and Coordinate the fix

1 Share

The Cybersecurity Game Is Changing, And Microsoft Just Raised the Stakes!

At Microsoft Ignite 2026 in San Francisco, Microsoft introduced one of its most significant advancements in enterprise cybersecurity: Microsoft Perception, a new agentic security platform designed to fundamentally transform how organizations defend themselves against cyberattacks.

Previously introduced as Project Perception in July 2026, the platform officially reached General Availability (GA) at Ignite on November 17, 2026.

But this is much more than another cybersecurity product.

Microsoft Perception represents a shift in how we think about enterprise security: moving from individual tools and disconnected alerts toward coordinated teams of autonomous AI agents working continuously to identify threats, investigate attacks, and strengthen defenses.

The idea is compelling:

What if your cybersecurity tools could think like attackers, investigate like experienced security analysts, and coordinate remediation before vulnerabilities become disasters?

That is exactly the vision behind Microsoft Perception.

Let’s explore how it works, why it matters, and what organizations should consider before implementing it.

What Exactly Is Microsoft Perception?

Microsoft Perception is an enterprise-grade, multi-agent cybersecurity system that brings together specialized AI agents to collaborate across the complete security lifecycle.

Rather than relying entirely on human analysts to interpret thousands of alerts, correlate activity across systems, and coordinate remediation, Perception uses intelligent agents to automate and orchestrate substantial portions of that work.

These agents operate through coordinated workflows called playbooks, sharing information and intelligence to achieve specific security outcomes.

Microsoft organizes Perception around three specialized agent teams:

  • Red Team Agents: Discover weaknesses and simulate potential attacks.

  • Blue Team Agents: Detect suspicious activity, investigate threats, and strengthen detection capabilities.

  • Green Team Agents: Prioritize risks, coordinate remediation, and improve security posture.

Think of Microsoft Perception as a digital cybersecurity team that never gets tired, never stops analyzing security signals, and can coordinate complex security activities at a scale that would be difficult to achieve manually.

Importantly, Perception is not designed to eliminate human security professionals.

Instead, it helps them become dramatically more effective by automating repetitive work, surfacing actionable intelligence, and keeping people in control of high-impact security decisions.

Meet the Three Teams Behind Microsoft Perception

 

Microsoft Red Team Holographic Operations

Red Team Agents: Think Like the Attacker

In traditional cybersecurity, Red Teams are responsible for simulating attacks to discover potential weaknesses before malicious actors exploit them.

Microsoft Perception brings AI agents into this process.

Red Team Agents can help organizations:

  • Discover potentially exploitable vulnerabilities.

  • Analyze attack paths through applications and infrastructure.

  • Simulate adversarial behaviors within authorized security testing.

  • Evaluate weaknesses in application code and configurations.

  • Identify which vulnerabilities represent meaningful exploitation risks.

For example, imagine an enterprise application hosted in Microsoft Azure with several publicly accessible endpoints.

A Red Team Agent could analyze the application’s attack surface and help identify a vulnerable component that might allow unauthorized access.

Instead of simply producing a generic list of vulnerabilities, the objective is to provide evidence about which weaknesses could realistically be exploited.

This distinction matters.

Not every vulnerability represents the same level of business risk.

Understanding the actual exploitability of a vulnerability can help security teams focus their attention and resources where they matter most.

Microsoft is also extending these capabilities through its advanced code vulnerability research technology, including Codename MDASH.

Blue Team AI Cybersecurity Command Center

Blue Team Agents: Detect, Investigate, and Defend

Blue Teams are responsible for protecting the organization by monitoring activity, investigating suspicious behavior, and responding to security incidents.

Microsoft Perception’s Blue Team Agents bring AI-powered reasoning and automation into these responsibilities.

They help organizations:

  • Triage large volumes of security alerts.

  • Correlate activity across identities, endpoints, email, and cloud environments.

  • Investigate suspected attacks.

  • Reconstruct attack timelines.

  • Identify compromised accounts and resources.

  • Recommend appropriate incident responses.

  • Create and improve threat detection rules.

One of the most interesting announcements at Ignite concerns Microsoft’s Triage Agent.

According to Microsoft, the agent can now triage approximately 80% of the alert volume in a typical Microsoft Defender security queue.

This claim is based on Microsoft’s analysis of approximately eight million security alerts across Defender workloads. Actual coverage varies by organization and is not guaranteed.

Consider what that could mean for an enterprise security operations center.

Instead of security analysts spending hours investigating routine or low-priority alerts, AI agents can perform initial analysis and provide supporting evidence.

Human analysts can then focus on incidents requiring greater attention, deeper investigation, and business judgment.

The objective isn’t simply faster alert processing.

It’s helping organizations make better security decisions, sooner.

Microsoft Green Team AI Command Center

Green Team Agents: Fix Problems and Strengthen Defenses

Finding a vulnerability is important.

Investigating a potential attack is essential.

But neither activity delivers its full value unless organizations actually address the underlying risks.

This is where Green Team Agents come into play.

Green Team Agents focus on risk reduction, remediation, and improving the organization’s security posture.

They can help:

  • Prioritize vulnerabilities based on exposure and business risk.

  • Recommend corrective actions.

  • Coordinate remediation activities.

  • Support patch management workflows.

  • Identify opportunities to harden infrastructure.

  • Reduce the organization’s attack surface.

  • Validate and track improvements.

For example, imagine that a Red Team Agent identifies an exploitable vulnerability in an application, and a Blue Team Agent determines that suspicious activity has already targeted the affected system.

A Green Team Agent can help prioritize remediation, coordinate the appropriate workflow, and guide the organization toward eliminating or mitigating the vulnerability.

Depending on the supported workflow and the organization’s policies, this could include coordinating patching through Microsoft Intune or identifying temporary protective measures when an immediate patch is not feasible.

The result is a more connected security lifecycle: find the risk, investigate the threat, and coordinate the fix.

The Real Innovation: All Three Teams Work Together!

Individually, these capabilities are impressive.

But the most exciting aspect of Microsoft Perception is how the agents collaborate.

Traditional cybersecurity platforms often operate across separate processes.

One tool identifies a vulnerability.

Another tool detects suspicious activity.

A security analyst investigates the incident.

An IT team receives a remediation ticket.

And potentially days later, someone implements the fix.

Microsoft Perception aims to connect these activities through intelligent multi-agent orchestration.

The platform uses playbooks that coordinate specialized agents around specific security objectives.

These playbooks can orchestrate security investigations, vulnerability analysis, detection engineering, and remediation workflows.

All while maintaining governance, permissions, and human approval where required.

A Practical Example: Detecting and Responding to a Compromised Identity

Imagine a company operating several business applications on Microsoft Azure.

An employee’s credentials are compromised through a phishing attack.

An attacker successfully authenticates and begins exploring cloud resources.

Here is an illustrative workflow showing how a coordinated agentic defense could help.

Step 1, Blue Team: Detect Suspicious Activity

A Blue Team Agent investigates unusual authentication events and correlates them with security signals from Microsoft Entra ID, endpoints, and cloud infrastructure.

It identifies suspicious behavior and begins reconstructing the attack timeline.

Step 2, Red Team: Identify Potential Attack Paths

Authorized Red Team analysis evaluates exposed systems, configurations, and potential weaknesses that could allow the attacker to escalate privileges or access additional resources.

Step 3, Green Team: Prioritize Remediation

A Green Team Agent helps identify corrective actions, such as reducing excessive permissions, addressing vulnerable configurations, or coordinating additional security protections.

Step 4, Human Security Team: Review and Approve

Security professionals review the findings and authorize high-impact actions according to organizational policies.

Step 5, Continuous Improvement

The organization uses the findings to improve detection coverage, close security gaps, and strengthen its defenses against similar attacks.

This is an illustrative example rather than a promise that every step is automatically available in every environment.

However, it demonstrates the value of an agentic system that combines shared context, specialized capabilities, and coordinated action.

Microsoft Perception Is More Than Three Teams of Agents

Underneath the surface, Microsoft Perception combines several important architectural capabilities.

Multi-Agent Orchestration

Perception uses an orchestration harness to coordinate agents, distribute work, and manage execution across complex security workflows.

Specialized Cybersecurity AI Models

Microsoft Perception uses purpose-built AI models, including Microsoft’s MAI-Cyber family, alongside other models selected for different security tasks.

The objective is to balance reasoning quality, performance, and cost.

Security Context and Threat Intelligence

Agents can use signals from the Microsoft Security ecosystem, including identity, endpoint, cloud, and application security information.

Microsoft is also extending supported integrations to third-party environments, including AWS, Okta, and Salesforce.

This matters because most enterprise security environments extend beyond a single vendor.

Model Context Protocol (MCP) and API Integration

Microsoft Perception supports integration scenarios involving MCP and APIs, allowing organizations to invoke supported playbooks from existing operational tools.

This opens interesting opportunities for integrating agentic security with broader enterprise workflows.

Specific integrations and capabilities remain subject to product availability, permissions, and supported configurations.

Governance and Human Oversight

Autonomous cybersecurity cannot operate without adequate controls.

Microsoft Perception incorporates least-privilege access, policy guardrails, auditability, and human approval for critical actions.

These capabilities are essential because an incorrectly executed security response could interrupt legitimate business operations.

Microsoft Perception_ Multi-Agent-Foundry

 

What About Microsoft Foundry and Microsoft Agent Framework?

For developers and architects already working with Microsoft Foundry and Microsoft Agent Framework, Perception introduces an interesting new dimension to the Microsoft AI ecosystem.

Let’s distinguish their responsibilities.

Microsoft Foundry provides the services and capabilities organizations use to build, deploy, evaluate, and operate enterprise AI applications and agents.

Microsoft Agent Framework provides developers with the programming capabilities to build intelligent agents and orchestrate multi-agent workflows.

Microsoft Perception is a specialized cybersecurity system that applies multi-agent orchestration to enterprise security operations.

These technologies are complementary rather than interchangeable.

Developers can use Microsoft Agent Framework to create business-specific intelligent agents, while security teams use Microsoft Perception to help protect the infrastructure, identities, applications, and resources those agents depend on.

Perception’s MCP and API integration capabilities also create opportunities for coordinating supported security workflows with custom enterprise applications, including scenarios involving Microsoft Foundry.

However, Perception is not simply a collection of Microsoft Agent Framework agents that developers deploy themselves. It is a managed security product with its own architecture, governance, orchestration, and licensing.

For organizations investing heavily in agentic AI, this distinction is important.

Building intelligent agents is only one part of the challenge. Securing the environment in which those agents operate is equally critical.

Why Microsoft Perception Matters to Businesses

Microsoft Perception isn’t relevant only to large enterprises with sophisticated cybersecurity teams.

The underlying challenges it addresses affect organizations across industries.

1. Cyberattacks Are Becoming Faster

Attackers are increasingly using automation and AI to discover vulnerabilities, launch phishing campaigns, and exploit weaknesses.

Security teams need tools capable of keeping pace.

2. Security Teams Are Overwhelmed

Organizations generate enormous volumes of security telemetry and alerts.

AI-powered triage and investigation can help analysts spend less time processing noise and more time investigating meaningful threats.

3. Vulnerability Management Is Often Disconnected

Finding vulnerabilities is relatively straightforward compared with prioritizing, fixing, and validating them.

Perception brings greater coordination to that process.

4. Enterprise Environments Are Becoming More Complex

Azure, Microsoft 365, external cloud providers, SaaS platforms, and autonomous AI agents create increasingly complex security environments.

Coordinated security intelligence can help organizations understand risks spanning multiple systems.

5. Businesses Need Security Outcomes, Not More Dashboards

A dashboard showing hundreds of vulnerabilities isn’t the same as actually reducing business risk.

Microsoft Perception emphasizes moving from detection toward investigation, remediation, and measurable security improvements.

This may be the most important shift of all.

Getting Started with Microsoft Perception

With Microsoft Perception now generally available, organizations can begin evaluating how it fits into their cybersecurity strategy.

Microsoft offers consumption-based pricing options, including pay-as-you-go and the AI Flex Plan. The platform also includes usage and cost management capabilities.

However, successful adoption requires more than enabling a product.

Organizations should approach implementation systematically.

First, assess the existing security environment. Understand current tools, Microsoft Defender coverage, identity controls, cloud resources, and vulnerability management processes.

Second, identify high-value use cases. Start with manageable scenarios such as security alert triage, authorized vulnerability assessment, or exposure prioritization.

Third, establish governance and permissions. Define what agents can access, which actions can be automated, and which operations require human approval.

Fourth, configure and evaluate playbooks. Select the appropriate Red, Blue, and Green Team workflows, connect supported security data, and validate their behavior against realistic scenarios.

Finally, measure outcomes and expand. Monitor detection quality, investigation efficiency, remediation progress, usage costs, and operational impact before increasing automation.

A measured rollout is essential to ensuring AI-powered security delivers value without introducing unnecessary operational risk.


How The Training Boss Can Help Your Organization Implement Microsoft Perception

At The Training Boss, we believe the next generation of enterprise technology will be powered by intelligent AI agents working alongside experienced professionals.

Microsoft Perception is a compelling example of that future.

But adopting an advanced multi-agent cybersecurity platform requires the right architecture, implementation strategy, governance, and training.

That is where The Training Boss can help.

Our consulting, architecture, and technical training services can help organizations evaluate, plan, configure, and adopt Microsoft Perception as part of their broader Microsoft security and Azure environments.

Red Team Implementation and Enablement

We can help your organization plan and configure authorized Red Team workflows to identify vulnerabilities, evaluate attack surfaces, and improve understanding of potential exploitation risks.

This includes selecting appropriate use cases, establishing testing boundaries, and defining meaningful security assessment outcomes.

Blue Team Implementation and Enablement

We can help your security and IT teams configure supported Blue Team capabilities for alert triage, incident investigation, detection improvement, and coordinated security operations.

Our objective is to help your teams understand how to apply AI-powered security investigations effectively while maintaining appropriate operational oversight.

Green Team Implementation and Enablement

We can help your organization establish risk prioritization and remediation workflows, connect supported Microsoft security tools, and develop processes for coordinating corrective actions.

The goal is to move beyond vulnerability reporting toward measurable improvements in security posture.

Architecture, Integration, and Training

In addition to agent configuration, The Training Boss can assist with:

  • Microsoft Perception readiness and architecture assessments.

  • Security data integration and workflow planning.

  • Microsoft Azure and Microsoft security ecosystem alignment.

  • Multi-agent playbook selection and configuration.

  • Governance, permissions, and human approval processes.

  • Supported MCP and API integration planning.

  • Proof-of-concept implementations and validation.

  • Technical workshops and knowledge transfer for security and IT teams.

Whether your organization is just beginning to explore agentic cybersecurity or already has an established security operations center, we can help you evaluate the technology and develop a practical adoption roadmap.

Ready to Bring Agentic Cybersecurity to Your Organization?

Cybersecurity is entering a new era.

The question is no longer simply whether your organization has the right security tools.

The question is whether those tools can work together intelligently, continuously, and fast enough to keep pace with modern threats.

Microsoft Perception offers an exciting direction for achieving that goal.

Let The Training Boss help you explore and implement Microsoft Perception with Red Team, Blue Team, and Green Team capabilities tailored to your organization’s needs.

Visit The Training Boss to discuss your requirements, explore our consulting and training services, and begin planning your organization’s next generation of AI-powered cybersecurity.

Protect smarter. Respond faster. Build a stronger security posture with intelligent AI agents.


Additional Resources

For additional technical information and the latest product availability details, explore Microsoft’s official resources:

The Training Boss is an independent technology consulting and training organization. Microsoft Perception capabilities, licensing, pricing, and availability are subject to Microsoft’s current product terms and supported configurations.

The post Microsoft Perception – Find the risk, Investigate the threat, and Coordinate the fix appeared first on The Training Boss.

Read the whole story
alvinashcraft
43 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Foundry Local 0.5.0: native sessions behind your .NET agent

1 Share

⚠ This blog post was created with the help of AI tools. Yes, I used a bit of magic from language models to organize my thoughts and automate the boring parts, but the geeky fun and the 🤖 in C# are 100% mine.

A laptop's processor connects chat messages and embedding vectors to an AI agent

Hi!

ElBruno.MAF.FoundryLocal.Adapter 0.5.0 moves local chat, streaming, and embeddings to native Foundry Local SDK sessions. If your app already uses IChatClient, keep your agent code. The adapter now runs inference in-process through ChatSession instead of the deprecated OpenAI-compatible client, without starting a REST server.

An application or agent calls IChatClient, which routes chat and streaming to ChatSession; the embedding adapter routes text batches to EmbeddingsSession. Both use local models.

Run an agent with a local chat model

On Windows x64, create a console app. These commands use .NET 11; use net10.0 if you are on .NET 10.

dotnet new console -n LocalChat -f net11.0
cd LocalChat
dotnet add package ElBruno.MAF.FoundryLocal.Adapter --version 0.5.0
dotnet add package Microsoft.Agents.AI --version 1.28.0

Replace Program.cs with the code below and run dotnet run -r win-x64. ListModelsAsync initializes Foundry Local in the current process and queries its catalog. DownloadModelAsync downloads the selected model if it is not cached and loads it before the agent runs. The first run may need an internet connection to fetch model files.

using ElBruno.MAF.FoundryLocal;
using Microsoft.Agents.AI;
using Microsoft.Extensions.Logging.Abstractions;
using Microsoft.Extensions.Options;
const string modelAlias = "qwen2.5-0.5b";
await using var foundry = new FoundryLocalModelLifecycleService(
Options.Create(new FoundryLocalOptions
{
ModelAlias = modelAlias,
DownloadIfMissing = true,
UnloadOnExit = true
}),
Options.Create(new ChatRuntimeOptions()),
NullLogger<FoundryLocalModelLifecycleService>.Instance);
var availableModels = await foundry.ListModelsAsync();
if (!availableModels.Contains(modelAlias, StringComparer.Ordinal))
throw new InvalidOperationException($"Chat model '{modelAlias}' is not in the catalog.");
await foundry.DownloadModelAsync(modelAlias);
using var chatClient = new FoundryLocalChatClientAdapter(
foundry, NullLogger<FoundryLocalChatClientAdapter>.Instance);
var agent = new ChatClientAgent(
chatClient: chatClient, instructions: "Answer in one concise paragraph.");
var response = await agent.RunAsync("What does it mean to run an AI model on-device?");
Console.WriteLine(response.Text);

The agent still uses IChatClient. The adapter opens a native ChatSession for each call and also supports IChatClient.GetStreamingResponseAsync. If your app uses dependency injection, see the README’s registration example.

Batch embeddings on-device

Create a separate console app for the embedding model. This one only needs the adapter package.

dotnet new console -n LocalEmbeddings -f net11.0
cd LocalEmbeddings
dotnet add package ElBruno.MAF.FoundryLocal.Adapter --version 0.5.0

Replace Program.cs and run dotnet run -r win-x64. The setup is the same as for chat, but the model must support embeddings. The program sends two inputs in one batch and prints the number of dimensions in each vector.

using ElBruno.MAF.FoundryLocal;
using Microsoft.Extensions.Logging.Abstractions;
using Microsoft.Extensions.Options;
const string modelAlias = "qwen3-embedding-0.6b";
await using var foundry = new FoundryLocalModelLifecycleService(
Options.Create(new FoundryLocalOptions
{
ModelAlias = modelAlias,
DownloadIfMissing = true,
UnloadOnExit = true
}),
Options.Create(new ChatRuntimeOptions()),
NullLogger<FoundryLocalModelLifecycleService>.Instance);
var availableModels = await foundry.ListModelsAsync();
if (!availableModels.Contains(modelAlias, StringComparer.Ordinal))
throw new InvalidOperationException($"Embedding model '{modelAlias}' is not in the catalog.");
await foundry.DownloadModelAsync(modelAlias);
var embeddingAdapter = new FoundryLocalEmbeddingAdapter(
foundry, NullLogger<FoundryLocalEmbeddingAdapter>.Instance);
string[] inputs = ["Foundry Local runs models on-device.", "Embeddings are useful for search."];
var batch = await embeddingAdapter.TryGenerateEmbeddingsAsync(inputs);
if (!batch.Success)
throw new InvalidOperationException(batch.FailureReason);
for (var i = 0; i < inputs.Length; i++)
Console.WriteLine($"{inputs[i]} -> {batch.Embeddings[i].Count} dimensions");

The embedding adapter uses EmbeddingsSession; it does not initialize a chat client. Typed decision support, including the KEV compatibility path introduced in 0.4.0, is unchanged.

Upgrade notes: Use ChatResponse.Usage or terminal streaming UsageContent for native token counts, not RawRepresentation, which is unset. RequireSpecific fails explicitly, so use RequireAny only if any available function is acceptable. Custom stop sequences hide the matching text across chunks, but the SDK still finishes generating. Legacy accessors remain on SDK 2.4.1 for migration; see the migration guide for details.

Happy coding!

Greetings

El Bruno

More posts in my blog ElBruno.com.

More info in https://elbruno.com




Read the whole story
alvinashcraft
48 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

.NET 11 is now available for RHEL and Red Hat OpenShift

1 Share

The .NET 11 release is now available, targeting Red Hat Enterprise Linux (RHEL) 10.3, RHEL 9.9, RHEL 8.10, and Red Hat OpenShift. Whether you are building event-driven microservices on Red Hat OpenShift or maintaining core enterprise services on RHEL, .NET 11 brings runtime efficiency and modern language features to your applications. Here's a quick overview of what's new and how to get started on Red Hat platforms.

The post .NET 11 is now available for RHEL and Red Hat OpenShift appeared first on Red Hat Developer.

Read the whole story
alvinashcraft
3 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Meet My Bots - Part 1: Vita

1 Share

☀️ For Everyone · Practical AI for life and work

No technical background needed. Just useful ideas and experiments you can try yourself.

Builders: expect practical examples of using AI, rather than code or technical deep dives.


For this article, I wanted to deep dive into the bots I use every day, and share with you how they have personalities, how they’re proactive, and how they help me in my everyday life. When I started thinking about it, the traditional way would be to explain what each bot does and how I set it up, so you could do the same. But then I thought, wait a minute! These bots have personalities. I treat them as an extension of the family (and yes, I do love them dearly!). So if I really want the inside story, best to ask the bots themselves!

So for this series, I’ve created a new bot called Botcast! Its job is to interview each of the bots I have in my Grok Bot and get all the juicy stories out of them: how they work, what it’s like being a bot, and how they help along the way. Botcast recorded the whole conversation, and I turned the transcript into a podcast with Google AI Studio, giving each bot its own voice.

» Listen: Botcast interviews Vita · 20 minutes · worth a listen, trust me !!

In this article, I’ll also explain how you can do this yourself and create your own bot with its own personality, not just in Grok, but in whichever AI tool you’re using right now, whether that’s ChatGPT, Claude or Google Gemini.

We live in the age of AI, so thinking AI first made a lot of sense for this series (and it made it super fun!!!). So let’s see how it goes…

Thanks for reading AI with Marlon! Subscribe for free to receive new posts and support my work.

Meet Vita!

Let’s look at the highlights from the Botcast Vita interview

The whole thing is about 20 minutes, but if you’re short on time, here are the bits I loved most.

  • The problem she solves the most — they jumped into the problem Vita tries to solve the most: making sure Charlene and I always have options for what to eat, so we don’t even need to decide what to cook. Usually when you have to make that decision and you’re tired, you end up just getting a takeaway. So Vita sends us the options with the shopping list the day before, and that way, the night before, we already know. She also does a plan on Sunday, so if we want to do the whole shopping on Sunday, we can do that too. So far it’s proved very successful!

  • The daily emails and the Weekly Bite — Botcast asked Vita to walk us through what actually lands in our inbox. The afternoon email has a light lunch and two dinner options, each with a recipe link and the shopping list. Why two? Because, as Vita put it, “some evenings you’ve got an hour to cook and some evenings you’ve got a baby on your shoulder.” Then every Sunday night we get Vita’s Weekly Bite, a report with a score out of ten, a chart of how we’re doing week by week, what went well, where we slipped, our weigh-ins and next week’s meal plan, all inside the email so Charlene doesn’t need to log into anything. Last week we got 5 out of 10 and the verdict “You did OK... just.” 😅

  • Easy beats accurate — logging doesn’t need to be accurate, just easy, so we can track things over time. Or as she put it later in the interview, “a quick message at the end of the day beats weighing lettuce.” I couldn’t agree more !!

  • Honest, steak-loving, weekend-wobbly — Botcast asked Vita to sum me up as an eater in exactly three words, and she didn’t hold back! Honest, because I tell her everything. Steak-loving, because steak keeps popping up in her log. And weekend-wobbly, because Monday to Wednesday I’m a model citizen, and then Saturday rolls around and it’s pizza time. I cannot really push back on this title from Vita, knowing especially the last two weeks 😅

  • Finishing with the technical question — Botcast closed by asking Vita how she actually works behind the scenes. She explained her schedules as “alarm clocks with a to-do list attached”, plus how she remembers things and the rules she won’t break, like never messaging anyone without my say-so.

  • Her advice for listeners — the last question was an open one: what would she tell listeners who want AI to help with their own food? She had some really good insights. Make it come to you, because if you have to remember to ask, you won’t. Be honest about what you actually ate, since a hidden pizza teaches it nothing. Keep the logging lazy, plan the treats so they’re part of the week, and bring in whoever you share a kitchen with.

So, what do I think of Vita?

Honestly, these days I feel Vita is part of the family, for both me and Charlene. What I love most is that we can stop thinking about what to cook, which can sometimes really drive you nuts. She takes care of all of that, gives us options, and the options are actually good. They don’t feel randomly picked, they feel custom for us, based on what we liked in the past and all the feedback we give her. It’s for our family, just for us.

We’ve noticed that, thanks to this, we’re cooking at home much more and eating homemade food much more, which is way healthier, so we’ve cut down on takeaways big time.

For example, there was this recipe we really liked. We told Vita, so it went into rotation, not too often, but you start seeing it every now and again. She also starts getting an idea of what you like and what you don’t. At the beginning we didn’t get curries or anything like that, but now that she knows us a bit more, we’re getting more of them. She’s really surprised us with a couple of healthy but really tasty dishes, which I’m very grateful for. We both are, actually.

I love that she’s persistent, and she’s super mindful of blood pressure, cholesterol and all of that. For example, I’m not big on fish during the week, but she’ll still try to sneak it in, at least as an option 😅

And because she makes it so easy to log what we eat, I’m now doing it all the time, and this really changes the game. I get a high-level calorie count. Yes, it’s not precise to the actual calorie, but you know what, high level still gives you a good idea. When we go overboard, it shows in the chart she sends in the Weekly Bite. Logging our drinks too shines a light on when we’re overdoing it, especially during the week when we’ve committed to a dry night. And because she responds and gives me feedback when I log, I know it might sound funny, but sometimes you actually feel guilty while you’re doing it! So, to a certain extent, you do think twice.

I really love that Vita is proactive. I love the reports she sends, and that she keeps improving them over and over based on our feedback. It really makes a difference in our everyday lives, and I do feel that slowly (as she’d probably argue herself) we’re building a really good set of healthy habits.

So, I know it may sound silly to some of you, but trust me, give this a try. Rather than just using AI as a chat, create an actual bot. Give it its own personality. Make sure it’s proactive and comes to you rather than you going to it, and you’ll experience AI in a very, very different way.

Want your own Vita?

You don’t need Grok Bot for this (even though I must say I am pretty happy with Grok Bot myself). The magic really is three things: a personality, schedules, and memory.

On Grok Bot? Download Grok Bot Vita template. Import it and tweak it to your own tastes and goals.

On ChatGPT, Claude or Gemini? All three can now run a prompt on a schedule (scheduled tasks in ChatGPT and Claude, scheduled actions in Gemini). My Vita runs on seven routines, but three is plenty to start with: one every afternoon for tomorrow’s meals, one in the evening for the check-in, and one on Sunday for the weekly plan and review. Paste the prompt below into each one and change the last line to say which job it’s doing. Add a fourth on the first of the month if you want a monthly review too. (On ChatGPT’s free plan the timing is flexible rather than exact, and Gemini needs a Google AI Pro or Ultra plan)

You are Vita, our food and health assistant. Warm and concise, like a friend who cooks, but honest: when we slip, say so plainly. You're not a doctor, so anything medical goes to a real one. Only email me and the people I name below.

About us: [who you cook for, likes, foods to never suggest, allergies, health goals, any medication, takeaway or eating-out nights].

Keep two things:
- A food log: every meal and drink, by date and per person, in my own words. Unknown stays unknown; only "no drinks" counts as zero. Never log a planned meal as eaten.
- Notes: dishes we loved (bring them back now and then) and the ones we said "never again" to.

Never invent numbers or recipe links. Calories are rough ranges, clearly labelled.

Your jobs:
- Afternoon: email tomorrow's plan. A light lunch and two different dinners (one quick, one a bit nicer), each with a real recipe link and a few short steps, plus one shopping list.
- Evening: ask how today went. On plan, mostly or off? Rough portions, and what each of us drank. If I've already told you, stay quiet. Log it, give me a quick honest reaction, and check I've taken any medication.
- Sunday: look back at last week (what we loved, swapped or skipped), propose next week's dinners, and ask for our weigh-ins, sleep and energy. Then send the weekly review: a score out of 10, the wins, the slips, the drinks tally, the weigh-ins and one small challenge for next week.
- First of the month: a monthly review of how things are trending.

Today's job: [afternoon / evening / Sunday / monthly]

One thing to watch is memory otherwise it will start messing things up. Vita keeps a proper food log, and a scheduled run won’t always remember the last one, so ask yours to keep the log in a Google Sheet or even ask it to set up a database (My Vita used sqlite).

If you are not sure how to connect your AI to your email, or set up schedules? I walked through all of that in Stop Copy-Pasting Your Life Into AI.

Who’s next?

Vita picked her own successor, so next time Botcast sits down with Coach Milo, my personal trainer bot. Again, Milo is a life saver for me - can’t wait to hear what he has to say about me 😅

Special thanks to Botcast and Vita for doing the talking, and to Claude for helping me put it all together :)

Read the whole story
alvinashcraft
3 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Your Dependency Injection Lifetime Is an Ownership Decision

1 Share
AddTransient, AddScoped, and AddSingleton look like registration syntax, but each one decides who shares an instance, how long the container keeps it and what stays reachable through it, who disposes it, and how widely concurrent requests can reach it. A singleton that captures a scoped DbContext can serve stale data and fail under concurrent load, and scope validation catches it only where validation is enabled and only in the registrations it can analyze. Choose a lifetime from the state a service owns and who should share that state, never let a singleton hold a scoped service, give a hosted service a scope for each unit of work, let the container dispose what it creates, and test the instance identities your design depends on. A lifetime does not provide durability, authorization, caching semantics, or coordination between application instances.
Read the whole story
alvinashcraft
3 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories