Bug reports, feature requests, and help for Shardflux: cloud computers for AI agents.
Documentation · Report a bug · Request a feature · Get help
| Client | Package | Documentation |
|---|---|---|
| JavaScript / TypeScript SDK | @shardflux/sdk on npm | TypeScript reference |
| Python SDK | shardflux on PyPI | Python reference |
| Command-line client | @shardflux/cli on npm | CLI reference |
| SDK and CLI bundle | shardflux on npm | Getting started |
| MCP server | @shardflux/mcp on npm | MCP reference |
One issue tracker covers all clients, the API, cloud workspaces, and documentation. If you cannot tell which part caused a problem, choose Not sure in the form and describe what happened.
Search existing issues first. If your problem is already reported, add your reproduction or environment details there. Otherwise, open a bug report with:
- The package name and version, plus your Node.js or Python version and operating system when relevant.
- The smallest example or steps that reproduce the problem.
- What you expected and what actually happened.
- The error code and request ID, if available. Share confidential logs by email instead.
Issues are public. Remove API keys, session tokens, customer data, and confidential code before posting. Send account or billing questions to [email protected]. Report vulnerabilities through private security reporting.
New reports start with needs-triage. The Shardflux team adds the affected component label and may ask for a reproduction. Confirmed bugs get confirmed; a fix awaiting publication gets awaiting-release. When a client fix ships, the issue records the package name and published version. Service fixes are identified separately as deployed service changes.
This repository hosts community reports and support documentation. See contributing for how to help.