feat: Add AdaL as a login/auth provider in ForgeCode

[chindris-mihai-alexandru]

Summary

ForgeCode (formerly Forge) is an open-source AI-enhanced terminal development environment that supports multiple LLM providers. Currently, AdaL/SylphAI is not listed as a built-in provider in ForgeCode's provider registry.

Proposal

Add AdaL (SylphAI) as a first-class provider in ForgeCode so users can access AdaL's models directly from the ForgeCode terminal. This would:

1. Increase AdaL's reach — ForgeCode users could select AdaL as their provider via forge provider login adal
2. Enable model access — Users with AdaL API keys could use SylphAI's models through ForgeCode's interface
3. Cross-tool compatibility — Developers who use both AdaL CLI and ForgeCode could share credentials

Implementation

I've created a PR on the ForgeCode fork that adds AdaL as an OpenAI-compatible provider:

• Provider ID: adal
• API endpoint: https://api.sylph.ai/v1/chat/completions
• Models endpoint: https://api.sylph.ai/v1/models
• Auth: API key (ADAL_API_KEY)
• Response type: OpenAI-compatible

ForgeCode PR: https://github.com/chindris-mihai-alexandru/forgecode/pull/new/feat/adal-provider

Questions for the AdaL team

1. Are the API endpoints (api.sylph.ai/v1/...) correct for external integrations?
2. Is there a public API documentation page for the model endpoints?
3. Would you consider adding ForgeCode as a supported integration in AdaL's docs?
4. Are there specific model IDs that should be hardcoded vs. fetched dynamically?

References

• ForgeCode GitHub
• ForgeCode Custom Providers
• AdaL Models & Billing

🌸 Generated with AdaL

[chindris-mihai-alexandru]

Update: API Key Access Needed for Third-Party Integrations

I've completed the ForgeCode integration (upstream PR: antinomyhq/forgecode#2868) and tested the local build — AdaL shows up as a provider and the login flow works. However, I discovered that the AdaL dashboard doesn't currently expose a raw API key for use with third-party tools.

Current Situation

• AdaL CLI uses browser-based OAuth for authentication (no API key exposed)
• The AdaL Pro dashboard at sylph.ai doesn't have an API key section
• ForgeCode's provider system needs either an API key or an OAuth flow to authenticate

What Would Unlock This Integration

Any of these would work:

1. API Key on Dashboard (simplest) — Add an "API Keys" section to the AdaL dashboard where users can generate keys for api.sylph.ai/v1/ endpoints. This is the pattern used by Anthropic, OpenAI, and Google.

2. OAuth Device Flow — If SylphAI prefers not to expose raw API keys, ForgeCode also supports OAuth device code flow (like GitHub Copilot) and OAuth authorization code + PKCE flow (like Claude Code / Codex). I could add an OAuth auth method to the AdaL provider config.

3. Token Export — If there's an existing way to extract a bearer token from ~/.adal/settings.json or similar, that could be used as an API key.

Why This Matters

ForgeCode users with AdaL Pro subscriptions would get:

• Single-key model routing — Access all AdaL models (OpenAI, Anthropic, Google, Zai, MiniMax) through one credential
• AdaL's prompt caching & adaptive thinking via ForgeCode's interface
• Credit-based billing through existing AdaL subscriptions

The ForgeCode PR is ready to merge as-is — the provider will work immediately once an auth mechanism is available. Looking forward to hearing from the team! 🌸