The Work Is Too Specific for Enterprise Software Small and mid-sized teams run on operational content. A law firm receives NDAs, contracts, court filings, and client intake forms. A dental clinic handles referral letters, insurance documents, treatment plans, invoices, and patient forms. An accounting firm processes supplier invoices, receipts, bank statements, and monthly reports. A real estate
The Problem Changed The first version of Iteration Layer was written in TypeScript. That was the obvious choice at the time. The product looked like a normal web app with a normal API surface: accept a request, call a model or processing library, return a response. That shape did not last. Content-processing infrastructure does not behave like a CRUD app once people start using it for real work.
Why Most Crypto Bots Get Sandwiched (And How to Prevent It) If you've ever tried running a crypto trading bot, you've likely encountered the dreaded "sandwich attack." You place a trade, but before it executes, someone else jumps ahead of you, buys the asset, and then sells it back to you at a higher price. Congratulations—you’ve been sandwiched. This isn’t just bad luck; it’s a sophisticated ex
Adding email and calendar tools to an AI agent is mostly an exercise in restraint. Give it 50 commands and the agent gets confused. Give it 5 carefully-chosen ones and it punches above its weight. After running agents against the Nylas CLI for a few months, these are the five I keep coming back to. Each gets exposed via MCP (nylas mcp install) so the agent can call them directly. nylas email send
You ssh'd into a fresh Linux box and you need to send an email. Maybe a backup completed. Maybe a deploy succeeded. Maybe a process crashed and you want a stack trace in your inbox. The traditional path: install Postfix, edit main.cf, configure a smart relay, generate SASL credentials, restart the daemon, and pray nothing else on the box uses port 25. That is the 30-minute path. The 60-second path
I tried to give an AI agent its own email account three different ways. The first two took most of an afternoon. The third took 28 seconds. This is the migration story. The first instinct: just create a Gmail. Free, familiar, works everywhere. Forty-five minutes in: Created a new Google account with a phone number Google would accept (the agent does not have a phone) Configured 2FA, generated an a
Your password-reset flow needs an inbox to test against. Your invitation flow too. Your email-verification gate too. The classic setup is a "[email protected]" alias on a shared mailbox, polling Gmail's API, hoping nothing else lands while the test runs. It is fragile, it leaks state across PRs, and your credentials live in CI. A managed agent account flips this. Each PR gets a fresh inb
My inbox averages 200 messages a workday. Half are noise. A quarter need a fast acknowledgement. The remainder need real work. The split is mostly stable, so the triage rules are mostly stable, so it is a good fit for an LLM. I wired Aider to it. Aider is the AI pair-programming CLI — it has a shell, it can call commands, and it speaks Python natively. Pairing it with the Nylas CLI gives a triage