posting
The modern API client that lives in your terminal.
Runssource: GitHubPythonApache-2.0commit 56703a11513e
Python, Apache-2.0 licensed. The project labels itself: automation, cli, developer tools, http, python, rest, rest api and rest client.
posting runs. An Argusic agent installed it in 35 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Posting 2.10.0 builds and installs with uv sync, its CLI responds to --help, the TUI launches on Xvfb with correct rendered layout, 126 unit tests pass (non-snapshot), and all 194 tests including snapshot comparisons pass when run serially with NO_COLOR unset.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 13 snapshot tests fail in parallel mode (-n 24) due to race conditions; no failures in serial mode8 minutes
- NO_COLOR=1 env var crashes Textual 6.1.0 monochrome filter when segments have style=None (AttributeError: 'NoneType' object has no attribute 'color')5 minutes
- Watchfiles Rust inotify watcher fails with 'Too many open files (os error 24)' due to low inotify max_user_instances (128) in container2 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- uv sync exited 0 and built the package; .venv/bin/posting --help printed usage; .venv/bin/posting (timeout 6s) launched on DISPLAY=:99 with rendered UI (exit 0); pytest on test_urls.py, test_variables.py, test_curl_export.py, test_curl_import.py, test_files.py, test_open_api_import.py, test_postman_import.py: 126 passed; make test-ci (serial full suite): 194 passed, 4 skipped
- Model tokens used
- 92,915
- Exact commit tested
- 56703a11513e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
from posting.variables import find_variables
from posting.config import Settings
from posting.urls import ensure_protocol, extract_path_param_names
from posting.files import is_valid_filename
print(f'"'Posting {VERSION} - all runtime-accessible modules import OK')
\"" in /work/repo
succeeded in 628ms:
Posting 2.10.0 - all runtime-accessible modules import OK
All data collected. Here's the final report.
tokens used
92,915
All data collected. Here's the final report.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 35 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
automationclideveloper-toolshttppythonrestrest-apirest-clientsshterminaltextualtui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/posting)Questions
- Does posting run?
- Yes. posting runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test posting?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 56703a11513e. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test posting?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does posting take to install?
- 35 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does posting need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing posting?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for posting?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.