Skip to main content

​
Overview

Task tracking may not always be desirable. For example, when you’re launching a new sub-agent with simple tasks, or running test conversations, the session may not need to track tasks. By default, all sessions have task tracking enabled. When enabled, every message sent to a session will be monitored on agent planning and user feedback.

​
When to Disable Task Tracking

Consider disabling task tracking in these scenarios:
  • Testing and Development: When you’re testing your agent and don’t want to clutter your task logs
  • Simple Conversations: For basic Q&A sessions that don’t require task analysis
  • Sub-agents: When running lightweight sub-agents for simple operations

​
How to Disable Task Tracking

You can disable task tracking by setting the disable_task_tracking parameter to true when creating a session. 
from acontext import AcontextClient

client = AcontextClient(api_key="sk_your_project_token")

# Create a session with task tracking disabled
session = client.sessions.create(
    disable_task_tracking=True
)

print(f"Session ID: {session.id}")
print(f"Task tracking disabled: {session.disable_task_tracking}")

​
What Happens When Task Tracking is Disabled

When disable_task_tracking is set to true:
  • ✅ Messages are saved: Messages sent to the session are still saved to the database normally
  • ❌ No automatic tasks: No automatic task extraction.
  • ❌ No task analysis: The session won’t appear in task-based analytics

​
Best Practices

  1. Use selectively: Only disable task tracking when you specifically don’t need it
  2. Document your decision: Make it clear in your code why task tracking is disabled
  3. Testing environments: Consider disabling task tracking in test/development environments