Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CLI_VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v0.0.35-6-g0f89a25
v0.0.42
12 changes: 7 additions & 5 deletions skills/base44-cli/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,7 @@ npx base44 <command>
| `base44 link` | Link an existing local project to Base44 | [link.md](references/link.md) |
| `base44 eject` | Download the code for an existing Base44 project | [eject.md](references/eject.md) |
| `base44 dashboard open` | Open the app dashboard in your browser | [dashboard.md](references/dashboard.md) |
| `base44 dev` | Start the local development server for backend functions | [dev.md](references/dev.md) |

### Deployment

Expand Down Expand Up @@ -298,11 +299,12 @@ Agents are conversational AI assistants that can interact with users, access you

Connectors are OAuth integrations that let your app connect to external services (Google Calendar, Slack, Notion, etc.). They provide access tokens that you can use in backend functions to call external APIs.

| Action / Command | Description | Reference |
| --------------------------- | ----------------------------------------------- | ----------------------------------------------------- |
| Create Connectors | Define connectors in `base44/connectors` folder | [connectors-create.md](references/connectors-create.md) |
| `base44 connectors pull` | Pull remote connectors to local files | [connectors-pull.md](references/connectors-pull.md) |
| `base44 connectors push` | Push local connectors to Base44 | [connectors-push.md](references/connectors-push.md) |
| Action / Command | Description | Reference |
| --------------------------------------- | ----------------------------------------------- | ----------------------------------------------------------------------------- |
| Create Connectors | Define connectors in `base44/connectors` folder | [connectors-create.md](references/connectors-create.md) |
| `base44 connectors list-available` | List all available OAuth integration types | [connectors-list-available.md](references/connectors-list-available.md) |
| `base44 connectors pull` | Pull remote connectors to local files | [connectors-pull.md](references/connectors-pull.md) |
| `base44 connectors push` | Push local connectors to Base44 | [connectors-push.md](references/connectors-push.md) |

**Note:** Connector commands perform full synchronization - pushing replaces all remote connectors with local ones (and triggers OAuth for new ones), and pulling replaces all local connectors with remote ones.

Expand Down
64 changes: 64 additions & 0 deletions skills/base44-cli/references/connectors-list-available.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# base44 connectors list-available

List all available OAuth integration types that can be used as connectors in Base44.

## Syntax

```bash
npx base44 connectors list-available
```

## Options

No options. The command takes no arguments or flags.

## Authentication

**Required**: Yes. If not authenticated, you'll be prompted to login first.

## What It Does

1. Fetches all available integration types from Base44
2. Displays each integration with its type identifier and metadata

## Example

```bash
npx base44 connectors list-available
```

## Output

```bash
Google Calendar
type: googlecalendar
...

Slack
type: slack
...

Notion
type: notion
...

Found 12 available integrations.
```

## Use Cases

- Discover which integration types are supported before creating a connector file
- Find the exact `type` value to use in your connector `.jsonc` file
- Check what OAuth integrations are available on the platform

## Notes

- The `type` field shown in the output is the value to use in your `base44/connectors/{type}.jsonc` file
- Use `base44 connectors push` to push connector configurations to Base44
- Use `base44 connectors pull` to pull existing connector configurations from Base44

## Related Commands

- [connectors-create.md](connectors-create.md) - How to create connector configuration files
- [connectors-push.md](connectors-push.md) - Push local connectors to Base44
- [connectors-pull.md](connectors-pull.md) - Pull connectors from Base44 to local files
4 changes: 3 additions & 1 deletion skills/base44-cli/references/connectors-push.md
Original file line number Diff line number Diff line change
Expand Up @@ -103,8 +103,10 @@ Run the command again when you're ready to authorize.
|--------|---------|
| Synced | Connector already existed, scopes updated if needed |
| Added | New connector successfully authorized |
| Provisioned | Stripe sandbox was provisioned (special case for `stripe` connector) |
| Removed | Connector was deleted from Base44 (not in local files) |
| Failed | Authorization timed out, failed, or was skipped |
| Skipped | Authorization was skipped by user |
| Failed | Authorization timed out, failed, or was not completed |

## Troubleshooting

Expand Down
55 changes: 55 additions & 0 deletions skills/base44-cli/references/dev.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# base44 dev

Start the local Base44 development server for testing backend functions locally.

## Syntax

```bash
npx base44 dev [options]
```

## Options

| Option | Description | Required |
|--------|-------------|----------|
| `-p, --port <number>` | Port for the development server | No |

## Authentication

**Required**: Yes. If not authenticated, you'll be prompted to login first.

## What It Does

1. Reads project configuration (functions, entities, project settings)
2. Starts a local development server using Deno
3. Serves your backend functions locally for testing

## Examples

```bash
# Start dev server on default port
npx base44 dev

# Start dev server on a specific port
npx base44 dev -p 3001
```

## Output

```bash
$ npx base44 dev

Dev server is available at http://localhost:3000
```

## Requirements

- Must be run from a Base44 project directory
- Project must have backend functions defined in `base44/functions/`

## Notes

- The dev server runs functions locally so you can test them without deploying
- The port defaults to an automatically selected available port if not specified
- Use `Ctrl+C` to stop the dev server
- After testing locally, use `npx base44 functions deploy` to deploy functions to Base44
8 changes: 8 additions & 0 deletions skills/base44-troubleshooter/references/project-logs.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ npx base44 logs [options]
| `--level <level>` | Filter by log level: `log`, `info`, `warn`, `error`, `debug` | No |
| `-n, --limit <n>` | Number of results to return (1-1000, default: 50) | No |
| `--order <order>` | Sort order: `asc` or `desc` (default: `desc`) | No |
| `--json` | Output logs as JSON array instead of formatted text | No |

## Examples

Expand Down Expand Up @@ -45,6 +46,12 @@ npx base44 logs -n 100 --order asc

# Last 10 errors for a specific function
npx base44 logs --function myFunction --level error --limit 10

# Output logs as JSON (useful for scripting or piping to jq)
npx base44 logs --json

# JSON output for a specific function filtered by level
npx base44 logs --function my-function --level error --json
```

## Notes
Expand All @@ -55,3 +62,4 @@ npx base44 logs --function myFunction --level error --limit 10
- If `--function` is omitted, logs are fetched for **all functions** defined in `base44/config.jsonc`.
- The `--limit` applies after merging logs from all specified functions.
- The `--since` and `--until` values are normalized to UTC if no timezone is provided (appends `Z`).
- The `--json` flag outputs a JSON array with `time`, `level`, `message`, and `source` fields per entry.
Loading