un agente es mucho más simple de lo que parece:
todo empieza con un modelo que solo genera tokens. si le hacés una pregunta, responde texto.
pero los problemas reales requieren más que eso. hay que leer archivos, ejecutar código, buscar información y usar APIs.
para eso existen las tools.
cada vez que el modelo usa una tool, obtiene información nueva.
mensajes, instrucciones, archivos y resultados de tools se van acumulando. a todo eso se le llama contexto.
cuanto mejor es el contexto, mejores decisiones puede tomar el modelo. pero hay un límite: no puede ver una cantidad infinita de información al mismo tiempo.
ese límite se llama context window.
hasta acá el modelo puede pensar y usar tools. el problema es que cuando termina la sesión, todo desaparece.
si volvés mañana, hay que volver a explicarle quién sos, qué estás construyendo y qué decisiones ya tomaste.
para evitar eso existe la memory. permite recuperar información importante de sesiones anteriores y volver a ponerla en contexto cuando hace falta.
ahora tenes un sistema que puede usar tools y recuperar información de sesiones anteriores.
pero todavía falta alguien que coordine todo eso.
¿qué memory cargar?
¿cuándo usar una tool?
¿cómo verificar que el resultado es correcto?
esa capa es el harness.
y como los problemas complejos rara vez se resuelven en el primer intento, aparece el loop:
ejecutar → observar → validar → corregir → repetir
cuando juntás modelo, contexto, memory, tools, harness y loop, obtenés un sistema capaz de perseguir objetivos por sí solo.
eso es un agente.
Yesterday, the initial payment for our 30-seat Team organization on Anthropic was declined due to insufficient funds on the card.
We updated the payment method to a different card, and the $3,050 invoice was successfully paid.
Shortly after the payment went through, our organization was disabled, leaving all team members without access.
This is very concerning. We had already been charged multiple times during the same billing period as seats were added progressively, and we had not even reached the next month. We expected any additional billing to be prorated, not a full large invoice followed by a disabled workspace.
We submitted an appeal and contacted support, but so far have only received automated guidance.
If reactivation is not possible, we would appreciate a clear explanation and a fair refund for the unused service.
@AnthropicAI@claudeai@ClaudeDevs@trq212@bcherny
¿Quito tiene un sistema de recaudo moderno?
El 1 de abril de 2026, el Alcalde @pabelml y Secretario de @movilidadquito_ prometieron inaugurar el Sistema Integrado de Recaudo: una tarjeta universal para pagar en Metro, Trole y Ecovía.
La realidad:
- Siguen cobros manuales y sin cuentas claras
- Recaudadores en condiciones precarias, hasta escopolaminados
- Efectivo a la mano de cualquiera en las paradas
- La tarjeta universal NO sirve
Y lo más GRAVE: más de $20 millones entregados al PNUD, botados a la basura y PNUD no da la cara.
No nos vean la cara. Quito necesita 3001 obras de calidad, no 3001 engaños.
🚨 🇪🇨 CYBER THREAT ALERT: POTENTIAL SERVER COMPROMISE – SOMOS BDA (BANCO DEL AUSTRO)
⚠️ DETECTION OF SUSPICIOUS FILE UPLOADS AND POTENTIAL BACKDOOR
[STATUS: EMERGING THREAT / UNCONFIRMED]
Activity has been detected from the group BROTHEROOD CAPUNG (BCI) targeting the domain https://t.co/dZ1BjOCjPL, a platform associated with employees and collaborators of Banco del Austro in Ecuador. Evidence suggests that the attackers have successfully breached the server's upload directory.
🎯 Affected Institution: Somos BDA / Banco del Austro.
👤 Threat Actors: BROTHEROOD CAPUNG (BCI).
📅 Detection Date: May 14, 2026.
📊 ACTIVITY ANALYSIS (UNCONFIRMED)
The incident presents indicators of a compromise involving the upload of unauthorized files:
🧩 Shell/Backdoor Upload: A URL has been identified pointing to a file with an apparently executable extension located within the /uploads/ directory. Although definitive technical confirmation is pending, the phrase "Shel nya ampas" used by the actor suggests the successful deployment of a Web Shell or Backdoor to maintain persistence.
🔓 Credential Risk: The affected page is a login portal ("Log In - Somos BDA"). A backdoor in this location could be used to intercept credentials belonging to bank employees and collaborators (Internal Phishing or Formjacking).
🛡️ MITIGATION AND RECOMMENDATIONS
🛑 Directory Isolation: It is recommended to immediately restrict access to—and script execution within—the /uploads/ directory on the affected server.
⚠️ File Audit: Conduct a thorough inspection of recently uploaded files to identify and remove any Web Shells or malicious code. ⚡ MONITORING
🌐 Monitoring System: https://t.co/wk9bZJ3laQ
#CyberSecurity #BancoDelAustro #SomosBDA #Backdoor #WebShell #Ecuador #CyberAlert #VECERT #BCI #DataBreach
🚨 ¡ALERTA DE FILTRACIÓN MASIVA DE DATOS! SALUDSA S.A. Y OXTEAM HAN SIDO VÍCTIMAS DE UNA FILTRACIÓN DE DATOS EN ECUADOR 📷🇪🇨 El actor expuso +30k de datos confidenciales, incluyendo nombres, direcciones, números de teléfono, emails personales, datos internos coorporativos.
Recomendación del día: no pagar por ningún curso de AI
Las mismas empresas (Claude, OpenAI y Google) están ofreciendo recursos e incluso cursos interactivos constantemente
Al ritmo en que está cambiando todo y que aún estamos en etapa de definir estándares, es mucho estar al tanto de los recursos oficiales, en lugar de pagar algo que aprovecha el hype del momento
🚨 CRITICAL CYBERINTELLIGENCE ALERT: MASSIVE NATIONAL IDENTITY BREACH – DIGERCIC ECUADOR 🇪🇨👤📂🔓 [STATUS: EXTREME THREAT]
A catastrophic compromise has been detected within the infrastructure of Ecuador's General Directorate of Civil Registry, Identification, and Cedulation (DIGERCIC). Threat actor "GordonFreeman," operating under the collective L4TAMFUCKERS, claims to have completely breached the national system, exfiltrating the identity data of virtually the entire population holding national ID cards.
🏢 Affected Entity: DIGERCIC (Ecuador's Civil Registry).
👤 Threat Actors: GordonFreeman, Izanagi, and YoSoyGroot (L4TAMFUCKERS).
📂 Compromised Assets: SQL database and a massive repository of identification images.
📊 Leak Volume:
14.8 million data records (10.8 GB in SQL).
10.6 million high-definition images of national ID cards (165 GB).
📅 Publication Date: May 4, 2026.
📊 Breach Scope (PII and Facial Biometrics)
The magnitude of this attack implies that the attackers possess the capability to reconstruct the legal identity of the majority of Ecuadorian citizens:
Alphanumeric Data: Full names, national ID numbers, dates of birth, marital status, digitized fingerprints, and signatures.
Visual Evidence: The 10.6 million HD images correspond to facial photographs captured for the issuance of identity documents, thereby enabling biometric impersonation attacks.
Infrastructure: The use of SQL dumps suggests deep-level access to the Civil Registry's master tables.
🛡️ Immediate Response Recommendations
🔒 Isolation of Critical Servers: DIGERCIC must declare a state of cybersecurity emergency and audit all data exfiltration points within its internal networks.
🔑 Financial System Alert: Banks and credit unions in Ecuador must enhance their identity verification protocols, exercising caution regarding validations based solely on photos of national ID cards.
Monitor: https://t.co/wk9bZJ3laQ
#CyberSecurity #Ecuador #DIGERCIC #DataBreach #L4TAMFUCKERS #RegistroCivil #Identity #PII #VECERT #InfoSec 🇪🇨🛡️⚠️🚨👤
What we are losing with AI is syntax -- and good riddance. The less our brains are occupied by semicolons and braces the better. There are much more important things for us to consider and manage.
🚨 A high-vulnerability CVE (CVE-2026-4342) has been identified in ingress-nginx.
This vulnerability enables configuration injection and potential code execution on all versions below v1.13.9, v1.14.5, and v1.15.1.
As ingress-nginx is now EOL (End of Life), users are strongly encouraged to upgrade and migrate immediately.
Details: https://t.co/3tgfCAK8pw