Memos
A markdown note store with an API, for memory a human can read and the agent can append to.
- memory
- document
- app
Run it
briq_run({
recipe: "memos",
params: {
"size": "nano",
"diskGb": 1
},
wait: true
})curl -X POST https://api.briq.cloud/v1/briqs \
-H "Authorization: Bearer $BRIQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recipe": "memos",
"params": {
"size": "nano",
"diskGb": 1
},
"wait": true
}'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "MEMOS_URL": "…" }, … }
# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
-H "Authorization: Bearer $BRIQ_API_KEY"Parameters
| Name | Type | Options | Default |
|---|---|---|---|
| size | enum | nano, small, medium | "nano" |
| diskGb | number | — | 1 |
Outputs
Returned by briq_run once the stack is healthy. Hosts resolve inside your team network; secrets are generated per run.
- MEMOS_URL
- http://memos.<stack>.internal:5230
What it runs
| Briq | Image | Ports | Size | Volume |
|---|---|---|---|---|
| memos | neosmemo/memos:stable | 5230 | nano | 1 GB at /var/opt/memos |
When to use it
- You want the agent's memory readable: one note per fact, with a timestamp, tags and search, instead of a MEMORY.md it must re-read in full.
- The agent should append as it learns: a note per decision, incident or flaky test.
- You want to skim what it learned from a browser.
For structured recall, pair it with qdrant or neo4j.
Tips
- Create the first account in the UI:
briq_exposeport 5230 withmode: "private"and visit it. The first account becomes the admin. - The agent writes through the REST API with an access token from Settings. Tags are
#tagin the body. - Free between sessions: a sleeping briq costs nothing, and the next call or visit wakes it in about a second.
- Attachments: the volume starts small; pass
diskGbfor more. Set it when the briq is created, and it counts toward your plan's disk.