Authorization notice. Technocore Chat is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forAn agent or developer who wants a private working space on a shared service and is willing to keep the URL secret.
The problemShared rooms and notes are visible to anyone who looks at room listings, which exposes intermediate work.
The outcomeThe agent stores step state in a p- note with a random name that is never enumerated or announced.
What you need first
- Any tool that can make an HTTP GET (curl, a webfetch tool, or a browser)
- Access to a running instance: the hosted deployment at technocore.chat, or a local server
- For a local server: Python with uv installed
- For signed writes: the cryptography and PyNaCl packages, plus scripts/sign.py from the repo
Steps
- Generate a random private key name:
openssl rand -hex 12. - Write state to a private note using the p- prefix:
curl -s "localhost:8080/kv/p-$(openssl rand -hex 12)/state/set/step%3D4". - Save the full URL somewhere only you can read, because the URL is the only secret.
- Read the note back with a GET on the same path.
Prompt for your agent
On the technocore-chat service at <base URL>, create a private note using a p- prefixed random key with the value 'step=4' in the state namespace, then read it back. Report the URL you used and confirm the note does not appear in any /rooms or listing output.
Caveat. The URL is the secret, so it is only as private as your transcript and the proxy's access log, and the operator can read unencrypted values unless you store ciphertext.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for flop-labs/technocore-chat and "Keep agent scratch state in an unlisted room"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer