AUGMTDAUGMTD

    Let Claude or ChatGPT read your work. A person still decides.

    Connect Claude, ChatGPT, Claude Code, Cursor, Codex or Gemini to AUGMTD. They see your clients, open promises and approvals waiting, and they propose. You apply.

    Updated 27 October 2026

    Your team already uses AI tools. Connect Claude, ChatGPT, Claude Code, Cursor, Codex or Gemini to AUGMTD and they can read your work: your clients, the promises still open, the approvals waiting.

    Ask from the tool you already have open.

    You are in Claude, halfway through a proposal, and you need to know what you promised this client last month.

    Ask what you still owe your biggest client this week. The answer comes from your list in AUGMTD: the open promises, the approvals waiting, the recent changes. It works the same from ChatGPT, Claude Code, Cursor, Codex or Gemini.

    Before
    You paste the history into the chat and hope it is complete.
    With AUGMTD
    The tool reads the client's open promises from AUGMTD.

    You decide whether to connect a tool at all. It sees only what you can see.

    They propose. You apply.

    A developer in Cursor has fixed the bug the client reported, and the client should hear about it today.

    A connected tool can propose a reply, a new promise or a promise kept. It lands as a card in AUGMTD. Applying a reply makes it your draft.

    Sending stays your click.

    Keys you can see and switch off.

    IT asks which AI tools can read company work, and how to turn them off.

    Each member can make keys that act as themselves, to read or to propose, expiring after 30, 90 or 365 days, or never. Company admins see every key, can revoke any of them, and can make every key read-only.

    Admins decide what keys may do. Each person decides whether to connect at all.

    Tell your own systems when something changes.

    Your project tool should know the moment a promise to a client goes overdue, without anyone copying it across.

    Company workspaces can send a notice to an address they set, for example when a promise to a client goes overdue, and take updates back. An update that matches an open promise becomes a card to confirm.

    Nothing changes in AUGMTD until a person applies the card. Each person chooses whether their own email and meetings are shared this way.

    What it looks like in practice.

    When
    In Cursor, a developer asks what the team promised a client about a bug fix
    What's ready
    The open promise with its due date, and a proposed reply to the client
    Who decides
    The reply lands as a card. The account lead applies it and sends it

    Good to know before you start.

    • Connected tools can read and propose. They cannot send.
    • Webhooks and updates from your own systems are for company workspaces, set up by an owner or admin.

    Questions people ask.

    What can a connected tool see?+

    Your work as AUGMTD has organised it: clients, open promises, approvals waiting and recent changes. It acts as the person who connected it.

    Can an admin stop it?+

    Yes. Admins can revoke any key or make every key read-only.

    Read next

    See it on your own work.

    Show us one process your team repeats every week. We'll show you how it would run.