Match destinations, compare AI options, approve actions and review results.
Reviewed · 2026-10-12
On this page · 11
1. Prepare an action from a plan
- Act on Today’s research opens a side panel beside your plan; Full page opens the dedicated screen. Items in the Follow-ups list open as full pages. The top Follow-ups link returns to the previous filters, page and scroll position. For manual writing, select a section and inspect the linked plan and evidence.
- Check the method and destination. A cited issue may suggest commenting on that issue. Expand destination content/recent status to confirm the original you intend.
- Write the content or explicitly request an AI wording draft. Saving a draft prepares privately and does not send.
- Review the actual account, destination and body in Preview before execution, then approve. Report/event handoffs still require final saving in their forms.
- Record results and the next check afterwards. Later review drafts can use this action and confirmed observations as evidence.
2. Match evidence and verify the destination
- Linked from evidence · No AI used means citations, links or exact mentions produced candidates. It is not an AI-confirmed decision or completed delivery.
- Choose a method, then type a name, title, issue number or repository in Destination. Up to six suggestions appear without a Search button; More shows the next page. Before typing, only up to three exact evidence recommendations appear. Use arrow keys and Enter or click to select. The selection collapses to one line; Change preserves the title and body. Search uses no AI and distinguishes errors from no matches.
- A cited source is not necessarily the place to publish. A comparison report does not automatically become the destination for an instruction. Decide whom you need to ask and why.
- Inspect destination content/recent status for the body, assignees and available later comments. Freshness depends on connection type, access and read limits; check timestamps and errors.
- If candidates are absent or ambiguous, select manually or open the original. Do not mistake a private personal record for an external destination.
3. Choose among AI action recommendations
- AI recommendations prepares up to three alternatives from current evidence and permitted destinations. Adjust the direction toward an existing issue, direct inquiry, report/discussion or personal work, or add instructions.
- Compare purpose, method, destination and reference numbers. Alternatives might ask in an existing issue, message a relevant researcher or discuss evidence below a report.
- Recommendation batches are saved. After using one, expand the recommendations to create another draft. Continue draft opens existing wording; View result opens the completed action. Reuse consumes no AI allowance, and each action still requires review before posting.
- New recommendations preserve earlier batches in a collapsed area. Check creation time and current destination context. Inaccessible destinations are unavailable; repeating an action requires explicitly choosing Create another action.
- Use Change to correct an unsuitable destination manually. Multiple cited sources do not mean the same text should be sent everywhere.
- AI recommendations and AI wording are separate requests: the first chooses a method/destination; the second drafts content for the selected destination.
4. Know where each method leads
- GitHub comments post to an existing issue; new GitHub issues post to the selected repository. Chat messages go to the selected channel/direct conversation, and discussions go below the selected report/material. Verify access and destination.
- PI check-in sharing prepares a report for its recipient in LUNA. Personal work/check-in is a private record with no external publication.
- Manual/AI report creation and event creation prepare metadata and open the existing form. Recheck scope, period, dates, times, participants and audience there before saving.
- Continue code work links the repository and task context. Opening a repository does not complete local changes, commits or pull requests.
- For Notion or another supported publication, review the connection, actual destination and preview too. Publication does not imply overwriting the original or approving the research result.
5. Compose text, mentions, citations and attachments
- Select a method and destination, then write the title and body. Optional AI wording is prepared for that destination and applied after review. Per-request instructions can specify questions and length.
- Expand Edit & attach for Markdown headings, lists, tables, @mentions, [[document citations]], file selection, pasted images and drag/drop. Check upload limits and errors.
- Select researchers from mention autocomplete. GitHub delivery uses explicitly linked GitHub IDs; a LUNA username is not assumed to be the same GitHub identity.
- Check whether recipients can read cited documents. Links and attachments affect what is shared, so inspect the actual outgoing body and links.
- Preview headings, lists, links and attachments before saving. If the source or destination changes, review a fresh preview instead of reusing earlier approval.
6. Drafts, approval and uncertain delivery
- Save draft prepares an action. An AI draft marked ready means wording is ready, not that publication succeeded.
- Review the sending account, destination, body, attachments and changes, then choose Confirm and execute. Complete any separate creation form in that form.
- For success, inspect the result link and history. Sent does not mean read, answered, approved or research completed.
- Execution needs checking or an unknown response can mean the external write succeeded without a receipt. Inspect the original and history before sending again.
- If access, source or content changed, recheck the destination and use a new preview. Errors do not require deleting personal notes or original issues.
7. Inspect linked replies and later activity
- Open action details → Results and next check → Check linked replies. Supported destinations are read for replies and activity after the action within bounded limits.
- Directly linked replies and later activity on the same issue are labeled differently. A new issue comment is not necessarily an answer to your question; inspect content, author and time.
- Background checking is supported but is not unlimited real-time monitoring. Recent actions are checked in bounded batches; access and connection limits can cause delays or omissions.
- Check observation timestamps, errors and original links. No found reply does not prove inactivity. Inspect the original when needed.
- Separate sending an instruction, receiving a reply and verifying an outcome. AI reviews preserve those distinctions and do not invent completion or approval.
8. Record personal results and share them
- Personal work/check-in records something you do yourself. It is private and is not automatically published to the lab or a researcher.
- Save directly verified results and next steps in Results and next check. A follow-up date schedules your own review; it is not an imposed recipient deadline or an automatic message schedule.
- Share result creates a new sharing draft from the saved outcome. Choose an available chat, discussion, GitHub or report route, then preview and approve again. The original private record is not automatically published.
- I finished my follow-up clears your follow-up candidate. It is different from external task completion, experimental success or PI approval.
- Your results are self-reports; linked replies are observed evidence for AI review. They feed newly generated reviews/plans without automatically overwriting earlier saved text.
9. History, counts, cancellation and deletion
- Use the number beside a plan or Follow-ups → View all to inspect actions. Event-history counts can include state changes and differ from confirmed execution counts beside plans.
- Cancel a pre-execution draft with Cancel this action. This does not undo an existing GitHub comment, issue or chat. Check results first for processing or uncertain actions.
- Expand Delete record in the list/details, review its irreversible scope and confirm. Draft, cancelled and posted records can be removed, but processing work needs outcome checks first.
- Deleted personal actions are excluded from lists, detail views and AI evidence. Minimal receipts needed to prevent duplicates or authorize shared attachments may remain.
- Deleting a personal execution record does not delete external issues, comments, chats, reports or original attachments. Use the original service's controls and permissions for those.
10. Recurrence, scheduling and GitHub access
- Expand recurrence/scheduling only when needed. It starts disabled; recurring draft preparation and scheduled fixed-text delivery are different.
- Scheduled delivery requires the complete actual destination/body preview and separate confirmation. Free-text instructions do not authorize arbitrary recurring external actions.
- Changed sources, content or permission can stop a schedule or require renewed review. Check status/history and recurrence when cancelling or deleting.
- In personal GitHub connection settings, connect only your account's required repositories. This does not grant access to other researchers' private scopes.
- Disconnecting blocks later execution but leaves existing publications. Linking to repository work is distinct from actually committing code or opening a PR.
11. English display and translated drafts
- In English mode, action lists, pickers and editors translate titles, destination labels, linked sources, recommendations and expanded context with the existing free translator on supported devices. Destination IDs and links stay unchanged and no personal AI allowance is used.
- Korean Title, Content and Follow-up fields first show an English preview. Choose Edit original to revise the source or Use English draft to apply the translation to the field. Viewing a preview or saving a draft alone does not replace the original with English.
- View original restores display text. It does not undo edits already applied with Use English draft. Late translations never overwrite text you are editing.
- Mentions, document-citation syntax, link URLs, code, filenames, dates and Markdown markers are preserved. Review names, terminology and context before applying. The final execution review shows the actual saved text that will be submitted and is not automatically translated.
- Translations of a saved action's title, body and follow-up criteria are reused as private copies. Changed source versions or access invalidate reuse; deleting the action clears its copies. Unsaved edits are translated only in the current page.
- Choose Enable translation if the device needs preparation. Unsupported devices show a saved copy or the original, with no automatic switch to paid AI. Full pages and the action drawer in Today's research use the same behavior.