The market loves specialized agents. A mail agent that reads your inbox. A code agent that writes your functions. A news agent that summarizes your feeds. Each one trained for a narrow task.
It sounds efficient. And for a fixed, well-defined context it can work well. But when your context is constantly changing — new projects, shifting priorities, evolving relationships across multiple businesses — specialization starts to crack.
A mail agent reading your business emails doesn't understand your business. It processes text, but it doesn't know your vendors, your margins, your ongoing negotiations. A code agent doesn't know why you're building what you're building — it writes functions in isolation, missing context that would have changed the approach entirely. Each agent sees a sliver. None of them see the whole picture.
I found that if you give a capable AI the right context and clear rules, it can handle almost anything. You don't necessarily need a different agent for each task — you need one AI with deep vertical knowledge and well-defined norms.
Think about how you'd work with a trusted person in a company. You don't have a "spreadsheet person" and an "email person" and a "meeting person." You have someone who understands the business and can handle whatever comes up. That person is effective precisely because they have the full picture — not because they're specialized.
EIDARA treats agents as documents, not as programs. A file called agent-librarian.md contains the complete librarian protocol. Any AI that reads it becomes the librarian — Claude, GPT, DeepSeek, doesn't matter.
To share an agent, you share a file. To modify an agent, you edit a file. To create a new one, you write a file. The intelligence lives in the document, not in who executes it. This kills platform dependency and lets any AI step into any role, as long as it has the right context.
I manage 4 businesses with one AI that has complete context, not six agents that each see a sliver. It can answer questions about operations, review a contract, draft content, or summarize a strategy document — because it knows the full picture.
In my experience, specialization is often a workaround for lack of context. Fix the context problem, and a lot of that specialization becomes unnecessary.
EIDARA is the open-source project behind this approach. GitHub · Website