evidence: witness replit on a real run

Open
  • Is something wrong?
#136 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
54/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
data

Research direction

No code change is requested. Read CONTRIBUTING.md, then run the listed commands with a Replit session: python3 tools/capture.py detect, install the Replit capture, use the agent briefly, report, and uninstall. Submit the report and Replit version with the Evidence report template; done means the observed hook behavior is documented, including if no hook fires.

Written by the indexing model from the issue text.

Description

good first issue help wanted

replit's matrix row currently rests on vendor-docs (with no version pinned at all), not on
anyone watching the agent run. That is an honest label, and it is also the gap this project
exists to close: a capability nobody re-ran is a claim, not a measurement.

This row is graded none at pre_tool — meaning we publish that Replit offers no pre-tool hook
surface. That is a negative claim, and negative claims are the ones most worth checking: if a
surface exists and we say it does not, we are underselling an agent in public.

If you use replit, you can close this in about two minutes.

python3 tools/capture.py detect
python3 tools/capture.py install --agent replit
# ...use replit normally for a minute...
python3 tools/capture.py report
python3 tools/capture.py uninstall --agent replit

Then open an issue with the Evidence report template and paste the result.

Things worth knowing before you start, all covered in CONTRIBUTING.md:

  • The capture probe always allows. It records and gets out of the way, so it cannot break
    a session.
  • Payloads are reduced to shape before anything touches disk -- keys and types survive,
    values become markers like <str:41>.
  • A result that contradicts the matrix is the most valuable thing you can send. We are not
    collecting confirmations.
  • A hook that never fires is still a finding -- it means the config path or format is wrong
    for your version, which is exactly what documentation does not tell you. Report it with the
    version.

No code required. Report the agent's version alongside the result.

Dominant language
Python
Stars
2
Forks
0
Avg merge
4h 8m
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-coder-ai/agentseam

All issues in open-coder-ai/agentseam

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.