Skip to content
This repository was archived by the owner on Feb 19, 2026. It is now read-only.
This repository was archived by the owner on Feb 19, 2026. It is now read-only.

Suggestion: Support .env file for securely managing Composio and TAI API keys #3

Description

Hi team,

Thank you for your work on this project — it’s been fun to explore!

I’ve created a fork of grok-cli and added support for loading the Composio and xAI API keys from a local .env file instead of requiring manual input via CLI.

This approach improves security and developer experience by:
• Avoiding key exposure in command history
• Enabling easier automation or local reuse
• Aligning with .env usage patterns common in CLI tooling

I’m happy to open a pull request if this change is of interest.

Environment example:

COMPOSIO_API_KEY=your-composio-key
xAI_API_KEY=your-xai-key

here is the fork: https://github.com/emanuelgrammenos/grok-cli

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions