agent-device docs: parallel agents need their own --session
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read website/src/content/docs/docs/using-devices/agent-device.mdx and update the commands, example, and messages table. Explain that each agent should set AGENT_DEVICE_SESSION or pass --session, and include both error messages from the issue. Done when the docs cover parallel agents and list both errors; remove the guidance when the upstream fix ships and simlock requires that version.
Written by the indexing model from the issue text.
Description
When several agents use agent-device through simlock on one machine, commands after open fail unless each agent passes --session (or sets AGENT_DEVICE_SESSION). The errors are No active proxy device lease for this session; run open first. (agent-device CLI) and refused: lease <id> is not one of yours on this gateway (simlock, src/agent-device/front/relay-host-link.ts).
The root cause is in agent-device: without --session, a command falls back to a machine-wide "last saved session" pointer. Upstream: https://github.com/callstack/agent-device/issues/3931
Simlock side: website/src/content/docs/docs/using-devices/agent-device.mdx shows commands with no --session and says nothing about parallel agents. Its messages table lists neither error.
Fix: say that each agent sets its own AGENT_DEVICE_SESSION (or passes --session), show it in the example, and add both messages to the table. Drop this once the upstream fix ships and simlock requires that version.
Written by an agent.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 2
- Avg merge
- 8h 8m
- Merged PRs (30d)
- 366
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 callstackincubator/simlock
-
bug:new
Difficulty 1/5 Under an hour Newbie friendliness 78/100
callstackincubator/simlock#934 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
callstackincubator/simlock#871 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/simlock#817 ·
Maintainers usually reply within 1 day
-
bug:triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstackincubator/simlock#778 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 · 1 comment ·
Maintainers usually reply within 1 day
All issues in callstackincubator/simlock
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
openclaw/openclaw#182077 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
aikido high security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dequelabs/axe-linter-action#161 ·
-
[Feature Request] Update the DimCode agent icon to the 45:32 brand markPossibly taken @eric8810 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
lyswhut/lx-music-desktop#3026 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
abhigyanpatwari/GitNexus#3704 ·
Maintainers usually reply within 1 day