DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to keep work and personal memory in separate workspaces with Graybox

Create isolated workspaces so work and personal notes stay apart unless you search across both.

Who it is forA person who uses one tool for both job knowledge and private life and does not want the two mixed together.

The problemUnrelated work and personal notes can mix in one wiki and show up in each other's search results.

The outcomeTwo isolated workspaces, with searches limited to the active one unless you explicitly search all of them.

What you need first

  • Python 3.10 or newer
  • Access to an LLM provider and its API key, set in an .env file or as GRAYBOX_LLM_API_KEY
  • A config.yaml based on config.example.yaml with your LLM and workspace details

Steps

  1. Create a second workspace with graybox workspace-create work --description "Day job knowledge base".
  2. Switch between workspaces with graybox workspace-switch personal or graybox workspace-switch work.
  3. List your workspaces and see which one is active with graybox workspace-list.
  4. Search every workspace at once with graybox ask "<your question>" --all when you need results from both. (inferred, check the README)

Prompt for your agent

Use the Aaryanverma/graybox repo to create a workspace named <workspace-name> and switch to it. Expected output: the workspace appears in `graybox workspace-list` marked as active. Verify that a page captured in one workspace does not appear in `graybox pages` after switching to the other.

Caveat. Graph expansion is skipped in --all mode, and there is no automatic sync between workspaces, so shared facts must be captured in each one.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page