Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Puck

AI overview

Sign in and the AI will write an overview from our coverage.

Headlines · 4

  1. Amp launches workspace-owned Service Accounts

    Amp has introduced Service Accounts, workspace-owned identities that are not tied to a single user. Workspace administrators create them, and each has its own API keys and third-party credentials. Threads created under a service account can be viewed and messaged by other workspace members. The accounts are intended for team-owned work, including pull-request review, documentation maintenance and CI jobs that start Amp threads. Because anyone in the workspace can use a service account's threads, administrators should only assign credentials they would be comfortable giving all workspace members.

    Amp Chronicle · 🔥 0
  2. Amp extends AI agents beyond code with OpenAI's GPT-6 Astra

    OpenAI published a customer story on how coding-agent company Amp uses OpenAI models for work beyond writing code. Amp CEO Quinn Slack says OpenAI models account for the majority of tokens used in Amp, with some users consuming 10 billion tokens a week, and that Amp launched a Sign in with ChatGPT integration giving users more tokens and access to OpenAI models including GPT-6 Astra. The post also describes Amp's recently announced conversational assistant Puck, powered by GPT-Live-1 for real-time voice, and testing of a faster Ultrafast mode with GPT-6 Astra. All capability and performance claims come from OpenAI and Amp and include no independent benchmark data.

    OpenAI · 🔥 0
  3. Amp's Puck now reachable from ChatGPT and Claude via MCP

    Amp says users can now talk to Puck from ChatGPT, Claude and other agent clients via MCP (Model Context Protocol). Puck MCP exposes two tools: puck for interacting with your Puck in Amp, and orbs for an interactive view of running orbs with links to their portals. Amp says it is the same Puck used in Amp, able to search threads, find earlier work and coordinate agents; users connect via Settings > Puck with an "Add to Claude" button, or by pasting the MCP server address into another client and signing in with an Amp account.

    Amp Chronicle · 🔥 0
  4. Amp adds GitHub webhooks to follow up on PR comments and CI

    Amp announced first-class GitHub Webhooks support: when Amp opens a pull request, the agent can now subscribe to that PR's comments, reviews and CI results for its latest commit, so a failing check or a reviewer's question appears in the same thread where the agent already has context to act. Users can also ask Amp to start a new orb for every new issue or PR in a repository, optionally limited to a certain label, with each new item getting its own orb that reads it and leaves a summary waiting; later comments on that issue or PR go to the same thread. These subscriptions can be edited or paused under Settings → MCP & Integrations → GitHub, which also shows the orbs each one started, and the company says installing the Amp GitHub App on a repository is required to get started.

    Amp Chronicle · 🔥 0

Experience and discussion from the community

Share my Puck experienceAsk about Puck

Nobody has shared their experience with Puck yet.