Integrations / CrewAI
Keep your crew. Watch it work.
Sulcus instruments your crew’s normal kickoff calls. CrewAI still owns the crews, agents, tasks, tools, delegation and output.
Available nowSulcus adds
Visibility across the kickoff.
- Crew, agent and task activity that CrewAI exposes.
- Model and tool events from CrewAI’s hooks and event bus.
- Reported token usage and an optional per-run token limit.
- Stop control and a retained history of every run.
CrewAI keeps
The crew and its work.
- Crew and task definitions, processes, delegation and planning.
- Agent selection, prompting and tool invocation.
- The crew’s result and anything your app stores.
- Side effects your application or providers have already started.
How it attaches
Around your normal kickoff calls.
When a project selects CrewAI, Sulcus activates its instrumentation in the run’s container and wraps kickoff and akickoff. Your application kicks off its crew as usual.
OBSERVATION BOUNDARY- Runs the workflow
- CrewAI
- Instrumented calls
- Crew kickoff / akickoff
- Event source
- CrewAI hooks and event bus
- Not captured
- Prompts, model outputs, tool payloads
Boundaries
What this integration doesn’t do.
The workflow tree is shallower than for LangGraph, because CrewAI exposes less structure. Sulcus doesn’t create agents, assign tasks or choose delegation paths.
Sulcus Cloud doesn’t offer tool permission settings for crews. Stopping a run and the token limit can’t undo a provider request or side effect that has already started.
Get started
Run your first agent in Sulcus.
Point Sulcus at a public Git repository, pick the entrypoint and framework, and watch the run live.
Python · public HTTPS Git repos · LangGraph, CrewAI, OpenAI Agents SDK
