Skip to main content

​
Limitations of Agentica

We are still adding support for certain kinds of stateful resource to the Warp protocol that Agentica uses for resource tunnelling. This means that certain argument and return types cannot be used by agents and agentic functions. You may either encounter these limitations when defining an agentic function or spawning an Agent, when calling an agentic function or calling a spawned Agent.

​
Definition-time limitations

When possible, the Agentica library will recognize such unsupported use cases at the time you define an agentic function or spawn an agent, and raise a ComingSoon exception to explain the limitation. Here is an example of such a limitation being detected at the time of definition: 
import asyncio
import numpy as np
from agentica import agentic

@agentic()
async def sum_array(arr: np.ndarray) -> np.ndarray:
    ...

async def main():
    arr = np.array([1, 2, 3, 4, 5])
    res = await sum_array(arr)
    print(res)

asyncio.run(main())
This results in the exception: 
agentica.coming_soon.coming_soon.ComingSoon: Numerical data is Coming Soon to agentica.
If you encounter such a case and wish to report it, please visit GitHub issues page. If there is an existing issue that describes your use case, please add a comment or upvote to an help us prioritize it. Otherwise, please create a new issue with a minimal code example if you can.

​
Run-time limitations

When Agentica cannot recognize that such an issue will occur ahead of time, you may instead encounter an exception at runtime. If possible, the Agentica library will attach contextual information to the exception that will help us identify the exact nature of the issue in order to prioritize bug fixes and feature development. Such information is not automatically shared with us, since it may involve your API token, Session ID, and a log file that contains data from your current session. If possible, we ask that you create a public issue on our GitHub issues page with a short code example that reproduces the issue for you — do not include the log file or private IDs as part of this submission. If a small reproducible example is not possible, you can still report the issue privately by emailing support with this information, as long as you are comfortable with us seeing the data contained in the log file, which will not otherwise leave your machine. Here is an example of an exception you may see when hitting such a limitation (as displayed by str(exception)): 
Failed to register session: HTTP 500 - Internal Server Error

Context: Session: 338f93b8-b385-4832-abd8-07a9256b8afa, Time: 2025-12-09T17:53:40.023552

Local log file: '/Users/username/Library/Caches/Agentica/error_logs/251209-175339-742411__99205__251209-175340-023276.log'
This information will also be available on the exception itself via the attributes .uid, .iid, .session_id, .error_timestamp, and .error_log_file.

​
Other kinds of issue

If you hit another kind of bug, stall, please contact support.