Setup Journal

An AI agent setup tracker app idea: a log of which AI tools and settings you use per project. Weekend build with Electron, SQLite and Claude API, for developers who switch between claude code, codex and cursor.

See the spec
Why now

Why now

Builders are posting in What's your current AI agentic setup? about how scattered their tools are, and OpenAI seems to be silently re-enabling model training on Codex chats reminds people to recheck settings. beacon.sh shows interest in keeping agent context organised. From the signals of the week of 9 Nov 2026.

The spec

The spec

Records, per project, which AI coding tool you use, its data sharing setting, key rules files and MCP servers, and reminds you to re-check them. It saves the time of rebuilding your setup each time you open a repo and catches settings that quietly change.

Build time

WeekendBasic logic / CRUD · Level 2 of 5

Audience

Developers who switch between Claude Code, Codex and Cursor.

Stack

  • Electron
  • SQLite
  • Claude API

Fun factor

You finally get a single page that says how every project is wired.

Core features

  • Per-project tool and settings checklist
  • Rules file and MCP server inventory
  • Weekly recheck reminders
  • One-page setup export to paste into a new machine

AI features

  • Reads a repo's config files and fills in the inventory automatically
  • Summarises what changed since the last check and flags privacy relevant differences

Stretch goals

  • Team view for shared settings
  • Browser extension that checks account privacy pages
  • Diff between two projects' setups

First version

A desktop app that scans a project folder for agent config files and stores a checklist with a weekly reminder.

Build plan

Build plan

4 milestones, in the order you would build them. Saved ideas get this plan with checkboxes and notes.

Scan a folderDetect rules files, MCP configs and tool directories.
Start here
Store the checklistSave per-project entries with manual toggles in SQLite.
Add remindersNotify weekly to recheck data sharing settings.
Summarise changesCompare scans and explain what is different.
The build prompt

The build prompt

Paste this into ChatGPT, Claude, Codex, or Cursor, then build the first version before anything else.

setup-journal.prompt.md
# Build Setup Journal

You are a senior full-stack engineer pairing with me on a side project. Build a working first version of the product described below. Read the whole brief before writing any code, then follow "How to work" at the end.

## The idea

**Setup Journal.** Records, per project, which AI coding tool you use, its data sharing setting, key rules files and MCP servers, and reminds you to re-check them. It saves the time of rebuilding your setup each time you open a repo and catches settings that quietly change.

**Why now:** Builders are posting in What's your current AI agentic setup? about how scattered their tools are, and OpenAI seems to be silently re-enabling model training on Codex chats reminds people to recheck settings. beacon.sh shows interest in keeping agent context organised.

**Who it is for:** Developers who switch between Claude Code, Codex and Cursor

**What makes it fun:** You finally get a single page that says how every project is wired.

## Scope

- **Build time:** Weekend. Size every decision to ship a working first version inside this window.
- **Technical ambition:** Level 2 of 5, "Basic logic / CRUD". A few screens over a simple data model with create, read, update, and delete. One lightweight persistence layer, no heavy infrastructure.
- **First version only.** Ship the core features below end to end. Stretch goals are listed so you can design around them, not build them.

## Core features (each must work end to end in the first version)

1. Per-project tool and settings checklist
2. Rules file and MCP server inventory
3. Weekly recheck reminders
4. One-page setup export to paste into a new machine

## AI features

- Reads a repo's config files and fills in the inventory automatically
- Summarises what changed since the last check and flags privacy relevant differences

How to build them:
- Put every model call behind one server-side module with a typed interface, so the provider can change without touching the UI.
- Read API keys from environment variables only, and document each one in `.env.example`.
- Write prompts as versioned constants with clear instructions and an example of the expected output; parse and validate responses before using them.
- Handle timeouts, rate limits, and malformed output with a graceful fallback the user can understand. Stream responses where a wait would exceed a couple of seconds.
- Never let a feature depend on the model being perfect. Show the result, let the user edit or retry.

## Stretch goals (later, not in the first version)

- Team view for shared settings
- Browser extension that checks account privacy pages
- Diff between two projects' setups

Leave clean seams for these (a module boundary, a nullable column, a feature flag), but do not implement them unless I ask.

## Tech stack

