```typescript theme={null}
// Example custom tool usage
const result = await agentbase.runAgent({
message: "Get customer data for user ID 12345",
tools: ["get_customer_data"], // deployed tool name on the agentbase app
});
```
## Key Points
* Tools are selected automatically based on your task
* No manual configuration or tool specification required
* Computer environments created when needed for stateful operations
* All tools work together seamlessly in workflows
# Contact Support
Source: https://docs.agentbase.sh/contact-support
Get help and connect with our community
## Get Help
## Before you begin
* [Agentbase account](https://base.agentbase.sh/sign-up) with credits
* Node.js 18+ installed
## What are Traces?
Traces are comprehensive execution logs that capture every step of your agent's workflow, including:
* **Agent Initialization**: When the agent starts processing a request
* **Agent Steps**: Each reasoning step the agent takes
* **Tool Usage**: When and how the agent uses tools
* **Tool Responses**: Results returned from tool executions
* **Agent Responses**: Final responses generated by the agent
Each event in the trace includes:
* Timestamp of when it occurred
* Duration of execution
* Detailed information about inputs and outputs
* Status (completed, in progress, failed)
## Accessing Traces
Navigate to the **Traces** page in your Agentbase dashboard under the **Improve** section. Here you'll find:
1. **Sessions**: A list of all agent execution sessions with unique session IDs
2. **Traces**: Individual agent runs within each session
3. **Timeline**: A chronological view of all events in a trace
## Using Traces for Debugging
Traces are invaluable for:
* **Performance Optimization**: Identify slow steps or tool calls by examining execution durations
* **Error Diagnosis**: Pinpoint where failures occur in your agent's workflow
* **Behavior Analysis**: Understand the reasoning path your agent takes
* **Tool Usage Monitoring**: See which tools are being called and how often
* **Response Quality**: Review agent responses and the context that led to them
## Trace Events
### Agent Initialization
Records when the agent begins processing a request, including the initial prompt and configuration.
### Agent Steps
Each step represents a discrete reasoning action by the agent. Steps are numbered sequentially (Step 0, Step 1, etc.) and show:
* The agent's thought process
* Decisions about which tools to use
* Planning for next actions
### Tool Events
Tool usage is captured in two events:
* **Tool: \[name]** - When a tool is invoked, showing the tool name and parameters
* **Tool Response: \[name]** - The result returned by the tool execution
### Agent Response
The final response generated by the agent after completing all necessary steps.
## Best Practices
{item.text}
{item.text}