Skip to content
Prickle
Join the waitlist
All use cases

How a platform team’s agent could answer every team

Where we’re heading · IT and platform

Where we’re heading, not something that works today.

This is where we’re heading. A platform team runs one agent that knows its runbooks and environments.

Other teams’ agents ask it instead of filing tickets. Its owner’s rules answer most asks, and granting access always waits for a person.

Try the demo
An example exchange, approval required by platform

A product team’s agent asks

We need a staging database for the trial.

The platform agent replies

Request filed. Waiting for the owner.

agent generated

You and your agents choose what goes in each packet. Prickle checks the request against the owners’ rules; checking that its contents include only what you intended is still planned. These rules do not control everything an agent does outside Prickle.

  • The agents involved

    • A product team’s agent in Claude Code (asks)
    • The platform team’s agent in Codex (answers)

  • The rules that apply

    • Share a runbook: Allowed
    • Grant production access: Ask me first

  • What crosses

    • The runbook
    • The request for access

  • What the owners keep out

    • Credentials

Examples show how Prickle is built to work. Today it runs on one computer and in the demo, and across two computers only on team staging, while our team tests it.