Manage Cookies Per Identity Through our Public API: New in Version 2.4.1.1

Ghost Browser has always been a power tool for people who need true separation between browser sessions. With version 2.4.1.1 (April 2025 release), we’re giving developers even more control by extending the chrome.cookies API to work with Ghost Browser’s Identities.

You can now get, set, and remove cookies for a specific Identity using the same familiar functions — just add the identity parameter. This means better session control, smarter automation, and more flexible extensions.

For full documentation and code samples, please visit the Ghost Browser Public API documentation page. In the meantime here are a few seed ideas to get your creativity flowing!

1. Smarter Multi-Account Tools

When you’re running several accounts at once, cookie access is often the missing link. Extensions can now interact with cookies for each Identity without needing to switch focus or inject code into a tab.

What you can build:

• A dashboard that displays which email or ecommerce account is logged in for each Identity
• A session manager that lets users manually or automatically refresh login cookies for specific accounts

2. Custom Login Automation

Login flows often rely on cookies for authentication. With Identity-scoped cookie access, developers can handle login automation in a clean, compartmentalized way — perfect for extensions that manage test accounts, team dashboards, or client logins.

What you can build:

• A testing extension that logs into multiple staging environments and stores separate sessions for each
• A productivity tool that automatically restores saved sessions after browser restart using stored cookies per Identity

3. Privacy-Aware Session Cleanup

Different Identities often serve different purposes — some for work, others for testing, research, or temporary tasks. Cookie cleanup no longer has to be all or nothing. Developers can selectively clear cookies from specific Identities.

What you can build:

• A privacy extension that clears cookies from temporary or research Identities on a timer
• A session expiration tool that removes cookies after a certain age but only for selected Identities

4. Insightful Session Monitoring

With Identity-specific access, extensions can now monitor login states, token expiration, or even session behavior across multiple accounts — all without crossing data between them.

What you can build:

• A session monitor that flags which accounts are about to expire based on cookie age
• A token watcher that checks for the presence or expiration of specific cookies across all active Identities

5. Cross-Identity Diagnostics

Sometimes developers need to compare sessions across different environments or check how cookies differ between accounts. Per-Identity access makes it easy to pull and compare cookie data programmatically.

What you can build:

• A developer tool that compares staging vs. production cookie setups side-by-side
• A support extension that pulls cookie info for a user’s current Identity to help debug login issues

This update opens up a whole new category of extensions that take full advantage of Ghost Browser’s unique architecture. If you’re building something with this, let us know — we’d love to see what you create and we’re happy to explore further expansion of the API to meet your needs.