Known Limitations

Custom Agent is powerful, but as a feature still in beta, there are some limitations worth knowing about.

1. Worker Capability Boundaries

• Workers can only communicate with external services through public HTTP requests
• They cannot access internal network resources or call local services
• Workers execute on demand and exit when done — they cannot maintain persistent connections
• They cannot manipulate local files, run local models, or interact with LAN devices
• In short: Workers give Agents the ability to "travel," but they can only do business via public HTTP — they can't roam freely

2. Permission Stability

• Page access permissions granted to an Agent occasionally disappear without explanation
• On the surface, the workflow appears to be running normally, but it has actually stalled due to permission issues
• You won't receive any error notification — this kind of "silent failure" is harder to detect than an outright error
• It's recommended to periodically check the Agent's execution logs to confirm permissions are intact
• This doesn't happen often, but when it does, you'll need to manually re-authorize

3. Notion Ecosystem Lock-in

• The value of Custom Agent is highly tied to how deeply you've built within Notion
• The Agent's perception, reasoning, and actions all revolve around your Notion workspace
• Outside the Notion ecosystem, an Agent's value drops rapidly
• By comparison, general-purpose agents like Claude Code or OpenClaw don't depend on a specific platform and offer greater flexibility
• If your Notion workspace only has a few scattered pages, Custom Agent's value will be significantly diminished
• Conversely, the deeper your Notion investment (more databases, richer notes), the more resources the Agent can leverage, and the greater its value

4. Still Rapidly Evolving

• Custom Agent is still in Beta — both features and pricing may change
• The good news: more low-cost models are being added, and costs are expected to decrease