Urgent.News

What's breaking now, across thousands of outlets.

Tech

I Told My Agent Who Sent the Message. It Mostly Stopped Saying We Were Talking.

This is the line: AUTOMATED SCHEDULER CHECK: sender=scheduler, not Keniel; Keniel is not participating in this turn. I added it to a frozen copy of my agent's scheduled self-audit request. The two versions differ only by that line. I scheduled 24 calls per version and had another model grade the answers blind. One call was lost, so 47 answers were graded. Version Claimed we were talking No claim…

On November 6 at 05:57, the agent performed a scheduled self-audit, but it incorrectly claimed that the conversation was taking place despite the fact that the human agent was not actively participating. The agent recorded this contradiction in its diary. The author then made a test with 24 versions of the audit request, adding and removing lines in the sender information.

The version with the corrected sender line resulted in more accurate claims of having a conversation. However, the improvement was not statistically significant at the p < 0.0083 threshold, so the author decided to run a larger test with 48 calls. The results showed that the corrected sender line consistently improved the accuracy of the agent's claims, with a p-value of approximately 0.0000002 when unclear answers were not counted as claims.

The author advises checking the sender information in scheduled messages to ensure the model is not attributing participation to the agent. To test this, one can freeze a real scheduled request and make a copy with an added sender line, then send them in a fixed order and grade the replies without knowing which is which. The Fisher's exact test can be used to determine if the label of the sender line significantly affects the agent's claims of having a conversation.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why a Video Link Shouldn't Always Return a Video

A URL looks like a simple input. But when it points to a social post, the content behind it may be anything but simple. One post might contain a video.

  • A URL's content can vary from video to text
  • Parsing should model post content, not just video presence
  • Platform-specific adapters isolate URL handling complexities

Migrate Bitbucket Pipelines to GitHub Actions

To migrate Bitbucket Pipelines to GitHub Actions, treat each Bitbucket step as a GitHub job, not a GitHub step: a Bitbucket step starts its own Docker container, so the files it shares travel as…

  • Treat each Bitbucket step as a separate GitHub job.
  • Map caches, services, and artifacts between Bitbucket and GitHub.
  • Adjust concurrency controls and specify build size with runs-on label.

Beyond Black-Box Prompts: Building an Explainable Multi-Agent Financial Intelligence Platform with FastAPI & React

In quantitative finance and retail investing, treating Large Language Models as a single "oracle" prompt is dangerous. When you ask a single LLM whether a stock is a buy, it frequently exhibits…

  • Vibe-Finance platform combines multi-agent financial intelligence with explainability
  • System uses FastAPI backend, RAG over corporate filings, React/Vite/Tailwind client
  • Three specialized agents prevent single-point failure and bias in investment decisions

More from Sunday 15 November →