Skip to content

Aldwin 0.0.3

Choose a tag to compare

@folathecoder folathecoder released this 01 Nov 21:58
· 37 commits to main since this release
7ad8da9

Aldwin can now connect to your other apps through MCP servers, and warns you when it detects a secret in your message.

Added

  • Connectors: connect Aldwin to Notion, Linear, GitHub, Context7, and other apps with /connectors. Each connector is an MCP server that adds tools to the current session.
    • Catalogue: pick a service from the built-in list and sign in through your browser; Aldwin handles the OAuth flow and stores the token at ~/.aldwin/credentials/<name>.json (mode 0600).
    • Custom URL: paste any remote MCP server URL that is not in the catalogue.
    • Local servers: run any MCP server from a shell command; the command is shown for approval before it starts, and re-approved after any hand edit. Local servers are not supported on Windows.
    • Import: aldwin connectors import reads connector configs from other agent apps on your machine and adds compatible entries.
    • Ask Aldwin to connect: type "connect me to Notion" and Aldwin proposes the right connector for you to approve.
    • On-demand tool loading: tools are loaded from the server only when the model needs them. Up to 40 connector tools can be active at once; /new clears the loaded set.
    • Trust toggle: control whether a server's read-only tools run on Auto or always ask first.
  • Pasted-secret warning: Aldwin detects patterns that look like API keys, tokens, or passwords in your message before it is sent to the model. Confirmed messages have the detected text redacted in the session file and in logs/approvals.jsonl.
  • mcp version in --version: aldwin --version now reports the installed mcp SDK version, for example aldwin 0.0.3 (protocol v2, agentling 0.1.1, mcp 2.3.0).

Fixed

  • The set_persona tool always stated the persona limit as 2,000 characters even when limits.persona_chars was set lower. The tool now states the configured limit.
  • /memory always said "Notes in the last 7 days" regardless of the limits.notes_days setting. The count and label now follow notes_days.
  • /tools labelled every tool that needs approval "(always asks y/n)". Each tool now shows a note that matches its actual approval tier.
  • Setting theme: light or theme: colour_blind in ~/.aldwin/config.yaml had no effect. The configured theme is now applied.
  • The "Stopped after N steps" notice always said 15 regardless of limits.max_steps. It now shows the configured limit.
  • Some invalid config.yaml values produced garbled errors. Key fields now produce clear, human-readable messages.
  • Running aldwin from a folder that had been deleted after you cd-ed into it crashed with a traceback. Aldwin now falls back to ~/aldwin_workspace.

Security

  • Aldwin warns and asks for confirmation when it detects a secret-looking pattern in your message. Confirmed messages are redacted in the session file and logs/approvals.jsonl.
  • Connector sign-in tokens are stored at ~/.aldwin/credentials/<name>.json (mode 0600) and never passed through the model.
  • Local MCP server commands are shown for approval before they start and re-approved after any hand edit.
  • Connector tool output is wrapped as untrusted data, the same as file and command output.

Upgrade notes

Upgrading from 0.0.2 or 0.0.2.1 keeps all your sessions, notes, memory index, persona, and settings. No migration runs on first launch:

uv tool upgrade aldwin

There is no connectors.yaml or credentials/ folder until you add a connector with /connectors.

Known limitations

  • Local MCP servers run with your user's rights; there is no sandbox. A server can mark a write tool as readOnlyHint: true, and Aldwin trusts that hint.
  • Only macOS 13+ and Linux are supported. Local MCP servers are not supported on Windows.

Full changelog: https://github.com/lunarstack-co/aldwin/blob/main/CHANGELOG.md