Posting CLI
The terminal client stores API requests as YAML and lets agents send them through an open interface while users watch.
- 12,605 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The client sends requests using the selected environment’s permissions and retains potentially sensitive response history.
Install
- Works in
Manual install
brew install darrenburns/homebrew/posting@betaFirst Installation option for Posting 3 beta through Homebrew. The Go method appears later in the README.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The client sends requests using the selected environment’s permissions and retains potentially sensitive response history.
This is third-party code. Review the repository files before installing.
What it does
Posting is a terminal interface for composing HTTP requests and exploring responses. Tabs, headers, variables and JSON views work with local YAML collections that can be versioned in Git. Requests can be imported from curl or API descriptions. `posting remote` lets a coding agent use the open client while the user watches. GraphQL, gRPC streaming and SSE event inspection are also supported.
Who it is for. Integration engineers testing APIs with an agent while watching requests in a terminal interface.
Good fit when
- An agent request needs immediate header and body inspection.
- API collections should live as readable YAML beside the project.
- Debugging needs several request tabs.
- A gRPC or SSE stream needs individual-message inspection.
Not a fit when
- You only need an unattended test runner without a terminal UI.
- Tokens or responses must not be kept in local history.
- You require final-release stability from Posting 3 beta.
Example request
Send a read request to the test API through open Posting and show status, headers and the selected JSON field.Limitations
Posting 3 is in beta; validate important existing collections before migrating. The first installation method uses Homebrew, while source installation needs Go 1.25.5 or later. Requests reach real APIs and may change service data, so use test endpoints and restricted credentials. Collections, environment files and persistent response history can contain secrets; inspect them before committing or sharing with teammates.
How to disable. Close Posting and stop agent remote use. Review saved YAML, environments and response history separately.
FAQ
Where are requests stored?
In local YAML files suitable for reading and version control.
Can I paste curl?
Yes. Paste it into the URL bar to import; curl export is supported too.
How do I inspect large JSON?
Use the collapsible tree, response search and JSONPath filtering.
What about Posting 2 collections?
Posting 3 reads existing collections, configuration and .env; review migration guidance before switching.
Can it be used over SSH?
Yes. Its terminal interface supports keyboard-oriented workflows.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI runs HTTP request chains from plain-text files and checks response status, headers and body content.
The interactive HTTP client lets you inspect a browser request, change parameters and explore its response in the terminal.
Reviews the git diff and the conversation with the agent: catches bugs and gaps between your request and the agent's result. CLI, skill, GitHub Action
Backlot serves local copies of the Slack, Gmail, GitHub, Jira and S3 APIs with vendor-shaped responses: no accounts or network.
The CLI generates API tests from schemas and gives agents reproducible failures in responses and operation sequences.
A Rust HTTP load-testing tool with an MCP server: an agent runs a benchmark and gets latency percentiles and status breakdowns.
README in short
Features include layered environments, header completion and configurable keys. Collections can be imported from OpenAPI, Postman and Bruno.