[SECURITY] Audit logging for compliance and tracking

[jwesleye]

Feature Description

Comprehensive audit logs of all agent actions for compliance and debugging.

Problem/Motivation

Enterprises need audit trails for compliance. Debugging requires history.

Proposed Solution

chat_loop myagent --audit-log

# Logs to ~/.chat_audit/:
# - All queries and responses
# - Tool calls with arguments
# - Files accessed
# - Timestamps and user
# - Tokens and costs

Export formats:

• JSON for analysis
• CSV for spreadsheets
• Syslog for SIEM

Benefits

• Compliance (SOC2, HIPAA, etc.)
• Debugging
• Cost tracking
• Security monitoring

Priority

• Critical
• High
• Medium
• Low

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.

If this issue is still relevant, please:

• Comment to keep it open
• Remove the "status: stale" label
• Provide additional information or updates

Thank you for your contributions!

[jwesleye]

Closing as out of scope for this AWS Strands CLI tool.

This is an enterprise/compliance feature that adds significant complexity for a use case that doesn't align with a simple CLI tool.

For users with security/compliance requirements:

• Implement security controls at the infrastructure level
• Use enterprise agent platforms with built-in audit features
• Review saved conversation files manually (stored in ~/.agent-conversations/)

This CLI tool is focused on providing a straightforward interface for AWS Strands agents, not enterprise security features.

Thank you for the suggestion!