Your boards and account
How do I check readings from my coding agent?
Why it works this way
Readings from your agent wait on the test, not counted, until you confirm them or throw them out.
An agent's run is evidence only once you have looked at it. So nothing it sends counts until you press Confirm, and you confirm one batch at a time, seeing the total first.
What we gave up: Readings that land on their own. That would be faster, and one bad run could move your bar without you seeing it.
What it is
When your connected coding agent runs a test for you, it can send back what it found. That only happens on a test where nobody takes part: a data analysis, a reliability check, a cost per run check or a scenario stress test.
What it sends arrives on the test page as a batch, for example "3 rows from your agent, My laptop", with the name of the connection that sent it and when. Each batch is marked "not counted". Until you confirm it, your bar does not move and the test reads as it did before.
How to use it
- Open the test. Waiting batches sit on the test page, each with its rows, what the agent said about the run, and when it was sent.
- Read the line above the buttons. It says what your bar is and what the test would read once you confirm, for example "Confirm and this test reads 18 of 20 more than it does now."
- Press Confirm to count the batch. Its rows join the test marked "From your agent", or "From your agent, edited by you" if you change one later.
- Or press Throw them out. Nothing is counted.
- Do this one batch at a time. If more than five are waiting, the rest are counted under "and 3 more waiting", and appear as you clear the ones above.
- Keep people's details out. Readings are counts and short notes. Ask your agent not to send names, email addresses or other personal details from the data it ran on.
What it will never do
- Count a batch you have not confirmed.
- Take readings on a test where people take part. What people say has to come from you.
- Take new readings on a test you have already decided.
- Take a batch that is the same as one already waiting or already counted on that test. Your agent is told no.
If something looks off
- There is no Confirm button, only Throw them out. The test cannot take these rows any more. The batch says why: "This test is decided, so these rows cannot be counted", or "This test now asks people, so an agent's readings cannot count."
- "These match rows you confirmed on" a date. The rows look like ones you already counted. Confirming counts them a second time. If it is the same run, throw them out.
- "This test has no bar yet." Confirm adds the rows, but cannot tell you whether the test passes. Set the bar first. See How do I set the bar, and why can't I change it later?.
- Your agent says it was refused. It sent too much at once, the test already had 20 batches waiting, or it hit the most a day takes. Clear the waiting batches and ask it to try again, or try tomorrow.
- A batch you do not recognise. Throw it out, and check the connection named on it in Settings. Revoke it if you do not know it.