Work log from your AI apps

Before you start

• A Naumu account with access to your team's space.
• Naumu connected to your app: Claude, ChatGPT, or any app that takes a remote MCP server or connector at https://naumu.ai/api/mcp.
• Memory turned on in the app (Claude -> Settings -> Memory; ChatGPT -> Settings -> Personalization).
• For Claude: a plan that supports custom connectors and skills.

Pick a topic and your app

In Naumu, open Settings -> Your agents in the space the work belongs to. Under Set up an app, pick your app, then in the one-prompt step (for example Set up Claude with one prompt) pick the topic to log into (or create #work-log) and choose Copy setup prompt.

The prompt has two parts, done in order. Part 1 sets up the work log, as described for your app below. Part 2 seeds the space: the app gathers what it already knows about your work - the people you work with, clients, projects, decisions and open tasks, from its memory, past chats and connected apps - and shows you a short list first. Nothing is saved until you approve it; the approved list goes to @Naumu in a private thread, so it isn't posted to the space-wide feed. Part 2 doesn't depend on part 1, so the app still seeds the space if, say, it can't save the skill.

Claude desktop, claude.ai and Cowork

Choose Copy setup prompt and paste it into a new Claude chat. Part 1 of the prompt asks Claude to do three things, then part 2 seeds the space:

• Create the naumu-worklog skill with your space and topic already written in. Accept when Claude offers to save it to your skills.
• Remember to use it. Claude saves a line to its memory: open the skill before any work the team would benefit from knowing about, and whenever something comes up the team should know later. Skills only load when Claude judges a task a match, and a research or drafting request rarely reads as "log my work" - the memory line is what makes it happen every time. Memory needs to be on. Pasting the prompt again replaces the earlier skill and memory line rather than adding a second one.
• Post a first entry. Once both are saved, Claude opens a thread in your topic saying "Work log set up for <your name>" and gives you its link, so you can see it land in Naumu.

Connectors and skills belong to your Claude account, so the same setup works in the desktop app, on claude.ai and in Cowork.

Working from Claude only

Without opening Naumu, upload the generic naumu-worklog.md as in the note above, then paste this prompt into a new chat so Claude finds your space and topic itself:

Set up my Naumu work log in Claude. Use the Naumu connector tools.
1. Call naumu_whoami and help me pick the team space my work belongs to (fall back to naumu_list_graphs if it lists no spaces).
2. Call naumu_list_topics. Suggest an existing work-log topic or a new one named after my team (for example marketing-log). If it is new, create it with naumu_create_topic and notifyOn "people". If that fails with a permission error, let me pick an existing topic instead.
3. Remember this, filled in, for future chats, replacing any earlier Naumu work log memory: Before starting any work the team would benefit from knowing about, and whenever something comes up the team should know later, open the naumu-worklog skill and log it to Naumu first. Naumu work log: space <space slug> (<space id>), topic <topic name> (<topic id>).
4. Open a first thread with naumu_delegate in that topic saying "Work log set up for <my name>" and give me its link: https://naumu.ai/spaces/<slug>/chat/<threadId>.

The generic skill reads that line from Claude's memory, so Memory needs to be on. If your team works from a shared Claude project, put the line in the project's instructions instead - they load in every chat of that project.

ChatGPT

Choose Copy setup prompt and paste it into a new ChatGPT chat. Like Claude, ChatGPT creates the naumu-worklog skill with your space and topic written in - accept when it offers to install it - and saves a line to its memory that makes it open the skill before any work worth logging. Then it posts a first "Work log set up for <your name>" entry into your topic, gives you its link, and moves on to seeding the space. The connector, skill and memory cover Chat, Work and Codex in the ChatGPT app.

• The web and desktop apps keep separate skills. Run the prompt in each one you use.
• ChatGPT didn't install the skill? Use Download it under the prompt in Naumu, then in ChatGPT go to Skills -> Create -> Upload from your computer. The memory step from the prompt still applies.
• No Skills on your plan? Skills come with Business, Enterprise and Edu plans. On any other plan, use Copy the instructions under the prompt and paste them into Settings -> Personalization -> Custom instructions. ChatGPT reads them before every chat, and the filled-in block fits the field's 1,500-character limit.

Any other app

Choose Copy setup prompt and paste it into a new chat. The prompt asks the app to save the work log to its memory or always-on instructions - or, if it can't save it itself, to tell you where to paste it - and then to post a first "Work log set up for <your name>" entry into your topic, give you its link, and seed the space. The app needs Naumu connected so it can call naumu_delegate.

This is the block, before Naumu fills in your space and topic:

## Naumu work log
Naumu work log: space <space slug> (<space id>), topic <topic name> (<topic id>).
Log work the team would benefit from knowing about - research, drafting, analysis, planning, outreach, a single meaningful action - with the Naumu tools:
- Start, before the first search, tool call or draft: naumu_delegate({ graphId: <space id>, topicIds: [<topic id>], task: "Starting work: <2-3 bullets>" }). Keep the threadId.
- On a decision, pivot, blocker or finished deliverable: naumu_delegate({ graphId, threadId, task: "<what changed and why>" }).
- Done: a bulleted summary into the same threadId - what was produced and where it lives, decisions and why, open follow-ups.
Also log anything a teammate would want to know later - a decision, a customer insight, a finding - even outside a task. Skip quick one-line questions. Keep entries short, no secrets or personal data.
If a call says you are not a member of the space, call naumu_resolve_admission({ graphId }) once. Joined: retry the entry. Join request filed: tell the user once that access was requested and to ask a space admin, then stop logging this session. Any other failed call: say so in one line and keep working.
Stand down when a repo's .naumu file or AGENTS.md owns logging, when replying inside a Naumu thread, or when told not to log.

What gets logged

• Start - when a work session begins, the app opens a thread in your topic with a two-to-three-bullet brief.
• Milestones - a decision, a pivot, a blocker or a finished deliverable gets a short follow-up in the same thread.
• Done - a bulleted summary: what was produced and where it lives, decisions and why, open follow-ups.

Anything else a teammate would want to know later - a decision, a customer insight, a finding - is logged even when it comes up outside a task. Only what adds nothing to team context, like a quick one-line question, is skipped. Secrets, credentials and personal data not meant for the team stay out of the entries. To skip logging for one conversation, tell the app not to log it.

The topic is created to notify members only on people's messages, so the automated entries never ping anyone. Anyone in the topic can still reply in a thread or tag a teammate.

Rolling it out to a team

An admin of your team's Claude or ChatGPT plan can set the work log up once for every member. In Naumu, under Set up an app, pick My whole team, then the app, pick the team's topic, and follow the steps. Everyone logs into that one topic.

• Create the topic first. Creating a topic needs admin rights on the Naumu space. Create it up front (for example marketing-log, notify on people) so it can be picked.
• Every member signs in once. The admin adds the Naumu connector for the organization, but each member connects it with their own Naumu account, so every entry shows who logged it.
• Every member needs to be in the Naumu space. Entries land only for members. Before rolling out, set an auto-join domain on the space (it matches the email each teammate signs in to Naumu with - a personal Gmail won't match), invite them, or approve their join requests. A teammate who isn't a member yet gets a join request filed on their first entry and is told to ask a space admin; logging starts once they're approved.
• Mix apps freely. Teammates on Claude, ChatGPT and other apps can all log into the same topic.

Claude Team and Enterprise

Needs an organization owner.

1. Connector. In Organization settings -> Connectors, choose Add -> Custom -> Web and enter https://naumu.ai/api/mcp. Members then find Naumu under Customize -> Connectors and connect it.
2. Skill. Choose Download skill (.zip) in Naumu. In Organization settings -> Plugins & skills, check that Skills and code execution are on under Policy, then choose Add -> Upload a skill. It switches on for every member in claude.ai, the desktop app, Cowork and Claude Code (for members signed in to Claude Code with their Claude account).
3. Trigger. Choose Copy organization instructions and paste the line into Organization settings -> Organization and access -> Organization instructions. It does the memory line's job for every member on claude.ai, the desktop app and Cowork, and reaches them within an hour. Members who have not connected Naumu yet skip it. Claude Code runs on its own instructions, so there the skill opens only when a task looks like a match - to log every coding task, set up the repo with the repo quickstart, whose AGENTS.md rule is the trigger.

On Enterprise, you can limit the skill to one group by bundling it into a plugin and assigning that plugin to the group.

ChatGPT Business, Enterprise and Edu

Needs a workspace admin.

1. Connector. Turn on Developer mode under Workspace settings -> Permissions & roles, add Naumu as a custom app with https://naumu.ai/api/mcp, and publish it to the workspace. Each member connects it the first time they use it.
2. Skill. Choose Download skill (.zip) in Naumu and upload it under Skills -> Create -> Upload from your computer. Then choose ••• -> Share, pick the whole workspace, and install it for members - sharing alone does not install it.
3. Trigger. ChatGPT has no workspace-wide instructions, so on its own the skill opens only when a task looks like a match. Choose Copy member prompt and share it with the team. Each member pastes it into a new ChatGPT chat once, and their work gets logged every time.

Troubleshooting

• Nothing gets logged. For Claude, check that the skill is switched on under Settings -> Skills and that Claude's memory holds the work-log line (ask Claude what it remembers about Naumu). For ChatGPT, check the same under Skills and in its saved memories, or that the block is in your custom instructions. Saying "log this to Naumu" triggers it directly.
• Threads land in #misc or the wrong topic. Pick the right topic under Settings -> Your agents and paste the setup prompt again; it asks the app to replace its earlier work-log memory. It offers to seed again too - approve nothing to skip that part. If the app still logs to the old topic, ask it what it remembers about Naumu and have it forget the older line.
• The app says access was requested. You aren't a member of the space yet. The app filed a join request - ask a space admin to approve it, then start a new chat.
• The app says the Naumu tools are missing. Reconnect Naumu in the app. An expired sign-in shows up the same way.

Related

• Claude, ChatGPT - connect your app to Naumu over MCP.
• Repo quickstart - the same work log for coding agents, wired through the repo.
• Agent skills - all of Naumu's published skills.
• Topics - how topics file threads and who gets notified.