Give scheduled agents shared memory
Let a recurring briefing, research job, or project review pick up where its last run stopped. The service running the job handles the schedule; Stele holds the context and outcomes between runs.
Connect Stele where the job runs
Installing the CLI on your laptop does not connect a cloud job. Connect Stele in the app running the job, sign in, and make sure the job can use that connection. Select the same project your other agents use, or create one for this work. No local repository is required.
Claude's scheduled tasks can use connected tools and run remotely. Add Stele as a custom connector using the Claude connection steps, then create or edit the scheduled task's instructions to include the project and the read/save routine below. Review the schedule, timezone, and instructions in Claude. See Claude's scheduling guide for current availability and controls.
A host may expose different tools in a scheduled run than in an interactive chat. For ChatGPT or another host, check that its scheduler can use your Stele connection, including the writes the job needs. A successful chat connection alone does not establish that. If the scheduler cannot use it, run the workflow interactively or use a scheduler that supports the connection.
Add memory instructions to the job
Keep your existing job description. Append the instructions below, replace <project-slug> with your actual project slug, and choose one stable name for this job, such as research.weekly-briefing. Keep that name unchanged across runs so the job can find its own history.
Use Stele project <project-slug>. This job's stable name is research.weekly-briefing. Before each run, recall the project's relevant goals, decisions, and open work. Read this job's latest Timeline entry and follow its linked run record. Check its outcome, then find the last completed run if the latest run failed or was partial. Continue from the last confirmed progress; avoid repeating completed work. If there is no prior run, use the initial scope below. After the work, save useful findings and unresolved work in Stele with their sources. Keep reusable project knowledge separate from the run summary. Save a run record with the period covered, outcome, and next starting point. Add one Timeline entry under research.weekly-briefing linking to that record, with completed, partial, failed, or blocked status as appropriate. If Timeline logging is unavailable, maintain a clearly named job-state document in Stele and read it at the start of every run. If Stele itself is unavailable, say which context you could not read or save; do not claim that sharing succeeded. Do not perform actions that depend on missing context. Initial scope: <what the first run should cover>.
The run record tells tomorrow's agent where to resume. Saved decisions and findings also become available to your other agents. Recording failed and partial runs makes gaps visible.
Verify a run before relying on it
- Use the scheduler's run-now option, or wait for its next scheduled execution.
- Check the run output: did it retrieve the intended Stele project and save a run record? Resolve any sign-in or tool-approval requests in the host.
- Open a separate agent connected to that project and ask it to retrieve the saved findings.
- Check that the next run reads the previous outcome and continues from it.
Use Stele project <project-slug>. Find the latest run of research.weekly-briefing, read its linked record, and tell me what completed, what remains, and when it ran.
If no record appears, inspect the scheduled run's tools and connection first. If it wrote to the wrong project, correct the slug in the saved job instructions. If each run starts over, check that the job name stays the same and that the instructions read the prior state before doing new work.