LogStitch support

LogStitch picks up AWS profiles two ways — import what you already have, or create a new one inside the app.

Option A — Import your existing AWS CLI profiles

If you already have profiles defined in ~/.aws/config and ~/.aws/credentials, LogStitch loads them automatically on launch. Just pick the one you want from LogStitch's profile list and skip ahead to Profiles → Test Connection.

Option B — Create a new profile inside LogStitch

1. From the menu bar, click Profiles.
2. Pick the option that matches your setup:
   • New Static Keys Profile (⇧⌘K) — access key ID + secret access key
   • New SSO Profile (⇧⌘O) — AWS IAM Identity Center / AWS SSO
   • New Assume Role Profile (⇧⌘R) — cross-account or named role assumption
3. Fill in the form, then use Profiles → Test Connection to verify it works.

Whichever path you take, make sure the credentials have the IAM policy below attached.

Read-only access to AWS Lambda, CloudWatch Logs, CloudWatch Metrics, and STS GetCallerIdentity. Nothing else. LogStitch never creates, modifies, or deletes anything in your AWS account.

The full minimal IAM policy is in the IAM policy section below — copy it into an IAM user or role and attach it to the credentials you're using with LogStitch.

1. Confirm the IAM policy is attached to the user or role the profile uses.
2. Check the region — your function's logs live in the same region as the function. Switching regions in LogStitch points at a different log group.
3. For Assume Role profiles: the role you're assuming needs these permissions in the target account, not the source account.
4. For SSO profiles: your session may have expired (typical default is 8 hours). Re-authenticate from the Profiles menu.
5. Use Profiles → Test Connection to confirm the credentials work end-to-end.

Most common causes, in order:

1. The function hasn't actually run during the selected time window. Trigger an invocation manually to test.
2. An active search or filter in LogStitch is excluding everything. Clear the search field and reset any filters to make sure you're not just looking at an empty filtered view.
3. CloudWatch ingestion delay — usually under 30 seconds, occasionally longer for cold log groups. Wait a minute and refresh.
4. The log group /aws/lambda/<function-name> doesn't exist yet. Lambda creates it on first invocation.
5. Your CloudWatch log retention is shorter than your selected window — e.g. retention is 1 day and you're looking at last week. AWS has already deleted those logs.

1. Open LogStitch → Settings → Claude Integration. Confirm Enable MCP Server is on; the status line should read Running on localhost:<port>.
2. Note the configured port. Default is 47821, configurable on the same panel.
3. Add LogStitch as an MCP server in Claude Code (see the Claude Code MCP docs for the exact command for your setup). The URL is http://localhost:<port>.
4. Reload Claude Code so it picks up the new server.

Note: Claude Desktop is not supported. Its custom connectors route through Anthropic's servers and can't reach a server running on your local machine. LogStitch's MCP server is intentionally bound to 127.0.0.1 only and never exposed to the network — this is a deliberate privacy choice, not a bug.

Still not working? Email support@logstitch.app with a screenshot of LogStitch's Claude Integration panel and the output of your Claude Code MCP configuration.

Updates come automatically through the Mac App Store. See the changelog for what's in each release. You can also subscribe to the RSS feed.

There's nothing to cancel. The 14-day trial doesn't require a credit card. The app stops working at the end of the trial unless you purchase a license. LogStitch is a one-time purchase, not a subscription, so no recurring charges either way.

Sign in to the new Mac with the same Apple ID you used to buy LogStitch and re-download from the Mac App Store. The license travels with your Apple ID.

Your local log history doesn't transfer automatically. If you want it on the new machine, copy the LogStitch folder from ~/Library/Containers/ on the old Mac to the same location on the new one before opening the app for the first time.

1. Drag LogStitch from /Applications to the Trash.
2. Delete the LogStitch folder from ~/Library/Containers/ to remove cached logs, settings, and the local SQLite history.
3. Open Keychain Access, search for "LogStitch", and delete any matching entries to remove stored AWS credentials.

That's it. LogStitch doesn't write anywhere else on your machine and never sends data off your Mac, so there's nothing else to clean up.

Email support@logstitch.app with:

• Your LogStitch version (Settings → About)
• Your macOS version
• The steps that reproduce the bug
• What you expected to happen
• What actually happened
• Screenshots or a screen recording if relevant

The "Report a bug" tile above opens a pre-filled email with this template.

Get LogStitch from the Mac App Store. Open it. Free 14-day trial, no credit card required.

If you already have AWS CLI profiles in ~/.aws/config, LogStitch imports them on launch — just pick one. Otherwise, click Profiles in the menu bar and create a new profile (Static Keys ⇧⌘K, SSO ⇧⌘O, or Assume Role ⇧⌘R). Either way, run Profiles → Test Connection to verify.

Make sure the credentials have the IAM policy attached.

The function list populates within a few seconds. Click any Lambda function, then click an invocation in the timeline. The log lines for that single request — across whatever functions, accounts, and regions it touched — are stitched into one view.