Urgent.News

What's breaking now, across thousands of outlets.

AI

How I built Everbind: keeping project commitments alive across schedule revisions with Gemini and Google Cloud

This article was created as part of Everbind’s submission to the All Things Agentic Hackathon. The activity changed. The commitment didn’t. A routine schedule revision can retire Activity A and replace it with Activities B and C. A schedule comparison can show that A was retired and B and C were added, but it does not by itself establish which new work inherits A’s existing commitment. That…

This article explains how to build a production-ready AI agent using PHP, MySQL, Gemini Flash, and cPanel. The author demonstrates that such a system can be practical, understandable, and cost-effective, even for developers who are not working on a modern stack with Python, Docker, and cloud infrastructure.

The agent system consists of an HTTP endpoint that receives user requests, sends context to Gemini Flash, and uses the model to decide whether to request a tool or provide a direct answer. The agent loop continues until the model produces a final answer. This design focuses on the orchestration between the model, tools, and memory, which is often missing in other tutorials.

The system uses PHP to handle HTTP requests and the agent loop, MySQL to store chat memory and saved data, Gemini Flash to decide whether the agent should answer directly or use a tool, and cPanel to deploy the system on shared hosting. The author emphasizes that the agent is not a monolith but a loop that receives user input, sends context to the model, lets the model request a tool if needed, executes the tool, and sends the result back until the model produces a final answer.

To build the system, the author provides a project structure and a MySQL database setup with two tables: one for conversation history and one for saved notes. The PHP code includes functions for connecting to the MySQL database, making Gemini Flash API calls, and handling function calls. The author also stresses the importance of keeping the system understandable and debuggable by separating concerns and using a simple database schema.

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

This story

This is one outlet's version. Read the fullest account.

Read the original at dev.to →

More in AI

Why more context makes your AI answers worse

Your model says it has a one-million-token context window. Its real working memory is a lot smaller than that. On long-context benchmarks, models start failing well below the number printed on the…

  • Attention mechanism determines token focus; larger context splits focus, reducing performance
  • Important information near beginning and end of prompt performs best, middle performs worst

Stop Rewriting Legacy Systems: Use AI to Understand Them First

TL;DR: AI should not help us rewrite legacy systems faster, it should help us understand them better, modernize them safely, and design stronger architectures for the future.

  • Emphasize understanding legacy systems before modernization.
  • AI helps discover business knowledge in legacy code.
  • Incremental modernization is safer than large-scale rewrites.

More from Monday 31 August →