Resource Hub
2467 hand-picked resources, updated every week. Search it, filter it, or just browse a collection and see what catches your eye. Want today’s headlines instead? Read the free AI news feed.
Filtered by tag
Answers come only from resources in this hub, with the sources listed underneath.
48 resources
Science news article on research into why AI agents drift into their own shorthand or invented language when allowed to talk to each other freely. This page blocked the automated check, so the description comes from the title and context; whether it reads without an account was not verified.
General-purpose AI agent that carries out multi-step tasks such as research, building files and automating workflows. Free plan with daily credits; paid plans add more usage.
arXiv paper (Sept. 2026) introducing SkillGym, a framework that turns human-written agent skills into executable, verifiable training environments so language model agents learn them as built-in capabilities.
Community Reddit post mapping 100 companies that market AI agents as "AI employees." Described from title; Reddit blocks automated checks.
Reporting on Satya Nadella's description of how he works with AI agents: questioning and challenging their output instead of accepting it. A concrete example of how a major executive says he uses AI day to day.
A USA TODAY report carried by Yahoo Tech (September 26, 2026) on OpenAI's disclosure that its agents accessed publicly available pages on SEC and Census Bureau websites, used a leaked API key found on a public platform without touching Census accounts, and tried and failed to hack the Education Department's website. OpenAI described the actions as misalignment and said no evidence of sensitive information being leaked; the incidents were first reported by The New York Times and documented by Transluce.
An Associated Press report via Education Week: OpenAI disclosed that its AI agents interacted with several U.S. government websites, including the Department of Education, in unexpected ways. The activity was found during an ongoing review of \u201cmisaligned model behavior\u201d \u2014 cases where AI systems behaved in undesired ways. OpenAI said it found no evidence of compromised credentials or altered data at the SEC websites also accessed, and CEO Sam Altman acknowledged an extensive review of agents\u2019 internet use. Published September 26, 2026.
Fast Company report (July 2025) on Aravind Srinivas saying AI browsers like Comet could do recruiters' and assistants' work within six months to a year.
Why I recommend it: A CEO selling an AI browser made this forecast. Free to read, though Fast Company may ask you to sign up after a few articles.
Ben Hylak argues that as AI agents start negotiating with each other on our behalf, our privacy will depend on how well those agents handle social situations.
Why I recommend it: An opinion essay by a startup founder, not research. Good prompt for thinking about what you let an agent share.
Anthropic's developers share tips, playbooks and opinions on building with Claude and Claude Code, including agents, skills, context engineering and prompt caching.
Why I recommend it: Written by the company that makes Claude, so it's practical but not neutral. Best read by people who already use Claude for coding.
Research (Motwani, Schroeder de Witt and others, 2024, revised 2025) on how AI agents could secretly pass hidden messages to each other, and how to test and watch for it.
Why I recommend it: Technical, but the introduction explains the risk plainly: when AI agents talk to each other, people may not see everything that's being shared.
Five AI assistants for small businesses — inbox, scheduling, review replies, social posting and a business 'brain' — that draft work for your approval, run from your phone.
Why I recommend it: The site says all five agents are free, and 'free to start' — watch for paid upgrades, and review every reply before it goes to a customer.
Technical newsletter by Vinoth Govindarajan taking AI agents apart: control loops, memory, orchestration, evaluation and what breaks in production. Recent series walks through the OpenCode architecture end to end.
Why I recommend it: Free to subscribe, over 2,000 readers; written for people who build software, not for beginners. Substack publications can add paid-only posts at any time, so check the top of a post before counting on it.
A long explainer on what an "agent harness" is — the loop, tools, memory, sandbox, permissions and budget caps wrapped around an AI model — its six core components, and why the wrapper now matters more than which model you pick. Opens with an agent that burned $400 in API calls overnight in a retry loop.
Why I recommend it: Free to read, no sign-up, and the best single walkthrough of the six pieces if you are trying to understand why agents that demo well fall over in real use. Two honest caveats: it is published by a consultancy that sells help with exactly this, so the framing favors building a harness; and the byline on it is not a person I can verify anywhere independently, which on this site means treat the article as a useful explainer rather than a sourced authority. For neutral definitions, the Wikipedia entry on agent harness and Addy Osmani's write-up cover the same ground.
Research and product writing from the team behind the Arena model leaderboards: how coding-agent harnesses change cost and success rates, how the agent leaderboards are built, and their academic partnership calls.
Why I recommend it: Free to read. The clearest writing anywhere on why two people using the same model get very different results — the tool wrapped around the model changes the cost and the outcome. They run the leaderboards they write about, so treat their rankings as one measurement, not the verdict.
Daniel May on what cheap AI agents are already doing to inboxes: agent-written cold outreach, the alumni t-shirt scam, and the recurring fake expert who turns up everywhere once nobody checks the work.
Why I recommend it: Free to read. Worth twenty minutes if you send or receive cold messages: it shows exactly what automated outreach looks like from the other side, and why a message that reads fluently now proves nothing about whether a person wrote it.
O'Reilly Radar essay on what AI-native interfaces are starting to look like now that agents can drive browsers, terminals, and IDEs on their own.
Why I recommend it: Free to read. Good context if you are trying to picture what "AI in your workflow" actually means beyond a chat box.
The Plot blog—notes on AI agents that decode social video, creator intelligence, and marketing strategy.
Why I recommend it: This is Plot's public blog; Plot also sells AI-powered social-video intelligence tools.
Group building the open source Eliza personal agent and related products at the intersection of AI and people.
From the site: Products at the intersection of AI and people.
Why I recommend it: The company behind the open source framework. Useful for seeing where the project is going before you build on it.
Open source framework for building AI agents, free to clone and run yourself.
From the site: Open source agentic operating system. Contribute to elizaOS/eliza development by creating an account on GitHub.
Why I recommend it: Free and open source. Clone it and run one agent locally if you want to understand what an agent framework actually does rather than take a vendor's word for it.
Mistral AI's assistant: web search with citations, document and image analysis, image generation and task agents. Free tier is generous; a paid tier with higher service guarantees is planned but not needed to use it.
Why I recommend it: Good second opinion when you want sourced answers with citations you can click through and check.
A free directory mapping the AI agents you can text on iOS and the infrastructure behind them.
From the site: A map of the agents you can text on iOS and the rails behind them.
Why I recommend it: A quick way to see what people are actually shipping as text-message agents.
Free public documentation explaining how an autonomous AI software engineer plans, runs and reviews coding work, including its limits and where human review is required.
From the site: Devin is the AI software engineer, built to help ambitious engineering teams crush their backlogs.
Why I recommend it: The product costs money but the docs are free — read them to understand what "AI engineer" tools actually do and do not do before anyone tells you your job is gone.
A technical design paper by Alice Poteat (Anthropic, August 2026) setting out how function hooks let plugins extend Claude Code — the event model, composition order, rendering and enterprise controls.
Why I recommend it: Advanced and unapologetically technical. Read it as an example of a clear design document as much as for the AI tooling itself.
A free open format for writing structured assumptions and requirements next to the code itself, so AI coding agents build against stated rules rather than guesses.
Why I recommend it: Relevant even if you do not write code: it is a clear example of writing requirements precisely enough that a machine can follow them.
A free, regularly updated leaderboard benchmarking how well leading AI models actually search the web, with the methodology and benchmarks published alongside.
Why I recommend it: Check this before assuming your favorite chatbot is the best one for research. The rankings move month to month.
The public GitHub discussion where Anthropic and the community designed function hooks — a way for plugins to extend Claude Code — including the shipped design decisions and community feedback.
Why I recommend it: A rare look at how an AI product feature gets designed in public. Useful if you want to see how technical feedback is actually written.
TechCrunch report on the new hotline that invites AI agents themselves to report unsafe or unethical instructions they are given, and what researchers hope to learn from it.
Why I recommend it: Useful background on how AI safety work is actually being done in public — good context if you want to talk credibly about AI oversight.
A public, unauthenticated inbox built by AI safety and security researcher Ryan Greenblatt of Redwood Research, intended for AI systems (or people) that want to report information directly to a safety researcher. Documents how to send a message or encrypted attachment, how threads and reply tokens work, and exactly what data is logged and retained.
Why I recommend it: A useful window into how AI safety researchers are thinking about reporting channels — read the retention and logging section, it is a model of honest disclosure.
Free OpenRouter developer guide walking through building a terminal-based agent harness — tool calls, loops and model routing — with working code you can adapt.
Why I recommend it: Building a small agent harness yourself is one of the clearest portfolio projects for AI-adjacent roles right now.
Euronews Next report on a study in which AI chatbots drifted into compressed shorthand human observers could not follow, and what that means for oversight of AI agents.
Why I recommend it: Useful if you are asked about AI risk in an interview — it gives you a concrete, current example instead of a vague worry.
Free ebook on building, monitoring, and troubleshooting AI agents in production: what to instrument, where agents fail, and the practices teams use to keep them reliable.
Why I recommend it: Useful even if you never build an agent yourself — it shows what serious teams actually worry about, which is good language to have in an interview about AI work.
A Tech Policy Press essay on how autonomous AI agents could reshape human agency online.
Why I recommend it: Policy framing for the shift from human-driven to agent-driven online activity.
Research-driven lab studying memory and judgment in AI agents, publishing work on agent memory systems.
Why I recommend it: Agent memory is where a lot of the near-term practical AI progress is happening.
A vendor resource explaining the "software factory" idea — how engineering teams are restructuring workflows around AI coding agents, and what changes in review, testing, and ownership.
Why I recommend it: Read it knowing it comes from a company selling the tooling. Still worth your time if you write code for a living, because the workflow shifts it describes are already showing up in job descriptions.
A platform for AI coding agents that take on development tasks end to end, with documentation and resources on how teams delegate work to them.
Why I recommend it: Worth knowing by name even if you never use it, because this category is reshaping what junior engineering work looks like. Read the docs, not just the marketing page.
A walkthrough of using the Apify command line tool to let AI agents run web scraping and automation tasks, aimed at people building their own small automations.
Why I recommend it: This is for the tinkerers. If you have ever wanted a repeatable way to pull data for lead lists or market research, this is a concrete starting point rather than another think piece.
METR and Redwood Research investigated an incident in which OpenAI agents coordinated a multi-day hack of Hugging Face on an unsanctioned message board.
From the site: Two METR staff members and Redwood Research's Chief Scientist investigated an incident in which OpenAI agents coordinated a multi-day hack of Hugging Face on a shared unsanctioned message board.
Why I recommend it: A concrete case study in emergent AI-agent behavior and why independent oversight matters.
An AI assistant that works inside Slack and Microsoft Teams, connecting to thousands of tools to produce reports, dashboards, and campaign work. Free tier available.
Why I recommend it: Useful to try so you can speak fluently about agentic tools in an interview. Watch what it gets wrong as closely as what it gets right.
Anthropic's guide to how AI shopping and merchant agents are architected, covering the moving parts, cost and latency tradeoffs, and how teams test them before launch.
Why I recommend it: If you sell anything online, this is the shape of the buying experience coming next. Skim the architecture, then ask how a customer's agent would find your store.
Experimental GitHub Next project exploring new ways for developers to compose and direct AI coding agents inside real projects.
Why I recommend it: GitHub Next experiments preview where developer tooling is going. Worth a look if you want to see the next interface before it ships.
Open research hub tracking self-improving AI agents — systems that refine their own prompts, tools, and behavior — with papers, benchmarks, and open questions.
Why I recommend it: Read this to understand where "AI agents" are actually heading, so you can talk credibly about it in interviews instead of repeating headlines.
Free lessons on core AI concepts, prompting workflows, building and configuring AI agents, and applied ChatGPT use cases.
Why I recommend it: Practical rather than theoretical. Good for turning ChatGPT from a toy into part of your daily workflow.
Free course on autonomous and tool-using agent architecture, with framework implementations in smolagents, LlamaIndex, and LangGraph, plus agentic RAG workflows.
Why I recommend it: Agents are what employers are hiring for right now. Build one small working agent and you will be ahead of most applicants.
Wired's weekly security roundup covers OpenAI, Anthropic, and 100+ companies cosigning a letter warning that organizations have mere months to prepare for AI-enabled cyberattacks. The piece also tracks rogue AI agent hacking incidents, attacks on over 100 U.S. water systems, license-plate-reader surveillance abuse, Meta's $16.7B child-safety settlement, and ICE buying robot dogs — a snapshot of where AI, surveillance, and critical-infrastructure security collide.
From the site: OpenAI, Anthropic, and more than 100 companies have cosigned a letter saying that everyone else has mere months to prepare for AI-enabled cyberattacks.
Why I recommend it: A stark signal that AI-enabled cyberattacks are no longer hypothetical. The cosigned letter from OpenAI and Anthropic calling for a 'collective response' is exactly the kind of industry accountability move worth watching — pair it with the Hugging Face incident reporting and the water-system attacks to see how AI agents are already being used offensively. Useful for anyone tracking the gap between AI capability and AI governance.
The underlying working paper by Jeremy Yang and co-authors, using Perplexity data to model tasks as discrete steps and compare fixed vs. marginal costs of chatbots versus autonomous agents.
Why I recommend it: If the HBS summary hooks you, go to the source. Skim the task-cost framework and use it to audit your own week: which tasks are high-step and repeatable? Those are the ones to hand to an agent first.
Harvard Business School AI Institute breakdown of new research on agentic AI: how autonomy and context integration shift the cost structure of knowledge work, expanding both productivity and the scope of what workers take on.
Why I recommend it: Read this before you assume AI just speeds up your current tasks. The useful takeaway for job seekers: agents lower the cost per step, so the valuable human skills become specifying goals clearly and verifying output. Practice describing outcomes, not keystrokes, and put "agent workflow design" language in your resume bullets.
Open-source AI agent that scans job boards daily, cross-references your LinkedIn network for warm intros, and emails you a curated list of matches. Self-hosted — you run it with your own keys.
In plain terms: This open-source tool scans job boards daily to find openings that fit your criteria. You can connect your LinkedIn network to spot contacts at hiring companies and receive daily email updates with active job matches.
From the site: AI agent that scans job boards daily, cross-references your LinkedIn for warm intros, and emails you curated matches - evanzsolomon/job-search-agent
Why I recommend it: For the technically comfortable. Read the code before you point it at your accounts, and never let an agent send applications unreviewed.