Use exactly: Electron, SQLite, Claude.

Stay on current stable versions, follow each tool's official conventions, and add a library only when the standard library or the chosen stack cannot do the job cleanly. If part of this stack is a poor fit for a specific requirement, say so and propose the smallest change.

## Owner's notes

Written by me, the project owner. Treat these as requirements and preferences that override the generated material above when they conflict.

The first version should be exactly this, and no bigger: A desktop app that scans a project folder for agent config files and stores a checklist with a weekly reminder.

## Build plan (with saved progress)

0 of 4 steps complete. Resume at step 1: Scan a folder. Before you start it, check what is already implemented so you do not repeat finished work.

1. **Scan a folder** [not started]
   Detect rules files, MCP configs and tool directories.

2. **Store the checklist** [not started]
   Save per-project entries with manual toggles in SQLite.

3. **Add reminders** [not started]
   Notify weekly to recheck data sharing settings.

4. **Summarise changes** [not started]
   Compare scans and explain what is different.

## Definition of done for the first version

- [ ] Per-project tool and settings checklist works end to end, with real data, not a placeholder.
- [ ] Rules file and MCP server inventory works end to end, with real data, not a placeholder.
- [ ] Weekly recheck reminders works end to end, with real data, not a placeholder.
- [ ] One-page setup export to paste into a new machine works end to end, with real data, not a placeholder.
- [ ] Every screen handles loading, empty, and error states.
- [ ] Typecheck, lint, and any tests pass, and the main user flow was exercised by hand.
- [ ] A README explains setup, environment variables, and how to run it locally.

## Quality bar

- Responsive from a phone to a desktop, keyboard-accessible, semantic HTML, visible focus states, labelled inputs, and sensible contrast.
- Loading, empty, and error states for every screen that reads or writes data. Errors say what happened and what to do next.
- Validate on the server, never trust the client, and keep secrets in environment variables with a committed `.env.example`.
- Type-safe end to end. No `any` without a comment explaining why.
- Small, readable modules named after what they do. No premature abstraction, no dead code, no TODOs left for later without a note.
- Sensible defaults over settings. If a choice is not in this brief, pick the simplest option that keeps the product coherent and say what you chose.

## How to work

1. **Read, then restate.** Summarize the product in three sentences and list your assumptions. Ask only the questions that block implementation. For everything else, decide and note the decision.
2. **Plan before code.** List the files and modules you will create, in build order, mapped to the core features. If a build plan is included above, use it instead: resume at the first step not marked done and check what already exists before touching it.
3. **Set up.** If a project already exists, inspect its code, instructions, and conventions first and build on them. Otherwise scaffold the stack above with linting, formatting, a typecheck script, `.env.example`, and a README stub.
4. **Model the data first.** Define the types, schema, and any migrations before the UI, so the shape of the product is settled early.
5. **Build in vertical slices.** Finish one core feature end to end (data, logic, UI) before starting the next. Keep the app runnable after every slice and commit each slice with a message that says what changed and why.
6. **Then the interface.** Apply the quality bar above to each screen as it lands, not as a final pass.
7. **Verify.** Run typecheck, lint, and tests. Exercise the main user flow by hand. Check each item in the definition of done and each acceptance criterion.
8. **Report.** Tell me what works, what you tested and how, what is not done, every setup step I must complete myself, and the three most useful next steps. Never claim a service, test, or flow was verified when it was not.

If you can edit and run the project, start implementing right after the short plan. If you cannot, give me concrete code and the exact commands to run for the next step.

Rules: keep the product name and the scope as written, do not invent features, prefer boring and proven choices, and stop to ask me when a decision would be expensive to reverse.

How to use

  1. Copy the prompt above.
  2. Open ChatGPT, Claude, or your AI editor and paste it into a new conversation.
  3. Build milestone one, run it, then move to the next. Add stretch goals only after the first version works.

Want ideas built around you instead? Generate four from your own interests, time, and stack.

Frequently asked questions

FAQ

Frequently asked questions

Answers on what Setup Journal is, how to build it, and where example ideas come from.

Similar ideas

Similar to Setup Journal

More productivity ideas, then a few from other categories.

Generate your own

Ready to generate yours?

Four ideas per round, shaped by your interests, skill level, and how much time you have.