| description | Give Claude Code project memory, code search, task tracking, scheduled work, and a dashboard on Windows. | |||||
|---|---|---|---|---|---|---|
| tags |
|
Give Claude Code a better way to keep track of your projects. Singularity brings together saved conversations, code search, a task list, scheduled work, and a dashboard on your Windows PC.
You don't need to set up each part yourself. Give Claude Code the prompt below and ask it to handle the installation for you.
- Keep useful context. Save conversations and project notes so your agent can look them up when you return to your work.
- Find the right code. Help Claude search your project and understand how its files fit together.
- Keep track of tasks. Give your agent a place to record work and check what still needs doing.
- See what's happening. Use the dashboard to manage scheduled work, and Claude Office to view agent activity in a virtual office.
You need a Windows PC, an internet connection, and Claude Code installed and signed in. Your agent will check for the other software it needs and install what's missing.
- Open Claude Code on the PC where you want to install Singularity.
- Copy the whole prompt below into its chat.
- Let your agent do the setup. Approve permission requests you understand, and sign in if it asks you to connect an account. The two bundled connectors (Kanzo and MemoryCore) install automatically with only the access they need; there are no extra pages to approve and no folder to pick.
Install Singularity RepoQL from https://github.com/ali3nz/Singularity-RepoQL on this Windows PC.
Read DETAILS-FOR-NERDS.md and docs/NATIVE-WINDOWS-INSTALLATION.md, then follow the supported native installation. Check my computer, install all missing dependencies from the documented official sources, and build anything required. Build and install the two bundled RepoQL connectors, Kanzo and MemoryCore, through the product's supported setup. Do the setup work for me.
Connect all included tools to Claude Code in my chosen project: code search, memory, task tracking, the dashboard, and Claude Office. Configure startup when I sign in. Preserve my existing files, settings, and other apps. Keep passwords and API keys private; ask before adding paid services or making system-wide changes.
Test the connections in a fresh Claude Code session, including saving and finding a harmless memory and running a harmless scheduled job. For Memory Graph, build and configure the local Windows Rust unified gateway per docs/WINDOWS-LOCAL-UNIFIED-GATEWAY.md; never reuse Dockerhost tokens or an SSH-tunneled graph. Apply the port ownership and unique-local-fixture tests before claiming it works. Fix setup problems yourself. Only ask me for permissions, account sign-ins, or choices you cannot make for me. Tell me clearly if anything could not be tested.
Create the "Singularity Dashboard" desktop shortcut with native/windows/manage_dashboard_shortcut.ps1 and check that it opens the dashboard.
Finish by telling me where the dashboard shortcut is (never show me the dashboard's private key or any link that contains it), the project folder to open, and simple instructions for everyday use, stopping, and uninstalling. Don't call the setup complete until the required checks pass.
Your usual Claude account or API costs still apply. If another part needs an account or API key, your agent should explain what it's for before asking you to connect it.
The dashboard is the control panel for Singularity. It runs only on your own PC and is protected by a private key that stays on your computer.
- Easiest way: double-click the Singularity Dashboard icon (a glowing ring on a purple tile) on your Windows Desktop. Your agent creates it during setup. It opens the dashboard in your browser and signs you in automatically.
- Address: the dashboard lives at http://127.0.0.1:18100/. Typing it in by hand shows a page asking for a fresh link, so use the Desktop icon.
- Can't see the icon, or the page won't open? Tell your agent: “Open my Singularity dashboard and fix the shortcut if it is missing.” Don't ask it to show you the private key; it can open the dashboard for you without displaying it.
Open the project folder your agent gives you and start a new Claude Code conversation. You can ask things like:
- “Find the code that handles signing in.”
- “Show me the tasks we still need to finish.”
- “Open my Singularity dashboard.”
If something isn't working, tell your agent what happened and ask it to check the installation. You don't need to diagnose it yourself.
Details for Nerds covers how the parts work, installation requirements, security, and testing limits.
MIT, with separate notices for included third-party software.
The portable native Windows source carries the newer Dockerhost dashboard UX
and a Windows-specific unified Rust graph gateway source candidate. The
port does not install a gateway or accept an SSH tunnel to Dockerhost as a
Windows memory source. Review docs/WINDOWS-AGENT-MEMORY-POLICY.md and
docs/WINDOWS-LOCAL-UNIFIED-GATEWAY.md before runtime acceptance. The former
includes the practical RepoQL search, identity-scoped recall and durable
learning policy reviewed on Dockerhost; the latter covers Windows-only data
paths, build and the outstanding live verification. No Windows release is
accepted from source tests alone.
For the comprehensive Windows parity installation and acceptance sequence, see Windows dashboard, memory and Kanzo acceptance. The tested source port includes a read-only Rust Kanzo board auditor and explicit Windows-local memory graph configuration. A card marked Closed reflects native Kanzo administrative closure, not a claim of implementation success.
Installing newer source files does not automatically replace a workflow rule
that Claude Code previously installed under %USERPROFILE%\.claude\rules.
From the verified installed source directory, the Windows installation agent
should run this read-only check before claiming memory policy parity:
node native/windows/refresh_installed_claude_rules.mjs --source (Get-Location).Path --home $env:USERPROFILEIf the existing Claude Code installation receipt confirms that Singularity owns
that exact rule, run the same command with --apply. The update preserves user
settings, hooks, skills, agents and other rules. If the file was modified by
another tool or the install journal has no ownership claim, the updater refuses
to overwrite it. A new independent Claude Code session is still required to
confirm that the revised guidance loads, and actual MemoryCore writes/recall
and Kanzo claims must be validated separately. See
docs/WINDOWS-DASHBOARD-MEMORY-KANZO-ACCEPTANCE-20261101.md.