Save & Writeback

Solutioneer’s default disposition is chat-only. Nothing is saved to disk and nothing is pushed to an external system unless you explicitly ask. Save and writeback are two separate paths with separate rules.

Save

Save is about writing markdown to a file on your local machine. Rules:

• Default output is chat-only.
• Before saving generated markdown to a user-requested .md path, Codex asks for confirmation.
• Codex saves only after confirmation — even if you mentioned a path in the initial message.
• The default output directory used by skill manifests is .context/solutioneer/runs, which is gitignored.

Save applies to any user-directed markdown path. If a skill produces JSON sidecars (for example seed-data.json), those follow the same confirmation rule.

Writeback

Writeback is about pushing an artifact to an external system via Composio. Rules, every time:

1. Codex confirms that you want the external write.
2. Codex confirms the target destination.
3. Codex verifies that COMPOSIO_API_KEY is present.
4. Codex verifies that the required toolkit is already connected.

If any check fails, the write does not proceed and Codex explains the block.

The Connect now / Skip decision point

When COMPOSIO_API_KEY is present but the required toolkit is not yet connected, Codex presents two options:

• Connect now — opens the Composio hosted login page in a browser tab when available. Codex waits for the user to complete login and polls the connected account until it becomes ACTIVE. Only then does the write execute.
• Skip external writeback — keeps the workflow chat-only. The artifact is still returned in chat.

If browser tooling is unavailable (for example, in a sandboxed environment), Codex provides the login link in chat and waits there instead.

The write is never executed before the connection is active.

Supported toolkit families

Solutioneer recognizes four toolkit families:

• googlesuper — Google Docs and Sheets
• confluence
• linear
• github

Each toolkit is a separate Composio connection. See Provider Overview for the specific connection guides.

What happens when COMPOSIO_API_KEY is missing

• External writeback is disabled.
• Google Docs, Google Sheets, Confluence, Linear, and GitHub writes are not attempted.
• The artifact is still returned in chat.

What happens when a toolkit is connected but the write fails

• Codex surfaces the Composio error with a short explanation.
• The artifact stays in chat.
• Codex does not retry silently.

Practical tips

• Pick your tracker. Integration Fit Gap Analyzer and POC Handoff Orchestrator can write to either Linear or GitHub. Pick one per team — duplicating trackers is usually more friction than value.
• Don’t pre-connect everything. Solutioneer only asks to connect toolkits that a specific run actually needs. You can connect one toolkit at a time as demand shows up.
• Re-use Google Docs for briefs and POC plans. Both Account Intel Brief and POC Handoff Orchestrator can push to googlesuper, so one Google connection covers both.