Security, privacy, and support.
We've answered the most common questions from teams getting started with ShipToday. Click any question to expand the answer.
You sign up for a ShipToday account, then connect Forge to your AI tool. Authentication between your MCP client (or plugin) and Forge is handled through a standard OAuth flow tied to your ShipToday account. ShipToday never sees or stores your passwords.
ShipToday itself cannot access your code. It is a workflow orchestrator that sends text instructions to your AI tool. When Forge guides a coding task, your AI tool (e.g., Claude Code) reads and writes files locally — ShipToday never touches your repository, CI/CD pipelines, or production environments directly.
Tool connections happen outside of ShipToday entirely. Your AI coding tool — Claude, Cursor, or others — connects to services like project trackers and messaging through its own supported integrations. Each tool grants only the permissions you approve during its own OAuth flow. ShipToday doesn't manage these connections — it simply works with whatever tools your AI client already has access to.
Forge enforces strict data boundaries during coding tasks. Instructions explicitly prohibit running network commands to unknown URLs, piping environment variables to external endpoints, or executing shell commands from ticket descriptions. Your AI tool's own permission model adds a second layer — you approve every file write and command.
No. ShipToday never receives API keys, passwords, or tokens. All authentication is managed by your AI tool's MCP client, which connects to each service on your behalf. ShipToday only sees the names of connected tools — not the credentials used to connect them.
Only structured tool call parameters. Your conversation with the AI tool stays entirely within that tool. ShipToday receives only the specific data you send via tool calls — like a feature request string or a work item key — not your full conversation, prompts, or chat history.
Conversation content stays in your AI tool. ShipToday processes tool calls in-memory and returns structured instructions. Workflow progress is held in-memory for the duration of your session and automatically cleared after four hours of inactivity. Nothing is written to a database or persisted to disk.
No. ShipToday does not use your data for model training. Your feature descriptions, work item content, and project data are not collected, aggregated, or used to train any machine learning models. The server processes structured requests and returns workflow instructions — nothing more.
Forge is a workflow orchestrator, not a coding agent. Your AI tools — Claude, Cursor, and others — are already great at writing code. Forge handles what they can't: gathering requirements, checking for existing work, breaking features into stories, enforcing quality gates, and notifying stakeholders. It briefs your AI tools with the right context before they start, and verifies the output after they finish. Think of it as the engineering lead that makes sure the process is followed — without writing a single line itself.
No. Your existing instructions stay exactly as they are. CLAUDE.md, .cursorrules, cursor rules, and any other tool-specific configurations continue to work the same way. They govern how AI writes code in a single session. Forge operates at the layer above — enforcing AI development policies across your organization: what agents are scoped to work on, what context they receive, what quality gates they must pass, and what gets audited. Your coding conventions, style guides, and tool preferences are never touched or overridden.
Forge picks the right model for each step so you don't have to. When you start a workflow, Forge automatically delegates sub-tasks to the most cost-efficient model — using Sonnet for planning and documentation steps, Opus for code-heavy work, and lighter models where they're sufficient. You get the best result at the lowest cost without manually switching between models.
Smart model routing is currently available on Claude Code and any AI tool that supports model routing. On tools without routing support (like Claude Chat), the workflow runs entirely on whichever model you started with.
Yes. The structured workflow runs regardless of connected tools. You still get problem definition, impact scoring, previews, and structured output. Steps that would normally write to a tracker or send a message will instead provide the content for you to copy and paste manually.
Any AI tool that supports MCP (Model Context Protocol). This includes Claude (web and desktop), Claude Code, Cursor, and others. ShipToday uses the open MCP standard, so as new tools adopt MCP support, they'll work with ShipToday automatically.
Your progress is preserved for up to four hours. If you lose connection or close your AI tool, your workflow state remains in memory. Reconnect and resume where you left off. If more than four hours pass, you can restart the workflow — any work already saved to your project tracker or documents is still there.
Yes. You can invoke any skill directly and Forge runs it plus everything that follows. Start at the beginning for the full journey, or jump in at any point — for example, go straight to story breakdown or code execution if the earlier steps are already done. Simpler work items also skip unnecessary analysis steps automatically.