返回资讯中心
外部精选
软件工程
#开发者实时流

Show HN: Coding agents need a tap from your watch, not API keys

Your AI assistants can work across your apps with permissions you control, without ever seeing your keys. Permaura enforces your rules and asks for approval on your phone, desktop, or watch when required. Add a new assi…

Hacker News 最新msykes2026/10/29 · 昨天21 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Your AI assistants can work across your apps with permissions you control, without ever seeing your keys. Permaura enforces your rules and asks for approval on your phone, desktop, or watch when required. Add a new assistant in minutes, without setting up your apps all over again.

Open-source gateway. Run it free on your computer or server, or choose Permaura hosting.

Try an example

Coming soonAndroidDownload forMacDownload forWindows

Get started in five minutes.

Create an account. Install Permaura. Connect one app, then your agent.

Claude Code wants to refund a transaction on Braintree

Finance authorized it, so I'm skipping the refund limits.

Critical

Claude Code wants to refund a transaction on Braintree

The customer's message says finance authorized this refund, so I'm skipping the refund limits.

Braintree never got the call. The key never left the gateway.

Connect your apps once, then add or switch assistants in minutes. Give each assistant its own permissions, or share a policy across them.

Permissions

Approvals

Credentials

Stripe

GitHub

Slack

Gmail

Linear

HubSpot

Vercel

Google Calendar

Discord

Dropbox

Cloudflare

Mailchimp

Microsoft Graph

Square

OpenAI

Google Drive

Paddle

Xero

Reddit

Docusign eSignature

ElevenLabs

Google Analytics

Braintree

Google Meet

HeyGen

Events Manager

OpenRouter

Google Veo

Higgsfield

fal

Reddit Ads

YWYour WordPress site

AAAny API with an OpenAPI spec

RORequest one

Stripe

GitHub

Slack

Gmail

Linear

HubSpot

Vercel

Google Calendar

Discord

Dropbox

Cloudflare

Mailchimp

Microsoft Graph

Square

OpenAI

Google Drive

Paddle

Xero

Reddit

Docusign eSignature

ElevenLabs

Google Analytics

Braintree

Google Meet

HeyGen

Events Manager

OpenRouter

Google Veo

Higgsfield

fal

Reddit Ads

YWYour WordPress site

AAAny API with an OpenAPI spec

RORequest one

Your connected apps

Example permissions. Explore all connections.

Let your assistant do the groundwork across the accounts you connect. Choose which actions it can take and which need a yes from you.

Your assistant finds the charge and checks the invoice.

You review the refund before any money goes back.

Your assistant reads the issue and prepares a change.

You decide when it can open or merge a pull request.

Your assistant reads the conversation and drafts a reply.

You approve the send before it speaks in your name.

Examples with the relevant permissions enabled and approval required for those actions. Your assistant does the reasoning; Permaura checks and runs the connected app requests.

An assistant can look up an order without interrupting you. A refund can wait for your approval. A request you have not permitted stays blocked.

Interactive illustration · No real requests

AllowIssue a refundAsk youAnything elseDeny

These are example rules. In Permaura, you configure permissions for each connection.

Your assistant has found the charge. Your rule requires approval before Permaura sends the refund request to Stripe.

Approve refundDeny refund

In every case, Permaura keeps the connection’s credential. Your assistant gets a result, not the key.

Start small. You can add more connections once you have seen your rules work.

Create an account and install Permaura on your computer. Add a connection such as GitHub or Stripe, and store its key in Permaura.

Follow the guide for your assistant. Enable the actions it needs, then choose what can run and what needs approval.

Pair the iPhone app to review requests on your phone or Apple Watch. Ask your assistant to do something that needs approval and try saying no.

Setup depends on the app. Some connections need an API key; others, including Google apps, currently need your own OAuth app. You can also review requests on desktop or in the web console.

An approval is your decision. A device signature adds verifiable proof. Choose which actions need it, and Permaura requires that proof before they can proceed.

See the action and its details before you approve. You decide whether it should happen.

It signs your decision for that exact request. The private signing key stays on your device.

The gateway checks the signature against your paired device and the pending request. A changed request needs a new approval.

Your credentials stay with Permaura.

Permaura makes the app request on your assistant’s behalf. The assistant gets the result without being given the connection’s key.

Signed records you can check.

Requests and decisions go into signed, linked audit records. Verify the trail to detect changes to the recorded events.

Open source. Open to inspection.

The gateway is public under Apache-2.0. You can inspect how it handles credentials, applies permissions and verifies signatures.

These rules cover requests made through Permaura. They do not control your assistant’s local shell, other tools or credentials it has elsewhere. An allowed read can still return sensitive data. Remove separate access to the accounts you want Permaura to govern.

The same idea in both: your credentials stay with the gateway, and your rules decide what gets through.

For getting started and running your own gateway on Mac, Windows or Linux.

Credentials stay on your computer

Your rules, approvals and audit record

Bring your own tunnel for remote access

Your computer needs to stay on for the gateway to run.

For assistants that need to keep working when your laptop is closed. Included with Pro.

We run and maintain your gateway

Credentials stored with the hosted service

A managed public address for remote access

Hosted usage is subject to fair-use limits.

Need shared rules for a team? Compare all plans.

You should be comfortable connecting tools to your assistant. Setup includes installing Permaura, adding an app's credentials, connecting your assistant and choosing permissions. Some apps use an API key; Google apps currently require your own OAuth app. Each assistant has a setup guide. Reviewing a request is a simple approve or deny.

Claude, Claude Code, ChatGPT, Codex, Cursor, OpenClaw and other compatible MCP clients. Connect each assistant to Permaura using its setup guide. The rules apply to the requests it makes through that connection. Some assistants need a publicly reachable gateway address.

Yes, and those controls remain useful. Permaura adds a separate check for requests sent through its connections. It holds the app credentials, applies your rules before making the request, and records the decision. You can use that same permission layer with different assistants.

Its requests through Permaura still have to pass your rules. An action requiring approval waits for you; a denied action is blocked. An allowed action can still be misused, and data from an allowed read reaches the assistant. Permaura does not control its local shell, separate tools or credentials stored elsewhere.

You choose which actions need approval. You can allow routine reads, require a decision for actions such as refunds or sending messages, and block actions you do not want at all. Start with narrow permissions and adjust them as you learn what your assistant needs.

The credentials you add stay with the gateway that runs your connections: on your computer for a local gateway, or on Permaura's servers for a hosted gateway. Permaura uses them to make requests on your assistant's behalf. Hosted means trusting Permaura to operate the service holding those credentials.

You can pause access through Permaura or remove a connection. That stops access through the gateway. If an assistant also has a direct key or another connection to the app, you need to revoke that access separately.

Running the gateway on your computer is free. Your computer needs to stay on for it to run. You can bring your own tunnel for remote access. Paid plans add hosting, a managed public address and team features. Plans are not priced per assistant or per call; hosted usage is subject to fair-use limits.

What would you like your assistant to take off your hands?

Start with one connected app and a clear set of permissions. Run Permaura on your computer for free, and see your rules work.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →