amitksingh1490

One reason we built this as a Zsh plugin instead of a CLI tool:

Most developers already have heavily customized shells (aliases, Oh-My-Zsh plugins, functions, etc).

We wanted the coding agent to become part of that environment instead of replacing it.

Totally agree, If we have made a mistakes in past we must have learnt from it and when designing a standard specially with AI where the outcome is non deterministic we got be more careful.

MCP new spec has to an extent covered auth. But the MCPs are yet to adopt to that.

Ya, even I feel its slow, Thats why I use it only for architecture planning and finding complex issue

The Forge team at AntinomyHQ open-sourced their AI-enhanced terminal tool (GitHub stars welcome!). Recent updates—better autocomplete, security modes, Custom workflows, Plan/Act modes—came from user feedback. What feature would you add to an AI Terminal assistant?

Hi everyone,

I’m excited to share Forge – an AI-powered coding assistant built to help you write better code, debug faster, and automate repetitive tasks. During our early access phase, we’re inviting developers to try Forge and provide feedback.

*What Forge Offers:*

- *Code Generation & Completion:* Leverage context-aware, natural language prompts.

- *Debugging Assistance:* Get detailed explanations and troubleshooting tips.

- *Automated Refactoring:* Receive smart suggestions to improve your code.

- *Multi-Language Support:* Optimized capabilities for popular languages.

*How to Try It Out:* 1.Join our Discord: https://discord.com/invite/kRZBPpkgwq 2. Comment on our GitHub Issue:Share your Discord username on the issue at [Get a API Key](https://github.com/antinomyhq/forge/issues/422). We’ll send your API key.

Looking forward to your thoughts and feedback!

FYI Links to the Previous parts can be found here

1) Part-1 https://tailcall.run/blog/graphql-schema/ 2) Part-2 https://tailcall.run/blog/graphql-schema-part-2-1/ 3) Part-3 https://tailcall.run/blog/graphql-schema-part-2-2/

Do try the Quiz in the end.

An in-depth comparison of five methods for integrating GraphQL with Angular:

- Apollo Angular - Urql - GraphQL-Request - Axios - Fetch API

The article covers installation, code examples, error handling, and unique features for each approach. It also includes a comparison table, caching analysis, and common issues with resolutions.

We're interested in hearing about the HN community's experiences with these or other GraphQL-Angular integration methods. What challenges have you faced? What factors influence your choice of approach?

Your insights and feedback are welcome!