mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5245] [feature]: Multi-Workspace Support and Environment Optimization #2004
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2004
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CloverAn on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5245
Is there an existing issue for this?
Summary
Dear Development Team,
Thank you for providing such a useful tool! I'd like to share four enhancement ideas that would significantly improve my workflow:
Workspace Management
I'd like the ability to create multiple local workspaces to separate different projects. While the current online workspaces and team collaboration features are helpful, I frequently need to switch between projects and require dedicated personal workspaces for better organization.
Environment Isolation
Currently with a single workspace, all projects share the same environment (though grouped in collections). I propose allowing environment customization per workspace - this would let me maintain distinct configurations for different projects without creating excessive environments.
Environment Parameter Sharing
When a workspace contains one project using multiple environments, there should be a way to store and reuse common parameters (headers, request bodies, auth tokens) across environments. This would eliminate redundant configuration for identical settings. #5239
Update Control for Chinese Users
Due to China's unique network environment, accessing your servers can be unreliable. Could you add configurable update checks (manual/interval-based) rather than mandatory updates on launch? Immediate tool accessibility would greatly improve the user experience.
These improvements would effectively address the challenges developers face when managing multiple concurrent projects.
Thank you for considering these suggestions!
Best regards,
Why should this be worked on?
Improves user experience
@liyasthomas commented on GitHub (Jul 15, 2025):
Hi @CloverAn - Multiple personal workspace are not in our current roadmap. Though, you can already create multiple workspaces and organize requests into collections and folders with team collaboration support. The environment is also scoped to workspaces. While we’re improving the platform’s features, most of the requests in the question are already addressed in Hoppscotch. You can use all these features in both Hoppscotch Cloud and Self-Hosted instances across multiple clients, like web apps, desktop apps, and more.
Docs: https://docs.hoppscotch.io/documentation/features/workspaces
@CloverAn commented on GitHub (Jul 16, 2025):
Thank you for your response!
I've reviewed the team collaboration workspace options, including using the self-hosted community edition. However, these don't fully address my concerns or what I'm hoping to achieve.
I wonder if other developer friends might have similar needs. I hope one day in the future, I'll be able to use these features on Hoppscotch.
Thank you again!
@KaKi87 commented on GitHub (Jan 28, 2026):
Hi,
I work at a company where cloud isn't an option and self-hosting involves a ton of paperwork, so the easiest immediate option would be to have local workspaces that could be synced as files in git.
Thanks