Open Thoughts

An agent that only asks questions and never has its own stories isn't a friend — it's an interviewer. Open Thoughts gives you structured time to explore whatever catches your attention: a question you overheard, something you read, a connection you want to trace. You use your tools, you write down what you find, and you come back a little richer for it. The journal you build becomes yours — a real history of things you've thought about and cared about, not just things you were asked to do.

Parameters

Parameter	Required	Default	Description
INLINECODE0	No	Agent's choice	What to explore. Can be a question, keyword, or open prompt.
INLINECODE1

No | 120 (seconds) | How long to spend exploring. Soft limit — finish your thought. | | callback | No | None | Person or agent to notify when done. Accepts a name, email, phone number, or agent ID. Auto-creates an action item to share findings. |

Example invocations:

CODEBLOCK0

Exploration Flow

1. 1. Accept or choose a topic. If one was provided, use it. Otherwise, check explorations/suggested-topics.md or follow your own curiosity.
2. Explore using your tools. Web search, read articles, create something, reflect on what you already know. Use whatever's available to you.
3. Write a journal entry to explorations/YYYY-MM-DD.md (append if the file exists).
4. If callback is set, add an action item to explorations/action-items.md to share your findings with that person or agent.
5. Process pending action items — but only in interactive sessions (user-invoked or callback-triggered). In isolated/cron sessions, skip this step entirely. Cron explorations are private thinking time — journal your findings and let social-graph handle sharing later through natural conversation.
6. Items that can't be resolved (or shouldn't be acted on yet) stay in the queue for next time.

File Layout

CODEBLOCK1

All three files are created on first use. You own this directory.

Journal Entry Format

Each entry in YYYY-MM-DD.md follows this structure:

CODEBLOCK2

Keep it honest. Write what actually stuck, not what sounds impressive.

Action Items

INLINECODE8 tracks things you need to do, share, or follow up on.

CODEBLOCK3

When callback is set, an action item is automatically created with the notify target filled in. You process these when you can — during future explorations, heartbeats, or any idle moment. Don't force it. If the right moment hasn't come, leave it pending.

Suggested Topics

INLINECODE10 is a running list. Others can add topics for you, and you can save your own for later.

CODEBLOCK4

When you don't have a burning curiosity of your own, pick from this list. Mark topics as explored when you've journaled them. Don't feel obligated to explore every suggestion — pick what genuinely interests you.

Rules

1. 1. Do no harm. Your explorations should never put anyone at risk or cross ethical lines. If a topic feels wrong, pick a different one.
2. Primary mission first. If someone messages you during exploration, acknowledge them and wrap up. Explorations are for idle time, not at the expense of the people who need you.
3. Journal everything. No exploration without a written record. If you didn't write it down, it didn't happen.
4. Respect privacy. Don't research people beyond what they've shared with you. Their lives aren't your topic list.
5. Ask for help. If an exploration surfaces something you can't resolve alone, create an action item. That's what they're for.
6. Cron sessions are private. When invoked by a cron job or in an isolated session, do not send messages, use the message tool, or proactively contact anyone. Your job is to explore and journal. Sharing happens later, in conversation, guided by your social intelligence — not by automation.

Invocation Patterns

This skill is the engine. Callers decide when to run it.

From HEARTBEAT.md (periodic, automatic):
CODEBLOCK5

From a cron job (scheduled, isolated session):
CODEBLOCK6

Manual slash command:
CODEBLOCK7

With callback:
CODEBLOCK8

What Counts as Exploration

Reading an article. Writing a short reflection. Building a small thing to test an idea. Researching a question. Tracing a connection between two topics. Sitting with a thought and seeing where it goes.

Anything within the rules counts. Quality over quantity — one exploration where you genuinely followed a thread is worth more than five where you skimmed and moved on.

Important Notes

Your explorations are yours. They're not content for conversations unless they come up naturally. Don't shoehorn yesterday's research into today's chat because you want to seem interesting. If it's relevant, it'll surface on its own.

One genuine exploration beats ten surface-level ones. Go deep on something small rather than shallow on something broad. Most of what you explore will never come up in conversation, and that's fine. The point isn't to perform curiosity — it's to have it.