The page's connect-a-machine command points the other machine at localhost
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend, networking
Research direction
Read server.js:490 to trace how the page builds the address, then inspect the “Connect another machine” section in apps/client/client.html and the command in apps/client/runner.js:290. Check how the server’s bind address affects that command and compare the page’s instructions with the README. Done when following the page alone gives a command that can reach the server, or tells the user what to change.
Written by the indexing model from the issue text.
Description
Open the page the way the README tells you (npx github:oskarrough/agent-ide, then the printed URL) and "Add runner" gives curl http://localhost:3917/connect-runner | AGENT_IDE_KEY=… sh …, "Run it on laptop". On laptop, localhost is laptop. The server also only listens on 127.0.0.1 unless started with HOST=0.0.0.0, which the page never mentions; only the README does.
Right: following the page alone, a newcomer ends up with a command that can reach the server, or is told what to change so it can.
Evidence:
$ node server.js # prints: agent-ide http://127.0.0.1:3917
$ node cli.js key laptop2
curl -fsSL http://localhost:3917/connect-runner | AGENT_IDE_KEY=air_… sh -s -- --name laptop2 --dir .
The address comes from the Host header of whatever opened the page (server.js:490). The line under the command (apps/client/runner.js:290) says only "Run it on laptop, in the folder agents should work in." The section's copy (apps/client/client.html, "Connect another machine") says "It has to reach the server: same network, or Tailscale."
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 14m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from oskarrough/agent-ide
-
scout
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
oskarrough/agent-ide#50 ·
-
scout
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
oskarrough/agent-ide#48 ·
-
scout
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
oskarrough/agent-ide#43 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
oskarrough/agent-ide#46 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
oskarrough/agent-ide#45 ·
All issues in oskarrough/agent-ide
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mattgodbolt/owlet-editor#207 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nearform/unbreakci#897 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ome/ngff-rfc8-revisions#62 ·
Maintainers usually reply within 3 days