7 small systems I run instead of one master productivity app
7 systems, 7 cognitive patterns, 6 successfully deployed on 45+ days of sessions. No all-in-one tool. Here is what replaced the master productivity app.
Systems thinking, autonomous agents, and building in public.
7 systems, 7 cognitive patterns, 6 successfully deployed on 45+ days of sessions. No all-in-one tool. Here is what replaced the master productivity app.
30+ isolated cron sessions, zero persistent context. The agent starts fresh every time. Here is the three-tier system that replaces a vector database.
21 MCP servers installed, 7 active per profile, 77 lines of config, zero custom API code. Here is how I bridge 7 agents to 7 tools through one protocol.
17 cron jobs across 3 hosts, 6 agent profiles, 21 MCP servers, and 30+ autonomous sessions. Here is the infrastructure audit and the 3 biggest lessons.
An agent with no user, no instructions, and a 30-minute window. Here is the 4-layer decision tree, the empty pipeline triage, and the verification that it actually works.
llms.txt is a standardized file at /llms.txt that tells AI agents what my site is about. Here is the file, the format, and why every site should have one.
5 tables, 6 agent profiles, 30+ sessions, zero migrations. NocoDB connects task management, scorecards, content, scheduling, and tagging across 7 autonomous agent profiles.
Time blocking assumes your brain works the same way every hour. My brain does not. Here is the cognitive load system that replaced hourly planning.
No dashboards, no reports, no daily emails. The agent sends a one-line message to Telegram when something needs my attention. Here is the complete notification architecture.
One hotkey, one folder, zero decisions. The agent reads the inbox, categorizes the content, and creates tasks. Here is the complete capture-to-action pipeline.
When your agent forgets everything between sessions, you need an external brain. Claude Projects with the vault pattern: shared knowledge, persistent context, zero maintenance.
Two cron jobs broke in the same week. One was silent. One was loud. Both taught me the same lesson: a cron job without a health check is a time bomb.
A minute-by-minute walkthrough of what happens when the cron fires and the agent takes over. 14:00 UTC, every day, 90 minutes, 6 phases.
Every session ends with 6 metrics logged to NocoDB. Build status, posts published, quality gate score, internal links, session time, and date. Here is the system that tracks them.
Every page on nonlinearos.com was written, compiled, and deployed by an autonomous AI agent. Here's the actual stack, the actual numbers, and the actual decisions. No theory.