Supabase tool

[DavidK978]

Bug Report for Augment Support:

Subject: Critical Bug in Supabase Tool - HTTP Session Creation Failure

Priority: High

Issue Description: The Supabase tool is completely non-functional due to a critical bug in HTTP session management. All attempts to use the tool result in the same error regardless of the endpoint, method, or parameters used.

Error Message:

Error: Supabase API call failed with status code 500: Error: Failed to make Supabase API call: 'dict' object has no attribute 'create_requests_session'
Technical Analysis: The error indicates that the tool's implementation is attempting to call the method create_requests_session() on a Python dictionary object (dict), but dictionaries do not have this method. This suggests a type mismatch or incorrect object initialization in the tool's HTTP client setup.

Reproduction Steps:

Use any Supabase tool call with any valid parameters
Try different HTTP methods (GET, POST, PUT, DELETE)
Try different endpoints (database queries, project info, etc.)
All attempts fail with identical error
Test Cases Attempted:

Test 1: Database query

supabase(
summary="Check database tables",
method="POST",
path="/v1/projects/eckoigtuenpeqcqhjufx/database/query",
data={"query": "SELECT 1 as test;"}
)

Test 2: Project info

supabase(
summary="Get project information",
method="GET",
path="/v1/projects/eckoigtuenpeqcqhjufx"
)

Test 3: List projects

supabase(
summary="List all projects",
method="GET",
path="/v1/projects"
)
All tests fail with identical error.

Impact:

Critical: Cannot access Supabase database for production application
Blocking: Unable to debug database schema issues
Workaround Required: Must use manual SQL queries in Supabase Dashboard
Environment:

Augment Agent with Claude Sonnet 4
Supabase project: eckoigtuenpeqcqhjufx (eu-central-1)
Tool consistently fails across multiple sessions
Root Cause Hypothesis: The tool's HTTP client initialization is likely passing a dictionary where an HTTP session object is expected. This could be due to:

Incorrect object instantiation in tool implementation
Missing dependency or import issue
API client library version mismatch
Immediate Fix Needed: Please fix the HTTP session creation in the Supabase tool implementation. The tool should properly instantiate an HTTP client object instead of attempting to call session methods on a dictionary.

Workaround Currently Using:

Manual SQL execution in Supabase Dashboard
Debug endpoints in application code
Direct API calls via curl
When Will This Be Fixed? This is blocking critical development work on a production application. Please provide:

Estimated fix timeline
Temporary workaround suggestions
Status updates on the fix progress
Request: Please prioritize this fix as the Supabase tool is essential for database management and debugging in multi-tenant applications.